YGOPRODeck
YGOPRODeck is a community-run Yu-Gi-Oh! TCG database and deck-sharing platform that exposes a free, public REST API (v7) for querying every Yu-Gi-Oh! card, archetype, card set, banlist status, format legality, market price, and card image. The API is the canonical open data source used by community deck builders, mobile apps, Discord bots, simulators, and analytics tools across the Yu-Gi-Oh! ecosystem.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles YGOPRODeck the way a machine reads it — 56 machine-readable artifacts across 5 APIs, 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 — YGOPRODeck scores 37.7/100 (thin), with a separate agent-readiness read of 39/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile YGOPRODeck
Each block below is one kind of artifact we hold for YGOPRODeck. 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 5
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.
YGOPRODeck Archetypes API
Recognised Yu-Gi-Oh! archetype catalog.
YGOPRODeck Card Sets API
Yu-Gi-Oh! card set catalog and per-print details.
YGOPRODeck Cards API
Card search, filtering, and metadata retrieval.
YGOPRODeck Database API
Database version and freshness information.
YGOPRODeck Reference Data API
Valid value enumerations used by the search engine.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
YGOPRODeck Yu-Gi-Oh! Card Database API
OPEN COLLECTIONSemantic 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.
Yu Gi Oh Ygoprodeck 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.
YGOPRODeck API Rules
SPECTRALYGOPRODeck API Rules
SPECTRALJSON Schema 15
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.
Archetype
JSON SCHEMACardClassValues
JSON SCHEMACardImage
JSON SCHEMACardMiscInfo
JSON SCHEMACardPrice
JSON SCHEMACardPrintingEntry
JSON SCHEMACard
JSON SCHEMACardSearchResponse
JSON SCHEMACardSetPrint
JSON SCHEMACardSet
JSON SCHEMACardTypeEntry
JSON SCHEMACardValues
JSON SCHEMADatabaseVersion
JSON SCHEMAMonsterValues
JSON SCHEMASearchMeta
JSON SCHEMAScroll within the panel for all 15 ·
JSON Structure 15
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.
Ygoprodeck Api Archetype Structure
JSON STRUCTUREYgoprodeck Api Card Class Values Structure
JSON STRUCTUREYgoprodeck Api Card Image Structure
JSON STRUCTUREYgoprodeck Api Card Misc Info Structure
JSON STRUCTUREYgoprodeck Api Card Price Structure
JSON STRUCTUREYgoprodeck Api Card Printing Entry Structure
JSON STRUCTUREYgoprodeck Api Card Search Response Structure
JSON STRUCTUREYgoprodeck Api Card Set Print Structure
JSON STRUCTUREYgoprodeck Api Card Set Structure
JSON STRUCTUREYgoprodeck Api Card Structure
JSON STRUCTUREYgoprodeck Api Card Type Entry Structure
JSON STRUCTUREYgoprodeck Api Card Values Structure
JSON STRUCTUREYgoprodeck Api Database Version Structure
JSON STRUCTUREYgoprodeck Api Monster Values Structure
JSON STRUCTUREYgoprodeck Api Search Meta Structure
JSON STRUCTUREScroll within the panel for all 15 ·
Examples 15
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.
Ygoprodeck Api Card Example
EXAMPLEScroll within the panel for all 15 ·
Security Posture 1
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for YGOPRODeck — 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.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/yu-gi-oh · machine-readable index on apis.io