ChaosDraft MTG Intelligence REST API wiki
This is the human-readable guide to the full current REST API, not only ASK AI. The OpenAPI 3.1 contract is authoritative for exact request and response schemas. The complete endpoint index lists every operation in the contract. API version: v1; contract version: 0.4.0 (2026-09-30 snapshot).
The documented API origin is https://api.chaosdraft.com. A route below that begins /v1 is called on that origin. These Markdown pages are the source for the customer-facing site at https://wiki.chaosdraft.com.
Start here
- Getting started — keys, scopes, response envelopes, pagination, errors, and a first request.
- Practical examples — copyable requests for chat, cards, decks, rules, events and pagination, marked by current key access.
- Choose an API area:
| Area | What it covers |
|---|---|
| Cards, sets and prices | Search, identity, printings, sets, stored prices, sources and status |
| Rules, formats and legality | Comprehensive Rules, glossary, rulings, format evidence and legality |
| Decks | Parsing, analysis, comparison, and API-stored deck versions |
| ASK AI | Chat, streaming, conversations, files, memory, feedback and live events |
| Events and stores | Official programs, local events and store listings |
| All endpoints | Every method/path, query parameter, required body field and current access |
Availability matters
The REST surface is wider than the routes currently available to an ordinary customer key. At this snapshot, a scoped key can use ASK routes with ask_ai, the one-card stored purchase route with card:purchase:read, and customer-wide feedback with ai:feedback:read when separately granted. Other /v1 routes require a privileged first-party * key. /health and /ready are public. Documented does not mean a customer key is entitled to that route or to every data field. Commercial source/field approvals and account entitlements are additional gates. See Getting started.
The older initial API specification describes design history and future phases; it is not the current route contract. Use this wiki and OpenAPI for integration. Future cross-product login and plan designs are not existing REST endpoints.