The directory that checks its own links.

an independent project. one worker, a probe schedule, and a grudge against dead tutorials.

What this is

shipapis is a directory of free public APIs — weather, photos, exchange rates, and hundreds more. For APIs on our probe schedule (1035 today — 317 probed, 720 queued — out of 1037 catalogued), we hit a real documented endpoint on a regular cadence and show uptime history, latency, CORS behavior, and the free-tier fine print. Listed-only entries stay metadata until we add them to monitoring.

Why it exists

Every "awesome free APIs" list rots. Endpoints die, schemas drift, free tiers quietly grow teeth — and the list keeps ranking in search, wasting an afternoon at a time. A directory should know when its own links die. Ours does: dead APIs are declared, dated and archived in the graveyard with their final response shape, so the tutorial you found in 2023 can at least be understood.

How it works

A monitoring sweep runs every 15 minutes across probed APIs, hitting one real documented endpoint per API and recording status, latency and response shape. Scores are computed from a published formula — uptime, latency versus category, schema stability. The same data feeds the pages, the meta-API, the MCP server and the static snapshots, so humans and AI agents read from one source of truth.

The rules we hold ourselves to
NO PAID PLACEMENTRankings come from the formula. Sponsorship, when it exists, is labeled and never mixed into results.
EVERY METRIC LABELEDWhat was measured and over which window — always. No naked numbers.
NEVER CLAIM BEYOND THE CHECKERIf our infrastructure can’t verify something, it’s marked unverifiable — never "down", never invented.
OWNERS STAY IN CONTROLAny API owner can correct metadata, dispute a score, or opt out entirely — opted-out APIs show UNMONITORED.
OPEN DATAThe catalog and health data are CC-BY-4.0 — free to use, index and train on, with attribution.
Contact

Corrections, disputes, submissions, anything else: hello@shipapis.dev. To list an API, use the submit page — it probes your endpoint live before it queues.