A catalogue that is checked, not copied
Every install carries 1507 public API records in the graph. They are not a list we pasted once: each record is re-probed on a schedule, and the result is stored on the node next to the claim it qualifies.
- alive
- The catalogue URL answered. A 4xx that a server chose to send is alive too — the host is there.
- needs a key
- 401, 402 or 403. The resource is alive; you need credentials or a payment to see it.
- dead
- No such name, connection refused, or 5xx twice in a row. Proven gone, not guessed gone.
- not confirmed
- A timeout, a TLS error, one 5xx out of two. “Could not check” is its own status and never a death certificate.
Source: the public-apis list under MIT. Status: our own probe against the same address.
Search the catalogue
Loading the catalogue…
| API | Category | Auth | Status |
|---|
Paid routes an agent can call on its own
A separate service under the same roof:
api402x.com answers 18 routes behind an HTTP 402 challenge —
USDC on Base, no key, no account, no subscription. Every paid route has a
free /preview sibling that returns the real shape of the
answer before you pay for one.
| Route | What it answers | Price |
|---|
Prices are read from each route’s own 402 challenge, which is the only authoritative copy.
How a record becomes a status
- The claim is a node
- Each API is one node with
kind=api, the source line of the public-apis list, and the URL as evidence. It went through the same P1–P6 gate every other node does. - The probe writes onto the node, not over it
observed_at,status,http_codeandrecheck_afterare added by the probe. The claim, the tags and the kind are never touched, so a probe can be wrong without corrupting the record.- Rechecks are scheduled by outcome
- alive and needs-a-key come back in seven days, dead in one day, not-confirmed in one hour. A host that was down for a minute is not buried for a week.
- A probe is not a verdict
- Records whose status is inferred rather than observed carry
not_a_verdict. The catalogue can say “I could not check”, which is the whole reason the fourth status exists.
Regenerate this page’s data with
python3 tools/site/export_catalog.py. It reads the store and
the live 402 challenges; it writes nothing back.