Data and API

Everything an index is made of is public, and the number the DEX trades against is the same number anyone can read. This page is for people who want to pull that number into code, chart it or check it.

What is public

For every published index:

• The level, together with the date it refers to.
• The history: every level of the index from its May 2004 base to the latest date.
• The constituent list: each card at its grade and grader, as it stands today and as it stood after each past review.
• The dictionary: the fixed mapping from each vaulted card's token to its grader, grade, set and number, resolved once and never edited afterwards.
• The commitments: a Merkle root over the inputs, published at regular intervals, so the data behind any past level can be checked for tampering. Each index's specification names where its commitments are anchored, so every root sits somewhere nobody can quietly rewrite.
• The specification: the formula, thresholds and parameters, versioned over time, together with the venues whose on-chain records the index reads.

Quanta indexes are built from real sales. Card Ladder sales data powers the 44-index board, its levels and its full history, and the public on-chain record of vaulted card sales is the settlement layer the index engine reads and anyone can verify. One engine feeds three outputs: the JSON feed the site reads, the history archive used for recomputation, and the oracle feed for the DEX. All three carry the same number, and the site displays it rather than computing anything itself.

The public feed

The feed is read-only JSON over HTTPS, with two endpoints.

Board snapshot

GET https://tradequanta.xyz/api/indexes

Returns the whole board: an asOf date and an indexes array with one entry per index.

Field	Meaning
id	Index id, used in the history endpoint (for example pokemon)
ticker	Board ticker (for example PKMN, MTG, BSBL)
name	Index name
level	Current level in raw points
cards	Number of cards in the index
change1d, change1m, change3m, change1y, changeAll	Change over one day, one month, three months, one year and since the base date, as a fraction (0.0254 is +2.54%)
description	Short description of the index, where it has one

Index history

GET https://tradequanta.xyz/api/indexes/history/<id>

Returns one index's full history: its id, an asOf date and a series of [date, level] points, for example /api/indexes/history/pokemon.

A trimmed board response looks like this:

{
  "asOf": "2026-10-05",
  "indexes": [
    {
      "id": "pokemon",
      "ticker": "PKMN",
      "name": "Pokémon",
      "level": 152276.99,
      "cards": 9609,
      "change1d": 0.004749,
      "change1m": 0.42885,
      "change3m": 0.76107,
      "change1y": 3.35612,
      "changeAll": 151.27699,
      "description": null
    }
  ]
}

Units. Levels are raw points. Divide by 1,000 to get the dollar figure shown on the board: every index starts at 1,000 points, or $1.00, in May 2004, so a level of 152,276.99 reads as $152.28.

Freshness. The data refreshes daily, and responses are cached for five minutes.

The site reads this feed and the DEX reads the oracle feed below, which carries the same level. What you see on the site, what you fetch from the feed and what the matching engine prices against all come from one source.

The oracle feed

The DEX receives the index price from Quanta's oracle at least once per second, sent by redundant publishers with median guardrails across sources (Market safeguards). The oracle delivers the same level the public feed serves; it is a delivery channel, not a second calculation. The cadence is high because the matching engine always works from a fresh price, not because the index moves that quickly.

Recomputing an index

The specification is written so that anyone can rebuild the level from public data. The check, which the specification spells out for each index, runs like this:

1. Pull the index history for the period you want to check from /api/indexes/history/<id>, along with the dictionary and constituent list in force over that period.
2. Read the on-chain sales record of vaulted cards from the venues the specification names, over the window it defines, and match each sale to its constituent through the dictionary.
3. Apply the specification: selection, cleaning, aggregation, scaling and smoothing, in its stated order and with its stated parameters.
4. Compare your levels with the published history, and your inputs with the published commitments.

A recomputation that matches is the strongest evidence an index can give, and it is evidence you produce yourself instead of taking our word for it.

Using Quanta data

Quanta index levels and history are free to display, quote and analyze, with attribution to Quanta and a link to the index page on tradequanta.xyz. Quote each level with its date, since a level means most next to the day it describes. For products that resell or embed the feed, contact us about commercial licensing.

For the terms used on this page, see the Glossary. For what each part of the method protects against, see Methodology principles.