Site Statistics and Transparency
This page is auto-generated from our snapshot data on every build. We run hourly HTTP checks on every API in our catalog and publish the aggregate measurements here. The full per-API data is exposed at our public JSON API for anyone who wants to build on top of it.
Catalog overview
active APIs tracked
in the graveyard (dead or paid)
categories
recent state-change events
Performance leaders
Fastest 5 right now
- Coinbase Advanced Trade API (Public) — 16 ms · cryptocurrency
- PokéAPI — 16 ms · public-data
- ip-api.com — 20 ms · geocoding
- NOAA National Weather Service — 29 ms · weather
- Weatherstack — 43 ms · weather
Slowest 5 right now
- Wikipedia REST API — 2032 ms · news
- The Guardian Open Platform — 918 ms · news
- Blockchair API — 789 ms · cryptocurrency
- Twelve Data — 747 ms · finance
- OpenCage Geocoding API — 663 ms · geocoding
These are single-point latest readings, not averages. An individual slow check can place an API in the slowest list temporarily; check the per-API page for the 30-day trend.
Per-category breakdown
| Category | APIs tracked | Alive now | Avg response time |
|---|---|---|---|
| cryptocurrency | 14 | 8 | 174 ms |
| dev-tools | 12 | 0 | 0 ms |
| finance | 14 | 5 | 1624 ms |
| geocoding | 14 | 6 | 276 ms |
| news | 14 | 6 | 329 ms |
| public-data | 10 | 7 | 204 ms |
| weather | 15 | 7 | 296 ms |
Authentication distribution
Of the 93 active APIs we track, the authentication burden splits as follows:
- 52 require no API key at all (genuinely keyless — you can integrate them in one fetch call)
- 41 require an API key (signup, usually free with email only)
- 0 require OAuth (more complex integration, often the sign that an API has user-scoped data)
Free-tier friction distribution
We score each API's free tier on a 0-1 scale based on signup friction. A no-key public API scores 1.0; an API requiring a free key with email signup scores 0.7; an API requiring credit-card details on signup scores 0.3. The split across our active catalog:
- 47 APIs with score 1.0 (no key, no signup, no card)
- 46 APIs with score 0.7 (key + email signup, no card)
- 0 APIs with score 0.3 or below (card required at signup, or other friction)
How this data is collected
Every hour, a Cloudflare Worker reads our catalog from D1, sends one HTTP request to each active API's documented health endpoint or simplest functional endpoint, and records the status code and response time. A second daily Worker rolls these into 30-day uptime percentages and average response times per API. The full methodology — including how we handle retries, timeouts, and User-Agent requirements — is documented at /methodology.
The data on this page was generated at 2026-07-10T21:53:20.713Z, the timestamp of the snapshot consumed by this build.
What's not here yet
Things we'd like to add but haven't: regional latency comparison (pinging from multiple Cloudflare edge locations), body-level response validation (catching APIs that return 200 with errors inside), and historical uptime graphs beyond 30 days. If you'd find any of these especially useful, the contact form is here.