Anyone can publish a list. This page explains — in enough detail to copy or to catch us out — how every status on this site is earned.
✅ Verified (111 APIs). Hand-picked, mostly famous, and tested at the endpoint level: a real GET request to a documented sample endpoint. We publish the outcome three ways — status, response time, and the captured response itself on the listing page. In the latest run: 81 live, 25 free-key listings, 5 marked down in red.
📋 Listed (1,526 APIs). Imported from the open public-apis dataset (MIT license) and link-checked: the official site must answer our request. 258 entries failed even that and were dropped before ever appearing here. Listed APIs graduate to Verified as endpoint tests complete, most-wanted first.
Every listing carries one number so you can compare at a glance. It is computed, never assigned by hand: Availability (40) — share of endpoint checks answered live, from the recorded history; Speed (25) — latest measured response time, full marks under 200 ms; Friction (20) — keyless beats free-key; Browser-ready (10) — CORS support; Freshness (5) — checked within the week. Grades: A ≥ 85, B ≥ 70, C ≥ 55, D ≥ 40, F below. Listed-tier APIs cannot earn availability points until endpoint-tested — the score says so by being low, which is the point.
Every API also has a public history page (linked from its listing) with its full check log, incidents and uptime, plus a machine-readable status JSON — the same data our badges and scores read.
Found a status that's wrong, a limit that's changed, or an API that died between runs? Tell us — corrections land in the next weekly run, and the change is visible in the listing's history of dates. Maintainers can also request re-checks the same way.
Last full run: 22 Oct 2026 · 1,637 APIs published · Dataset: open JSON catalog · Machine-readable summary: llms.txt / llms-full.txt