Pin it once. The data never drifts.

01 / Two modes

Live vs. snapshot.

• Live — the gh. / slack. / sentry. / circleci. / zendesk. / gl. / bb. / ado. / jira. / linear. / anthropic. / cursor. / devin. / openai. / chatgpt. / graph. / pd. / sf. / hubspot. / buildkite. / statuspage. / antigravity. / prom. / grafana. / api. hosts serve a continuously-fresh universe (newest activity within a day). Great for exploration.
• Snapshot — a pinned *.snap. host serves a reproducible universe that regenerates byte-identically on every request. Great for CI.

02 / Pinning

It's a hostname swap.

Point your client's base URL at a snapshot host instead of the live host — nothing else changes.

# One pin, one base URL. Every other pin is the same swap.
export GITHUB_BASE_URL=https://gh-2026-03-g12.snap.sandboxapis.dev

# The whole list, machine-readable:
curl -s https://api.sandboxapis.dev/v1/snapshots

Pins come in generations. A generation is a whole pinned universe, not a feature flag: generation 2 (the -g2 hosts below) serves repository files; generation 1 predates them. The two hold different data — different issue keys, different commit SHAs — so pick one and stay on it. The table below groups every pin by provider, and the generation filter answers the question people actually arrive with: give me every host on one generation.

03 / Available pins

Snapshots you can use today.

Discover pins programmatically at GET https://api.sandboxapis.dev/v1/snapshots, or via the MCP get_snapshot tool.