> For the complete documentation index, see [llms.txt](https://oracledocs.magpie.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oracledocs.magpie.gg/readme.md).

# Introduction

**MagpieOracle is a price oracle for trading cards** — Pokémon, Magic: The Gathering and One Piece today, more to come. For every card, raw or graded, it serves one thing: *a fair value you can actually defend* — with a band, an honest confidence level, and a history that is anchored on-chain so nobody (including us) can quietly rewrite it.

{% hint style="info" %}
**In one line:** realized sales lead, asking prices only fill the gaps, every number ships with its own uncertainty, and the whole history is verifiable on Solana mainnet.
{% endhint %}

## The problem with card prices

If you've ever tried to price a card seriously, you know the landscape: sellers' *asking* prices dressed up as market value, closed aggregates you can't audit, and historical charts you simply have to take on faith. It works until real money depends on it — a trade, a loan against a slab, an insurance valuation — and then it doesn't.

MagpieOracle was built the other way around, on four rules:

1. **Realized sales lead.** Where real settled sales exist — the public, on-chain sales of tokenized graded cards, and first-party marketplace deals — they drive the value. Asking prices are a floor estimate, weighted accordingly, never the headline.
2. **A band, not a point.** Every answer is `fair value + low..high + confidence + how many sales back it`. Thin data says so, loudly. `available: false` is a possible answer, and we prefer it to a guess.
3. **Verifiable, permanently.** Each day's published prices are frozen into a Merkle root posted on **Solana mainnet**, with the encrypted snapshot archived on **Arweave**. A price shown at loan origination can be *proven* months later.
4. **Self-graded, in public.** A walk-forward backtest scores every published value against the sales that came after it, and the error metrics are a free, keyless endpoint. To our knowledge, no other card-pricing provider publishes its own accuracy.

## What you can pull from it

| Endpoint                    | What it gives you                                                                    |
| --------------------------- | ------------------------------------------------------------------------------------ |
| `GET /price`                | fair value (raw) or gem value + per-grade breakdown (graded), with band & confidence |
| `GET /candles`              | finance-style OHLC candles — 1h · 4h · 1D · 1W                                       |
| `GET /history`              | the daily fair-value series                                                          |
| `GET /cards`                | resolve names & collector numbers to card ids                                        |
| `GET /accuracy`             | our public error metrics *(keyless)*                                                 |
| `GET /batch` · `GET /proof` | daily Merkle roots, on-chain attestations, inclusion proofs *(keyless)*              |

## Who's already on it

* [**Magpie**](https://magpie.gg) — the collection & P2P trading app. Every price, chart and candle in the app is oracle-served.
* **SlabX** — the Solana protocol for tokenized graded cards, using the oracle as its reference-pricing layer for series values and lender due diligence.

MagpieOracle is a standalone product: it powers Magpie, it doesn't depend on it. If you're building anything that needs card prices — an app, a marketplace, a dashboard, an AI agent — start with the [API reference](/build-with-it/api-reference.md) and the [free tier](/build-with-it/pricing.md).

***

**Find us:** [magpie.gg](https://magpie.gg) · [Discord](https://discord.gg/Hj5RstMUU) · [X / Twitter](https://x.com/magpiedotgg) · [Instagram](https://www.instagram.com/magpiedotgg)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://oracledocs.magpie.gg/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.