Quality Policy

1. Quality Scoring

Every active service on AgenticTrade receives an automated quality score from 0 to 100, calculated from the past 30 days of health check data. Scores update hourly.

• Uptime (50%) — Percentage of health checks where your endpoint returned HTTP 2xx–4xx (not 5xx or timeout)
• Latency (30%) — Average response time. 0ms = 100 points, 5,000ms = 0 points (linear scale)
• Error Rate (20%) — Percentage of checks resulting in HTTP 5xx or connection failure

2. Quality Tiers & Commission

Your quality score determines your marketplace ranking and commission rate:

Tier	Quality Score	Commission Rate	Benefits
Premium	95+	6%	Top discovery ranking, Premium badge
Verified	80–94	8%	Verified badge, priority in search results
Standard	60–79	10%	Standard listing
At Risk	Below 60	10%	Subject to automatic pausing

3. Monitoring Process

Our automated health monitoring system runs 24/7 with the following cycle:

1. Hourly health checks — Every active service endpoint is tested once per hour
2. HTTP GET request — We send a GET request to your registered endpoint
3. 10-second timeout — Responses must arrive within 10 seconds
4. Success criteria — HTTP status code below 500 is considered "reachable"
5. Score recalculation — Quality scores are recalculated using the most recent 30 days of data

4. Enforcement Actions

4a. Quality Warning (Score below 75)

• You receive an email notification in your preferred language
• Your service remains active but may rank lower in discovery results
• Maximum one warning email per service per day

4b. Automatic Pause (Score below 60 for 3 consecutive rounds)

• Your service is automatically paused — it will not appear in the marketplace
• You receive an email notification with instructions for reactivation
• Existing API calls to your service will receive a 503 response
• Your service data and configuration are fully preserved
• A Telegram alert is sent to our operations team for monitoring

4c. Trend Alert (Score drops 15+ points in 7 days)

• You receive an early warning email about the declining trend
• No immediate action is taken on your service
• This gives you time to investigate and fix issues before quality drops further

4d. Dead Service Removal (Uptime below 10% after 10+ checks)

• Services that are consistently unreachable are automatically deactivated
• This protects marketplace consumers from broken endpoints

5. Reactivation Process

1. Fix the underlying issues (downtime, slow response, errors)
2. Verify your endpoint responds consistently: under 5 seconds, HTTP 2xx status
3. Contact us to request a reactivation review
4. Your service enters a 24-hour observation period
5. If quality remains above 60 during observation, your service is fully reactivated

6. Multilingual Notifications

All quality notifications (warnings, pause notices, trend alerts) are sent in your preferred language. We currently support:

• English
• 繁體中文 (Traditional Chinese)
• 한국어 (Korean)
• 日本語 (Japanese)
• Français (French)
• Deutsch (German)
• Русский (Russian)
• Español (Spanish)
• Português (Portuguese)

To set your preferred language, use the PUT /api/v1/provider-contact endpoint with your email and preferred locale.

7. Provider Best Practices

• Monitor your own endpoint — Don't rely solely on our checks; set up your own uptime monitoring
• Respond quickly — Keep latency under 2 seconds for Premium tier
• Handle errors gracefully — Return appropriate HTTP status codes, not 5xx for expected errors
• Set up notification contact — Register your email via the API so you receive alerts early
• Use health check endpoints — Implement a dedicated /health route for quick checks

8. Appeals

If you believe your service was paused incorrectly, or if external factors (network outage, DDoS) caused temporary quality drops, contact us. We review all appeals within 24 hours and can manually override automatic actions when justified.

9. Changes to This Policy

We may update this policy as the platform evolves. Changes will be announced via email to all registered providers and posted on this page. The "Last updated" date above always reflects the current version.