Scryfall
Scryfall is the most comprehensive free Magic - The Gathering card database. The Scryfall API exposes Cards (search, autocomplete, named, random, collection, by various IDs), Sets, Rulings, Symbology, Catalogs, Bulk Data downloads, and card-object Migrations. The service is community-funded (Patreon / Ko-fi) and offered free of charge under the Wizards of the Coast Fan Content Policy for community software, research, and content. The API is HTTPS-only, requires a descriptive User-Agent and Accept header on every request, and asks that clients keep sustained traffic under 10 requests per second.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Scryfall the way a machine reads it — 68 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Scryfall scores 61.8/100 (strong), with a separate agent-readiness read of 24/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Scryfall
Each block below is one kind of artifact we hold for Scryfall. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Scryfall API
The Scryfall REST API exposes Magic - The Gathering card data, set metadata, Oracle rulings, symbology, catalogs of in-game data points, daily bulk-data exports, and card-object...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Scryfall Rate Limits
RATE LIMITSFeatures 9
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Comprehensive card database
Every Magic - The Gathering printing across paper, MTGO, and Arena with localized translations.
Fulltext search query language
Powerful Scryfall search syntax supporting color, type, format legality, set, price, oracle text, and more.
Daily bulk-data exports
Five daily JSON exports - oracle_cards, unique_artwork, default_cards, all_cards, and rulings - for offline ingestion.
Multi-resolution card imagery
Six image renderings per card - small, normal, large, png, art_crop, border_crop.
Up-to-date market prices
USD / EUR / MTGO Tix pricing across normal, foil, and etched finishes.
Oracle rulings
Wizards of the Coast Oracle rulings plus Scryfall editorial notes per card.
Symbology with SVG renderings
All Magic mana and text symbols with parser endpoint and downloadable SVG art.
Catalogs of in-game data points
Canonical lists of card names, creature types, supertypes, keyword abilities, and more for autocomplete and validation.
Free with attribution
No API key, no paid tier - usage is governed by attribution and a documented rate-limit policy.
Scroll within the panel for all 9 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Scryfall Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Scryfall API Rules
SPECTRALScryfall API Rules
SPECTRALJSON Schema 14
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Scryfall Bulk Data
JSON SCHEMAScryfall Card Face
JSON SCHEMAScryfall Card
JSON SCHEMAScryfall Card Symbol
JSON SCHEMAScryfall Catalog
JSON SCHEMAScryfall Error
JSON SCHEMAScryfall Image URIs
JSON SCHEMAScryfall Legalities
JSON SCHEMAScryfall List
JSON SCHEMAScryfall Migration
JSON SCHEMAScryfall Prices
JSON SCHEMAScryfall Related Card
JSON SCHEMAScryfall Ruling
JSON SCHEMAScryfall Set
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 7
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Scryfall Bulk Data Structure
JSON STRUCTUREScryfall Card Structure
JSON STRUCTUREScryfall Card Symbol Structure
JSON STRUCTUREScryfall Catalog Structure
JSON STRUCTUREScryfall Migration Structure
JSON STRUCTUREScryfall Ruling Structure
JSON STRUCTUREScryfall Set Structure
JSON STRUCTUREScroll within the panel for all 7 ·
Examples 9
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scryfall Bulk Data Example
EXAMPLEScryfall Card Example
EXAMPLEScryfall Card List Example
EXAMPLEScryfall Card Symbol Example
EXAMPLEScryfall Catalog Example
EXAMPLEScryfall Error Example
EXAMPLEScryfall Migration Example
EXAMPLEScryfall Ruling Example
EXAMPLEScryfall Set Example
EXAMPLEScroll within the panel for all 9 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Deck building applications
Powering search, autocomplete, and legality checks in deck-builder web and mobile apps.
Price tracking and portfolio tools
Aggregating USD / EUR / Tix prices across reprints for collection valuation.
Discord and Slack card-lookup bots
Inline card images, prices, and rulings inside team chat channels.
LLM and AI agent integrations
MCP servers exposing card data, rulings, and search to Claude and other agents.
Research and dataset publishing
Bulk-data exports feed academic and journalistic research on Magic's design history and card economy.
Spoiler and set-release coverage
Tracking newly-spoiled cards into and through release day via the Sets and Cards endpoints.
Custom card-rendering and proxy printing
High-resolution PNG and SVG art for personal-use proxies and educational content.
Tournament-legality verification
Format-legality checks for Standard, Pioneer, Modern, Legacy, Vintage, Pauper, Commander, Brawl, Alchemy, and historic formats.
Scroll within the panel for all 8 ·
Integrations 10
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
TCGplayer
Cross-referenced card identifiers and purchase links via tcgplayer_id.
Cardmarket
Cross-referenced card identifiers and purchase links via cardmarket_id.
Cardhoarder
MTGO price feed integration and purchase links.
Wizards of the Coast Gatherer
Cross-referenced via multiverse_ids for canonical Oracle text.
Magic Online (MTGO)
Identifier mapping via mtgo_id and mtgo_foil_id.
Magic Arena
Identifier mapping via arena_id.
EDHREC
Commander-format recommendation data linked from card.related_uris.
Anthropic Claude (MCP)
Multiple community MCP servers expose Scryfall to Claude Desktop and other MCP clients.
Google Sheets
Official Scryfall =SCRYFALL() custom function for spreadsheet card lookups.
Alfred (macOS)
Official Scryfall Scion workflow for fast card search from Alfred.
Scroll within the panel for all 10 ·
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Community software
Powering thousands of fan-built deck builders, collection trackers, and tools.
Magic content creators
Source of authoritative card data and imagery for podcasts, articles, and video content.
Researchers
Bulk-data exports enabling longitudinal analysis of Magic's design and economy.
Resources
Every other property we hold for Scryfall — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 19
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 19 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/scryfall · machine-readable index on apis.io