Trust scores
A 0–100 score + A–F grade that makes “is this safe to build on?” answerable in one glance — and auditable in one more.
Endpoint
bash
GET /v1/trust-scores/:id # id or slug — → { score: 86, grade: "B", factors, summary, computedAt }Also embedded in GET /v1/apis/:slug as trustScore.
Eight factors
Uptime24h / 7d / 30d from api_current_health
Response timep50 over recent health checks
Docs qualitydocumentationUrl present + OpenAPI availability
Auth clarityauth type normalized, warnings if ambiguous
CORScorsStatus Yes/No/Unknown
Pricing claritypricing type + rateLimitText + creditCardRequired
Freshnessdays since last verification / update
OpenAPIopenApiUrl / openApiAvailable
Evidence, not just a number
Every profile renders an evidence block sourced from api_field_sources + api_health_checks + api_metadata:
Reliability: High
✓ Successful probes past 30d · 99.2% uptime
✓ Public status page available
⚠ Two degraded-performance windows observed
✓ Last verified 3h ago — AUTOMATED_CHECK
Sources: PROVIDER / AUTOMATED_CHECK / CORE_API_REVIEW / COMMUNITY_REPORT / IMPORTED / UNKNOWN. See Trust & evidence.
When to trust / not trust
Treat scores as decision support, not a substitute for reading the provider’s terms before production. Low freshness or UNKNOWN pricing/cors are shown explicitly — stale is visible, not hidden.