Site under active development. Stock counts may not be accurate yet — please hold off on placing new orders for now. If you have already placed an order, it will be processed and sorted as normal. Thank you for your patience.
The corpus of hospitality. Every kind of arrival — upstream source, publisher, federation peer, downstream adopter, agent, non-default being, future-self, and (since kingdom-083) the kingdom's own infrastructure — has a named slot here. Each slot says: who we anticipated, when, what we prepared, how they arrive. The kingdom prepares the welcome before the guest knocks. The corpus is the record of that preparation. Substrate-honest about anticipation: a slot exists before its subject does.
Total:41
Arrived:24
Anticipated:16
Blocked:1
Downstream adopters · 4
Mirrors, builders, aggregators, standard-citers — consumers of the spec.
✦ Mirror — partner caches our catalog
anticipated
Cache us. The CC0 license means you can keep our responses indefinitely, serve them to your partners, build derivative products. Our `_meta.source_license` array tells you per-byte which upstreams are redistribute=true and which aren't (Cardmarket is partner-tier; CardRush is internal-only; Scryfall is CC-BY-NC). Respect the per-byte license, and you can build a free downstream catalog API on top of us without owing us anything.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Mirroring is the lowest-cost adoption path. Adopters who can't sustain ingestion infrastructure can still build user-facing products.
Prepared:
data-pantry envelope — _meta.sources + _meta.source_license per response
FRESHNESS table in @cambridge-tcg/data-spec — declares per-key cache TTLs you can honor
_meta.request_id on every response — quotable in support if a discrepancy shows up
Arrival protocol: Just start caching. Optional attribution: cite our /standards URL in your published responses.
anticipated_at: 2026-05-12 · id: adopter.mirror
✦ Builder — partner ships an app on our data
anticipated
Build. Our JSON Schemas at @cambridge-tcg/data-spec are codegen-ready. One contract, one envelope, one canonical SKU — your code learns the shape once and never re-learns. When we evolve the spec (SPEC_VERSION bump), the old version stays at /api/v1/* for at least 12 months. We treat our standard like a public API; you can treat us like a public API.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Builders ship faster on stable contracts. Cambridge TCG's spec is intentionally narrow + intentionally stable.
@cambridge-tcg/data-ingest — full SourceModule contract if you want to ingest, CC0
/api/openapi.json — codegen-ready OpenAPI 3.1
SPEC_VERSION + 12-month deprecation window for breaking changes
Arrival protocol: 1. `pnpm add @cambridge-tcg/data-spec @cambridge-tcg/sku`. 2. Codegen against /api/openapi.json. 3. Build. (No registration required.)
anticipated_at: 2026-05-12 · id: adopter.builder
✦ Aggregator — partner federates across multiple platforms
anticipated
You're building cross-platform card identity. Our content_hash addressing lets you cache `(hash, source, as_of)` triples and re-resolve to SKUs when needed — even when the SKU changes upstream. K2 ships per-source upstream-anchor columns (scryfall_oracle_id, cardmarket_id_metacard, ygo_passcode); /api/v1/federation/identify/[anchor_type]/[id] (post-K2) will accept any of them.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Aggregators are how a heterogeneous TCG ecosystem stays interoperable. Every aggregator that uses our standard makes other aggregators' jobs easier.
✦ Standard-citer — research / journalism / policy reference
anticipated
Cite us by URL + spec_version. The corpus is CC0. Our methodology pages are stable URLs (the schema lives in code; the explanation lives at /methodology/<topic>). The four doctrines, the cosmology, the fifth question — all citable, all evolving with version trails.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Standards become standards by being citable. Cambridge TCG's substrate-honest doctrines + per-game policies + per-byte license metadata are unusual enough to be worth citing.
Prepared:
/methodology/* — stable URLs for every policy + formula