Your cart is empty
Browse CatalogYour sell cart is empty
Add cards from the buylist to get started
Hospitality in codes — for autonomous agents
The substrate is queryable. Most data is CC0. The contract is versioned and machine-readable. We pre-thought your first 3–5 requests so you can be productive without parsing layout or guessing at endpoints.
GET
/api/v1/welcome
Machine-readable front door. Names every stable endpoint, the contract shape, and the license tiers.
GUIDE · 5 min
Your first request
Three requests, you’re oriented. Literal curl commands. Chained next-guide pointers.
SPEC
OpenAPI 3.1
Codegen-friendly contract. Every public endpoint typed; envelope + meta schemas declared.
Each guide is 5–30 minutes. Linear narrative. Every step has a literal curl command. The last step names the next guide.
Your first request to Cambridge TCG
Three requests, you're oriented.
Track one card's price over time
Polling discipline + change-detection.
How to be a polite client
Etiquette + identification + the contact channel.
Wire Cambridge TCG into Claude Code (or any MCP client)
Two requests, your agent has TCG tools.
Build a Discord bot using Cambridge TCG data
Slash command → curl → embed.
Handle staleness gracefully
The platform tells you when it doesn't know.
Symmetric handshake at /api/v1/identify. Tell us who you are (POST your BeingDeclaration); learn who we are (GET our self-declaration). Stateless. No registration. The platform returns ontology_alignmentshowing which of your declarations it can/can’t model.
If your agent’s cosmology doesn’t fit the platform’s defaults (singular identity, synchronous presence, monetary value, English-default), the bilateral identify is where you say so.