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

# Roadmap

Honest and demand-driven: paying integrators reorder this list. Dates are directions, not promises.

## Now → next quarter

**Coverage (the compounding asset)**

* Complete the full-history sweep of Collector Crypt (\~67k tokenized slabs, every venue, back to 2023) — running perpetually, chunk by chunk.
* Phygitals: full-sweep verdict (discovery and mapping already live).
* More EVM venues through the generic connector (Polygon / Ethereum / Base — any collection with standard marketplace settlement is one config entry).
* eBay sold-comps via the official partner API (application in progress) — the single biggest realized-coverage unlock for raw cards.

**API surface**

* Bulk pricing endpoint (many series per call) — first Partner request wins.
* Webhooks: "value moved > x%", "new realized sale for series".
* Self-serve key signup + usage dashboard.
* x402 pay-per-call GA (USDC micro-payments, agent-friendly).

## Mid-term

**Analytics products**

* Per-card **gem premium** (raw ↔ PSA-10 curves): the "should I grade this?" number, per card and per set.
* Market indices (e.g. vintage-Pokémon-PSA10 index) as subscribable feeds.
* Liquidity scores: how fast does this card actually trade, at what spread?

**Trust & attestation**

* EVM attestor (same root posted to Base/Polygon — the attestation layer is chain-agnostic by design, this is config, not a rewrite).
* Enforcement-grade feed option for financial partners: freshness SLA, hardened attestation — the upgrade path from "reference" to "trigger".

**Signal quality**

* Wallet-graph wash-trade detection (beyond the current self-trade guard).
* Cert-number → card mapping (PSA/CGC lookups) for near-perfect graded identification.
* Publisher program: signed realized sales from partner sellers (Pyth-style), with reputation weighting.

## Long-term

* Full standalone deployment (the oracle already lives behind its own namespace and client boundary; extraction is an ops move, not a refactor).
* More TCGs — the engine is game-agnostic; each addition is a catalog + connector, not a new system.
* On-chain consumable feed (a program/contract serving the latest anchored values) — when a settlement-grade consumer justifies it.

***

**Follow progress:** [Discord](https://discord.gg/Hj5RstMUU) · [X / Twitter](https://x.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/project/roadmap.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.