Documentation 29
Documentation · start here
Your first request, without the setup.
Point the client you already use at SandboxAPIs — any provider in the catalog — and your read code just works against a deep, real-looking data set (olympus-labs), not an empty test account. Read-only and API-identical (every dialect the real provider offers); adoption is a one-line base-URL swap, with no path prefixes and no custom routes.
01Get a free key — or stay anonymous
02Set one env var
03Your app just works
01 / Pick a provider
21 hosts, all drop-in.
21 providers
git host4
issue tracker2
AI telemetry5
messaging2
CI/CD2
observability3
CRM/support3
02 / The guarantees
How it works.
- Exact mirror. Provider hosts serve provider paths exactly — same JSON, headers, status codes. Your existing client library works unchanged.
- Read-only. Writes return the provider's error shape with a friendly "this universe is read-only" message naming what was attempted.
- Coherent. Every reference resolves — a PR's author is a fetchable user, its commits exist with matching SHAs, on every provider alike.
- Deterministic. Pinned snapshots regenerate byte-identically, so CI never flakes on the data.
- Cheap to poll. Reads carry an
ETag, and a conditional request that returns 304 costs nothing when our CDN answers it from its shared cache.
03 / Next steps
Where to go from here.
Verified quickstarts10 clients whose exact snippet a script runs against the live hosts on demand.Keys & rate limitsHow a key rides each provider's own auth slot, and what the tiers are.Versioning & pinningDeterministic CI that never flakes on data.MCP setupThe agent front door — discovery and query tools.Coverage manifestEvery endpoint, and exactly what it returns.Tour of the universeWho lives in olympus-labs.