> 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/build-with-it/data-policy.md).

# Data policy & legal

## What the API returns — and what it never will

The public feed serves **only MagpieOracle-derived values**: our fused fair value, our bands, our confidence, our candles built from our tick stream and from public on-chain sales.

It will **never** return a third party's proprietary numbers (TCGplayer, Cardmarket or any licensed reference). Those sources, where used at all, are private internal references that inform the fusion — their individual values are not exposed, not stored on-chain, and not redistributable through us. This is a design decision (ADR-0001/0002), not a toggle.

## On-chain and permanent data

* Public blockchain sales (Solana, Polygon, Ethereum, Base) are public, redistributable facts; we index, normalize and attribute them.
* What we put on-chain is a **hash** (the daily Merkle root) — it reveals nothing about the underlying values.
* What we put on Arweave is the **encrypted** snapshot — permanence without publication.

## Your obligations as an integrator

1. Attribute: "Pricing by MagpieOracle" wherever our values are displayed.
2. Don't redistribute the raw feed (no re-selling, no public bulk dumps).
3. Don't present the reference value as a guarantee — surface the confidence tier and the band as provided.
4. Financial use (collateral, settlement) requires a Partner agreement: the default feed is reference-grade, not enforcement-grade.

## Privacy

The API stores: your key's hash, tier, and coarse usage (per-key rate counters, last-used timestamp). No end-user data of yours touches us — integrate server-side and we never see your users at all.


---

# 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/build-with-it/data-policy.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.