> 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/project/faq.md).

# FAQ

**How is this different from PriceCharting or the closed aggregates?** On breadth, they win today — years of history on nearly every card. Our difference is the *nature* of the data: realized on-chain sales anyone can audit, a published error metric, bands and confidence instead of a bare number, and a history that's cryptographically anchored. We'd rather be honest and verifiable on fewer series than opaque on all of them — and coverage compounds weekly on a perpetual sweep.

**Which games are covered?** Pokémon, Magic: The Gathering and One Piece — a catalog of \~170,000 cards that syncs itself with new sets and late-added promos. Adding a TCG is a catalog-and-connector job, not a new engine.

**Where does graded coverage come from?** Tokenized-card venues, led by Collector Crypt (full per-slab sale history back to 2023, all Solana venues), with Phygitals wired and any standard-settlement EVM venue pluggable. Values break down per grading company and grade where sales exist.

**Why does a card return `available: false`?** Because we don't have enough signal for that variant and we refuse to guess. Treat it as "no reference yet" — never as zero.

**What currency are values in?** EUR — the fair value is EU-market-led. Convert client-side and label it.

**Can I use the feed to trigger liquidations or settlements?** Not the default feed — it's reference-grade by contract. Enforcement-grade feeds (freshness SLA, hardened attestation) are a Partner conversation; see the [roadmap](/project/roadmap.md).

**What happens to the data if MagpieOracle shuts down?** The daily roots stay on Solana mainnet and the encrypted snapshots on Arweave, permanently. The history remains provable without us — that's the point of the anchoring.

**Is verification really free?** Yes, forever: `accuracy`, `batch` and `proof` are keyless by design. Trust must never sit behind a paywall.

**How fresh are the values?** Tracked series refresh hourly; the full catalog rotates on a daily baseline; realized sales land as they're indexed. A cold value computes live in \~1–2s.

**I found a wrong price. What do I do?** Tell us on [Discord](https://discord.gg/Hj5RstMUU) with the card and timestamp. Mis-mapped sales are fixable at the source (the mapping is cached, corrections propagate) — and the accuracy metric will show the improvement, publicly.


---

# 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/project/faq.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.