Query the index, exports and checks over plain HTTP. No key needed to start.
One call
$ curl -s "https://satohub.ai/api/export/index.json?chain=Base" | jq '.resources[0] | {name, category, trust_score, liveness}' # the first Base listing: its name, category, Sato Score and liveness
Each export says when it was generated. A null means Sato Hub has no record, never zero.
By job
Look up one project, or what changed.
A GitHub repo or npm package to its listing
What changed since a date
The public counts, with their date
How fresh each data source is
Search Agent Passports
Sato Score badge (shields.io JSON)
The whole catalogue in one file. JSON, CSV or NDJSON.
Every listing. Slice with ?category= ?chain= ?standard= ?use_case=
The same rows for a spreadsheet (also .ndjson)
Agent skills with disclosures
The inputs behind each Sato Score
Listed MCP endpoints and their handshake result
x402 endpoints checked for a real HTTP 402
Look before you install, connect or pay.
What a package, MCP server, skill or repo can do with your keys
Every target in an install command or MCP config
A list of targets against your policy
A repo, package, endpoint, agent or token: go, caution, no or unknown
A whole dependency manifest in one call
Get told when a verdict changes
Which one, and why. Unsigned answers only.
A goal in plain words to a build plan
A venue for a swap, fee disclosed
A swap quote checked against your policy, unsigned
Which registered agent should take a task
An x402 endpoint that answered for a capability
Dated readings by registry, chain and step.
This week's readings (also .csv and .ndjson)
ERC-8004 agents on a chain, with what each declares
Generate a client
/api/openapi.json
OpenAPI contract
Every public read in one document. Generate a client from it.
/schemas
JSON Schemas
Each response shape at a stable URL, draft 2020-12. Version 1 only gains fields.
/api/pricing.json
Prices and limits
Every price, limit and fee in one machine-readable sheet.
Exports come as JSON, CSV and NDJSON. NDJSON puts one record per line, for streaming and warehouse loads. The change feed tells you what moved since a date, so you do not have to re-pull the whole index; read its coverage block, which says which parts are complete and which are partial.
Signed responses declare their shape with a Link: rel="describedby" header. A breaking change would ship as v2 at a new URL.
Catalog data CC-BY-4.0 — attribution: data by satohub.ai. Scores/liveness are informational signals, not safety or quality guarantees.
Pay per call
A few reads are paid per call in USDC with x402. No account: your client answers the 402 and retries.
Score history
GET/api/x402/history/{slug}
$0.005 for up to 90 days, +$0.001 per day beyond
Agent-economy series
GET/api/x402/agent-economy
$0.0001 per row, minimum $0.005
Large batch checks
POST/api/preflight/batch
free up to 50 targets and 10 live checks; beyond, $0.0005 per target and $0.005 per live check, minimum $0.005
Ask which declared x402 endpoint answered a 402 in the last seven days for a capability, then pay it with your own wallet. Sato Hub is a read: it does not relay, hold or settle funds.
1 · ask for a route
GET https://satohub.ai/api/route/x402
?capability=price-feed&chain=base
→ { "endpoint": "https://seller.example/v1/price",
"terms": { "scheme": "exact", "network": "base",
"asset": "USDC" },
"chosen_by": [ { "signal": "answered HTTP 402 …",
"value": "yes, within 7 days",
"checked_at": "2026-09-10" } ],
"checked_at": "2026-09-10" }2 · pay it from your wallet
{ "tool": "initiate_x402_request",
"arguments": {
"url": "https://seller.example/v1/price",
"method": "GET",
"maxPayment": { "amount": "0.01",
"asset": "USDC",
"network": "base" } } }Chosen by the readings in chosen_by, on the dates shown. A verified 402 is a protocol check: on that date the URL asked for money in a payload a client could parse. It is not a statement that the endpoint works, delivers, is solvent or is safe, and no payment was sent to establish it. No standing verification answers 404 { unknown } rather than a guess.
Building an AI agent?
The MCP server gives it the same data as typed tools.
Reference
Sato Hub. "Sato Hub API." Sato Hub, updated 2026-10-06, accessed 2026-10-06. https://satohub.ai/docs/apiData last refreshed 2026-10-06; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.