Reliability
How well each endpoint actually works
Success rates over the last 14 days, taken from terminal job outcomes. Every number carries the sample it came from, because a rate without a denominator is a decoration.
What these numbers are
Rates are terminal job outcomes over the window, split by caller. Internal traffic is one first-party workload and its mix moves independently of service quality; the reliability corpus in the repository is the mix-independent measurement.
Rates are withheld below 50 requests. “100% success over three requests” is not a reliability claim, and publishing it as one would make this page least trustworthy exactly where it matters most.
| Endpoint | Tier | Target | Customer traffic | Success | Keeping it | First-party traffic | Success | p50 | p95 |
|---|---|---|---|---|---|---|---|---|---|
| hn_post | ga | 99.0% | 0 | — | not enough traffic | 0 | — | — | — |
| hn_search | ga | 99.0% | 0 | — | not enough traffic | 0 | — | — | — |
| infra | ga | 99.0% | 21,215 | 96.1% | no | 0 | — | 3.3 s | 37.1 s |
| linkedin_employees | ga | 99.0% | 3,513 | 100.0% | yes | 0 | — | 22.5 s | 133.0 s |
| seo | ga | 99.0% | 44,235 | 98.0% | no | 0 | — | 9.0 s | 35.3 s |
| mentions | beta | 75.0% | 0 | — | not enough traffic | 0 | — | — | — |
| research | beta | 75.0% | 7 | — | not enough traffic | 0 | — | — | — |
| rss | beta | 75.0% | 0 | — | not enough traffic | 0 | — | — | — |
| search | beta | 75.0% | 8,871 | 94.4% | yes | 0 | — | 1.5 s | 2.7 s |
| sitemap | beta | 75.0% | 0 | — | not enough traffic | 0 | — | — | — |
| url | beta | 75.0% | 39,381 | 91.3% | yes | 0 | — | 1.2 s | 4.0 s |
| ads | experimental | — | 125,041 | 96.4% | no target | 0 | — | 1.4 s | 39.3 s |
| brand | experimental | — | 4 | — | no target | 0 | — | — | — |
| channel | experimental | — | 78,760 | 79.0% | no target | 0 | — | 2.3 s | 23.1 s |
| company | experimental | — | 37,180 | 96.6% | no target | 0 | — | 56.0 s | 130.8 s |
| linkedin_person_posts | experimental | — | 0 | — | no target | 0 | — | — | — |
| linkedin_post | experimental | — | 0 | — | no target | 0 | — | — | — |
| linkedin_profile | experimental | — | 0 | — | no target | 0 | — | — | — |
| producthunt | experimental | — | 4,131 | 2.6% | no target | 0 | — | 10.1 s | 10.1 s |
| reddit_post | experimental | — | 0 | — | no target | 0 | — | — | — |
| reddit_profile | experimental | — | 0 | — | no target | 0 | — | — | — |
| site | experimental | — | 0 | — | no target | 0 | — | — | — |
| social_engagement | experimental | — | 0 | — | no target | 0 | — | — | — |
| social_mentions | experimental | — | 0 | — | no target | 0 | — | — | — |
| x_post | experimental | — | 52 | 100.0% | no target | 0 | — | 1.3 s | 2.1 s |
| x_profile | experimental | — | 413,677 | 95.1% | no target | 0 | — | 3.1 s | 63.2 s |
What the tiers mean
- ga
- Succeeds at least 99% of the time over a fortnight. Safe to build on without a fallback path.
- beta
- Succeeds at least 75% of the time over a fortnight. Usable, but handle failures — and infrastructure-class failures are refunded.
- experimental
- No reliability commitment. Available, not recommended for anything load-bearing, and absent from the SDKs and the MCP tool list.
gateVerdict compares external traffic against the tier's published SLO. It reports whether a label is currently being kept; it does not promote or demote anything. Tier changes are decided on the versioned corpus, because a traffic-based rate follows the caller's mix as much as the service.