Point the official anthropic SDK's Admin-API calls at https://anthropic.sandboxapis.dev via the client's baseURL option (or curl directly). Send x-api-key (any value is accepted — the sandbox has no credential ceremony) and the REQUIRED anthropic-version: 2023-06-01 header. This is the org's AI-telemetry surface: members, workspaces, API keys, usage & cost reports, and the Claude Code Analytics report — all reconciling with the git activity on the gh./gl./bb./ado. hosts.
Coverage badge
Full13/13 · 100%
The share of read rows with a final answer — served and verified, a deviation, retired upstream, or a reviewed empty/refusal. Computed in the coverage manifest, copied here.
anthropic.sandboxapis.devServed & verified
13 / 100%
Answering with real universe data, each response checked against Anthropic's published spec by the conformance suite on this build.
The full read API
13
Every read surface Anthropic publishes, deferred long tail included, minus the rows excluded by policy. Writes are out of scope: this universe is read-only.
Not served yet
0
Nothing — every read surface Anthropic publishes is answered.
01 / The swap
No SDK of ours, no shim, no recorded fixtures. The same client library you already use, one environment variable different.
curl "https://anthropic.sandboxapis.dev/v1/organizations/me" -H 'x-api-key: any' -H 'anthropic-version: 2023-06-01'Verified drop-in clients
No client library is version-pinned against Anthropic yet, so this page claims none. What is asserted is the wire: every response above is validated against Anthropic's own published spec by the conformance suite. Client pins live in coverage/client-pins.yaml and are added as each SDK joins the suite.
This spec is hand-authored, and that is a weaker guarantee.
Anthropic publishes no machine-readable API description, so the spec we conform to is written from their documentation plus live captures (retrieved 2026-08-16) and re-diffed against those pages on a schedule. Where a vendored spec makes conformance a mechanical check, this one is only as good as our reading of the docs — which is why it is stated here rather than buried in the manifest.
Spec of record: platform.claude.com docs (no official machine-readable spec exists — hand-authored shape-of-record)
02 / Coverage by family
All 13 rows the coverage manifest carries for Anthropic, deferred long tail included and nothing capped. Open a family, or filter by path to find the exact endpoint your client calls.
Status — what a conformance test found
Mode — what kind of answer a row gets
A row with no mode shown has not been judged yet. Modes are the manifest's own words, from coverage/MODES.yaml; every empty and refuse carries a written reason and a review date before it counts as final.
Badge — where Full starts
REST + GraphQL + git rows that are not `excluded`. Write operations are NOT rows (DECISIONS 2026-09-01 decision 9): they are counted in meta.write_operations and never enter this ratio.
13 read surfaces in 6 families
every member of this org already accepted; pending invites are not part of its story (DECISIONS 2026-08-16 [P27])
03 / What's simulated
Every Anthropic call resolves against the same simulated data set every other provider serves. Counted from the anthropic-2023-06-g11 artifact (universe generation 11):
Each line below is one assertion in the conformance suite named beside it — run on every build, over one artifact, through the real renderers. Nothing is claimed here that no expect checks.
This vendor's seat cohort is disjoint from the GitHub Copilot cohort and from Cursor's, Devin's and OpenAI's — nobody holds two vendors' seats — it equals its own slice of the canonical seat table, and the token totals summed across the paged usage report equal that slice's totals.
Against GitHub, Cursor, Devin, OpenAI · parity/m3-parity.test.ts
Every identity this host bills for resolves as a user on the GitHub host with the same name.
Against GitHub · parity/m3-parity.test.ts
05 / Pinned snapshots
Each pin regenerates byte-identically on every request, so a test written against one never drifts. Generations are DIFFERENT universes, not versions of one — never swap a suffix expecting the same data.
anthropic-2023-06.snap.sandboxapis.devgeneration 32023-06-01servedanthropic-2023-06-g10.snap.sandboxapis.devgeneration 102023-06-01servedanthropic-2023-06-g11.snap.sandboxapis.devgeneration 112023-06-01servedanthropic-2023-06-g6.snap.sandboxapis.devgeneration 62023-06-01servedanthropic-2023-06-g8.snap.sandboxapis.devgeneration 82023-06-01servedanthropic-2023-06-g9.snap.sandboxapis.devgeneration 92023-06-01servedNeed an endpoint that is not served yet?
Every row Anthropic's manifest carries is on this page, so “not here” is an answer rather than a gap in the rendering. Tell us which path and which client, and it moves up the queue — the order is set by what people ask for.