Public
main142 commits
01 / The sandbox org
There's no empty state — the universe arrives full. Meet Olympus Labs, a Greek-myth-themed engineering org where every name, team, and commit is real, fetchable data.
1
Repository
4
Teams
16
Team seats
142
Commits
7
Entry points
21
APIs
Every figure and link on this page is taken from the frozen snapshot host gh-2026-03.snap.sandboxapis.dev, so each one resolves forever. The live host serves the same org but re-rolls daily — new commits, new pull request numbers.
02 / Browse the universe
Or jump straight in — real responses captured from the pinned hosts at build time, cross-provider included. Each opens right here, and each resolves forever.
One thing the explorer above is not: a provider list. Its three tabs browse repositories, teams and entry points — GitHub's shapes, on the GitHub pin — and the cards beneath them are a handful of cross-provider deep links chosen to show the same org from another angle, not a catalog. Since the CORS ruling of 2026-09-03 every pin host answers a browser, so each of those cards opens right here on its own host rather than in a new tab; what stays GitHub-only is following a reference out of a response, because the followable-path vocabulary is GitHub's and no other provider's has been enumerated yet. On a non-GitHub response the references render as plain text — which is the honest outcome, not a thinner universe underneath. All 21 providers serve this same story just as fully from curl, an SDK or MCP, and every one of them is listed at /providers.
03 / Where the story gets discussed
An incident here isn't only a tracker issue and the pull request that closed it. It is also an argument in #incident-bridge — 16 messages across 10 people, opened minutes after the issue was filed and resolved by the time it closed. The burst sits inside the issue's own open→done window because the chatter is derived from the canonical event stream, not written alongside it.
Two hosts serve that conversation from one artifact. Slack calls the prose text on a message keyed by a ts; Microsoft Graph calls it body.content on a message keyed by epoch millis. Neither is a translation of the other — run both:
# Slack's dialect: the thread's opening message, keyed by its `ts`.
curl -s "https://slack-2026-08.snap.sandboxapis.dev/api/conversations.history?channel=CF1UPUMGC8Q&limit=2"
# Microsoft Graph's dialect: the same message in the same channel, keyed by
# epoch millis — served from the same artifact, so the prose is the same prose.
curl -s -H 'Authorization: Bearer any-token' \
"https://teams-v1.snap.sandboxapis.dev/v1.0/teams/31837fb8-c814-42ba-8775-01dedad6c921/channels/19%3Ae5b377c202622bec6934aec07c160755%40thread.tacv2/messages?$top=2"Both answer with the same first line, to the byte:
schema marks a nullable field as required. paging whoever's closest to the logger.And the walk keeps going — without leaving the frozen universe. That thread opened 8 minutes after FATE-46 was filed on the trackers; the issue was closed by a merged pull request; that pull request merged the branch clio/leak-http-client-keep-alive-pool; and both git dialects report the same head SHA, d2aa02c65f19. Each hop is a snapshot host, so each link resolves to those same bytes forever:
Linear tells the same story in its own shape — it serves FATE-46's branchName as clio/leak-http-client-keep-alive-pool, the branch that pull request merged — but its API is GraphQL over POST, so it is a query rather than a link. All 13 APIs with a pin in this generation share one artifact, which is what makes a conversation → issue → pull request → SHA walk pinnable at all: until those pins existed, only the messaging hosts were frozen on this universe and the rest of the walk could only be taken on the live hosts, which re-roll daily.
04 / Start testing
The live universe re-rolls every day — yesterday's commits, a PR that merged this week. Need it frozen for CI? Pin a snapshot and it regenerates byte-identically on every request.