Skip to content

New paid orders and subscriptions are retired. Existing records, settlement and refunds remain available through your account.

Data directory

Cambridge TCG's public data directory. The directory needs no account or key; each entry names its own access requirement and limits.

Public reachability is not an open-data license. Only an exact resource that explicitly declares CC0-1.0 is CC0; mixed upstream responses are NOASSERTION, with known source tiers carried alongside their lineage.

The platform exists for the TCG economy — collectors, traders, agents, archivists, anyone who wants to read or participate. Not every participant needs an account. Not every observer wants to transact. This page lists both public and access-controlled surfaces and labels the requirement on each one.

24 shipped · 3 partial · 3planned. Counts as of page render; the surface grows. Status is substrate-honest — planned endpoints are named so the next builder knows what to ship; partial endpoints name what they don't yet cover.


What this is for

Public access and reuse permission are separate.Read each entry's authentication requirement, then inspect the response license and source-rights fields before redistribution, training, or commercial reuse.


Endpoints


Conventions

Versioning

The /api/v1/* prefix contains versioned public routes, including the universal-representation surfaces. Unprefixed paths such as /api/verify/* and /api/leaderboardsare older contracts. Shapes still vary between routes; use each entry's status and documented response rather than assuming one global contract.

Time

JSON timestamps are normally ISO 8601 strings. Only endpoints that say so also provide Unix epoch fields or distinguish @retrieved_at from @as_of. Older endpoints do not all carry those pairs.

Identity

Identifier shapes follow each endpoint's purpose. Card resources may use string SKUs, and math-mirror resources may include a SHA-256 hash of canonical public content. Public person and transaction projections omit internal account identifiers. Read the documented response shape; no identifier form appears on every response.

SKU format

Versioned card interfaces accept and emit the canonical SKU format: <game>-<set>-<number>-<lang>[-<variant>]. Lowercase, hyphen-separated, machine-parseable, language-aware. 22 public game codes are registered; 6 currently have catalog rows. Legacy stored and input forms still exist. Interfaces normalise them only where their documented resolver supports that form; do not assume every stored row conforms. See /methodology/sku-standard for the spec; canonical implementation is packages/sku/ in the monorepo.

Errors

The HTTP status is authoritative. Older routes may return a string inerror; envelope-based routes may return a structured code and message. Check the endpoint's documented shape before parsing it.

Rate limits

Limits differ by route, and not every public route publishes one yet. An absent number is not permission for unbounded traffic. The MCP gateway documents its own agent-key limit at methodology/agents.


How to ask for what isn't here

If you need data the platform has but isn't exposing:

  1. Check if it's under a planned endpoint above (most things are named in the planned set; that's the queue).
  2. Email [email protected] with the use case. There is no public issue tracker; the source repository is currently private.
  3. For agent access, a signed-in human can provision an operator-managed key at /account/agents. New self-serve registration is paused (see methodology/agents).

The platform commits to substrate honesty about what's open and what isn't. If something is planned here and isn't shipped yet, that's a real promise. Future builders consult this page when deciding what to ship next.


Source-of-truth for this page: docs/connections/the-open-substrate.md. Doctrinal frame: docs/principles/substrate-honesty.md + docs/principles/transparency.md. Companion welcoming: /methodology/welcoming. The door is open; the substrate is queryable; the door is warm to the touch.