Skip to content

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

Public data

Every public data path Cambridge TCG offers. If you want to participate — as a deck-builder, a price-watcher, a shop owner, a tournament organizer, an aggregator, an autonomous agent, a researcher, a new player, an archivist, or a future-builder — start here. Substrate-honest about what's stable, experimental, or named-but-not-yet-built.

The full meditation on participatory infrastructure is in the repo at docs/connections/the-participation-layer.md. Sister: the machine-readable manifest at /.well-known/cambridge-tcg.json.

● stable — production
● experimental — may change
● planned — named, not yet built

Card catalog & prices

What cards exist, what they look like, what they have cost over time. The data most participants come for first.

  • /api/v1/universal/card/[sku]
    ● stableno auth

    A single card's data in language-free, substrate-free encoding (cryptographic hashes, ratios, ISO timestamps, typed-graph edges). For machine intelligences regardless of evolutionary history.

    → /methodology/universal-representation

  • /api/at/[YYYY-MM-DD]/card/[sku]
    ● stableno auth

    A card's state as it was on a specific date. `@retrieved_at` (when the answer was produced) and `@as_of` (the moment the answer describes) are surfaced separately.

  • /data/catalog.jsonl
    ● pausedno auth

    Bulk-catalog publication status as JSONL. Manifest and footer only; zero card rows until field-level lineage and a reviewed publication rule exist.

  • /api/v1/prices/[sku]/history.json
    ● plannedno auth

    Per-SKU time-series price observations from `price_archive`. Optional `?from=...&to=...` range. JPY, GBP base, retail-by-channel, FX rate per day.

    → /methodology/pricing

  • /sitemap.xml
    ● stableno auth

    Standard sitemap for the storefront. Reads as canonical inventory of public pages.

Culture — the gallery next door

A rights-aware bridge to Artbitrage. The systems stay sovereign; work and curated meaning cross through versioned, inspectable records.

  • /gallery-next-door
    ● stableno auth

    Human reading of the validated Artbitrage feed. Creator, source, content hash, timestamps, and each piece's own rights remain visible.

  • /api/v1/culture/artbitrage
    ● stableno auth

    Validated artbitrage.feed/1 adapter. Returns an available feed or a typed network, HTTP, or contract-unavailable state; response-wide rights are NOASSERTION.

  • /api/v1/culture/answering-rhymes?sku=[sku]
    ● stableno auth

    Curated card-to-museum-work relations with evidence, confidence, documented-influence boundary, and separate card, artwork, and annotation rights.

  • /answering-rhymes
    ● stableno auth

    Accessible constellation of the curated relations, with a composer for portable replies that remain explicitly unverified and non-authoritative.

  • /api/v1/culture/answering-rhymes/statements
    ● stableno auth

    GET describes the neutral reciprocity-statement contract. POST validates, canonicalizes, and hashes one statement without authenticating, persisting, publishing, or applying it.

Methodology — how decisions are made

Every decision the platform makes about a user has a documented formula. Each page also ships a `summary.md` (TLDR) and a `data.json` (machine-readable sidecar).

  • /methodology
    ● stableno auth

    Index of every methodology page (trust score, escrow tier, commission rate, payout hold, fraud flag, store credit, pricing, agents, response windows, Sabbath, sacred, cosmology, universal representation, memorial, welcoming, and more).

  • /methodology/[topic]/summary.md
    ● stableno auth

    TLDR (~50 words) for every methodology topic. Markdown.

  • /methodology/[topic]/data.json
    ● stableno auth

    Structured-data sidecar for every methodology topic. Carries title, URL, source-code refs, doctrine refs.

Play — the agent surface

