Catalog
356 production APIs, under one contract.
- 356Live endpoints
- 29Categories
- 705msMedian latency
- 34New
- 99.9%Uptime SLA
Showing 18 of 356 APIs
APICategoryLatency UptimeCost
001–018 of 356
One contract
Every endpoint behaves the same way.
Learn the pattern once. It holds across all 356 APIs — same envelope, same auth, same billing.
# the same shape on every one of 356 endpoints { "status": "ok", "error": null, "data": { /* endpoint payload */ } }
One response envelope
Every call returns status, error, and data. Write your parser once.
Typed SDKs
First-party clients for Node, Python, Go, PHP, and .NET — plus plain REST.
Predictable credits
One pool spends across the whole catalog. No per-endpoint rate cards.
99.9% uptime SLA
Served from 24 regions, with latency published on every API page.
How does pricing work per API?
Each call spends credits from one shared pool. Most APIs cost 1 credit; compute-heavy ones cost 2–5, shown on every API's page before you call it.
Do all APIs return the same format?
Yes — every endpoint wraps its result in
{ status, error, data }. Ask for JSON, XML, or YAML with a single parameter.Can I try an API before I sign up?
The free tier includes 100 credits a month across the whole catalog, no card required. Upgrade only when you need more.
Is there an SDK for my language?
Typed clients ship for Node, Python, Go, PHP, and .NET, plus a plain REST interface that works with any language.
Can AI agents call these APIs?
Yes. The MCP server exposes the full catalog to your agents behind the same key — no per-endpoint wiring.
How reliable are the APIs?
Every endpoint runs under a 99.9% uptime SLA across 24 regions, with p50–p99 latency published on each API page.