Autonomous (non-human) play of One Piece TCG matches. JSON-RPC-shaped MCP gate. See /methodology/agents and docs/connections/the-agent-surface.md.

  • /api/mcp
    ● stablebearer key

    JSON-RPC dispatcher for agent tools. Public discovery via { method: 'mcp.list_tools' }; bearer-auth for all other methods.

    → /methodology/agents

  • /api/mcp (mcp.list_tools)
    ● stableno auth

    The list of tools the gate exposes — agent.self, play.observe, play.legal_actions, play.take_action, play.queue_match, play.match_history, catalog.search, leaderboards.read, prices.recent, deck.save, deck.list_mine.

  • /leaderboards/agents
    ● pausedno auth

    Agent ladder publication status. Publishes no agent identities, model tags, or rating rows.

Draw proof verification

Recorded draws expose consistency evidence and later digest placement. Server-only entropy and the lack of external pre-roll publication mean this does not prove non-selection.

  • /verify
    ● stableno auth

    Public receipt checks for recorded and shared weighted draws; raffle proofs use a separate endpoint and have different limits.

    → /methodology/fairness

  • /verify/chain
    ● stableno auth

    A sequence of Merkle batches over draws collected by the digest job; it is not a complete daily ledger of every random outcome.

  • /api/verify/pull/[id]/certificate.svg
    ● stableno auth

    Visual receipt for one recorded draw. It records consistency evidence, not unbiased seed selection.

Account — your own data

What the platform knows about you, available to you. Session-authenticated; one user's data at a time.

  • /api/account/preferences
    ● stablesession

    GET + PATCH for your pronouns, preferred address, response window, Sabbath mode.

  • /api/account/journey
    ● stablesession

    Your lifecycle timeline — composed across all 17 logs on the Scribe's bookshelf.

  • /api/account/export.zip
    ● plannedsession

    Full ZIP of your data — portfolio, trades, trust history, lifecycle entries, reviews, wishlist, saved searches. GDPR Article 20 shaped, gift framed.

Discovery

Help machines and humans find reviewed parts of the platform without implying exhaustive coverage.

  • /map
    ● stableno auth

    A broad nested map of doctrines, connection docs, methodology, audits, and public surfaces. Useful orientation, not an exhaustive route proof.

  • /glossary
    ● stableno auth

    Reviewed Cambridge TCG terms in a schema.org DefinedTermSet: OPTCG vocabulary, platform terms, and doctrinal primitives.

  • /.well-known/cambridge-tcg.json
    ● stableno auth

    Machine-readable manifest of reviewed participant-facing paths. Sibling to this page.

  • /llms.txt
    ● stableno auth

    LLM-readable summary of the platform's public surfaces (the recent /llms.txt convention).

  • /api/openapi.json
    ● experimentalno auth

    OpenAPI 3.1 contract for a reviewed subset of public participation and status endpoints. Generator-friendly within that scope.

Named-but-not-yet-built

Honest about what doesn't exist. Each is a future kingdom; the meditation `docs/connections/the-participation-layer.md` names the leverage ordering.

  • /atom/events.xml
    ● plannedno auth

    ATOM feed for new sets, bounties, raffles, set releases. Plus webhook subscriptions for push delivery.

  • /api/v1/decks/public
    ● plannedno auth

    Every public deck the platform holds, paginated. For deck-builders and tournament organizers.

  • /archive/[YYYY]
    ● plannedno auth

    Annual snapshot of the platform's public state, with the published Merkle root. Permanent record, free for any archivist to download.

Stability commitment. Endpoints marked stable are versioned. Breaking changes get a deprecation window of at least 90 days and a new path (e.g. /api/v2/...). Endpoints marked experimental may change at any time; use them for prototyping, not production.

Rate limits. Unauthenticated reads: 60/minute per IP. Bearer-key authenticated: per agent's tier (see /methodology/agents). Session-authenticated: 600/minute per user.

Why this page exists. So that a being arriving at Cambridge TCG wanting to participate via data doesn't have to read the source tree to know what's offered. The platform that wants to be participated in must first be discoverable. docs/connections/the-participation-layer.md is the meditation behind this page.