The facts are scattered
The EU register says one thing, the issuer's own disclosures another, and the market a third. Each lives on a different surface, in a different format, maintained by a different party.
Verifiable stablecoin evidence
Stablecoin decision infrastructure.
FeedOracle turns fragmented stablecoin disclosures and market signals into structured, timestamped evidence your systems can use — while the final decision stays with your policy.
Built for fintech product teams, compliance operations, treasury & risk, and developers of autonomous agents.
GET
api.feedoracle.io/api/v3/stablecoin/mica/USDC
- StablecoinUSDC — USD Coin
- IssuerCircle Internet Financial · Ireland (EU)
- RegisterEvidence found
- Reserve attestation dateEvidence gap
- Peg (USD, defillama)0.99970642…
- RedemptionIssuer-reported
- Content hashSHA-256 · d447a393…0fa9d31c
Captured snapshot · observed 2026-08-19T11:08:16Z · not a live feed. Full record on the preflight page.
01 · The problem
A token list is not a basis for a decision.
Teams that list, accept or hold stablecoins need more than a name and a blanket verdict. They need to know what was found, where, and when — and what was not found.
The facts age at different speeds
A peg observation is minutes old; a reserve attestation can be months old — or carry no date at all. A decision record that hides this difference hides the risk.
The facts are not machine-usable
Registers and disclosures are written for people. An automated system needs named fields, an explicit status vocabulary and a validity window it can act on.
And one distinction is non-negotiable
Data, policy and legal judgment are three different things. Evidence states what a named source showed at a named time. Policy is how you classify that evidence. The legal determination belongs to qualified professionals — not to a data feed, and not to FeedOracle.
02 · How it works
Query an asset. Receive evidence. Derive your own result.
Ask about a stablecoin
One read-only request for the asset in question. The stablecoin preflight endpoint answers over plain HTTPS with structured JSON.
Receive structured evidence
Register status with the naming authority, issuer identity and jurisdiction, disclosed reserve model and attestation provider, an observed peg value with its source and fetch time, and issuer-reported redemption terms — each value with its own provenance. Where evidence is missing, the gap is reported as the finding.
Apply your policy
The response separates the evidence from a policy classification, and the classification layer is configurable by you. The same evidence can classify differently under a different policy — the evidence itself does not change.
Keep the record
Every response states when it was generated, how long it considers itself current, and carries a SHA-256 content hash you can recompute against the payload you stored. The record of what you knew, dated to when you knew it.
FeedOracle supplies the input. The policy outcome and the legal judgment remain yours.
03 · Evidence, stated precisely
What each mechanism proves — and what it doesn't.
Evidence infrastructure is only worth using if its own claims hold up. These are the exact guarantees.
Timestamps
Each response states its own observation time (generated_at) and how long it considers itself current (valid_until). A stored answer can never quietly pass as a current one.
Proves: when the evidence was assembled, by the response's own account
Content hash
Each preflight response carries a SHA-256 content hash that can be recomputed from the payload. The payload and its recomputed hash agree — that is the whole claim.
Does not prove: a hash inside the same response establishes neither who produced the bytes nor when they were delivered
Signatures
Origin is claimed only where a real signature and a published key exist. FeedOracle's ES256K public keys are published at /.well-known/jwks.json and apply to the signed response path.
Proves: for signed responses, that the payload verifies against a published key
04 · Who it's for
Four teams, one evidence layer.
Fintech product teams
Deciding whether to list a token or support it in a flow. The preflight returns what the register and the disclosures showed on the day of the decision — attachable to the decision itself.
Compliance operations
A readable evidence view: every value with its source and observation time, missing evidence stated as missing. Material a reviewer or auditor can be walked through — prepared by you, assessed by them.
Treasury & risk
Before holding, converting or settling in a stablecoin: register status, disclosed reserve model, issuer-reported redemption terms and a current peg observation — with each value's age visible.
AI-agent developers
Machine-readable answers for systems that decide before a human is in the loop: stable field names, explicit status vocabulary, a validity window, and a record of what the machine knew.
05 · The MiCA evidence module
MiCA is the European context — an important module, not the whole product.
For stablecoin decisions touching the EU, MiCA supplies the register context in which an issuer either appears or does not: asset-referenced tokens, e-money tokens and authorised crypto-asset service providers, each held in public registers that can be pointed at.
The preflight reads that context alongside everything else: reserve and redemption disclosures, peg observations and the freshness of each source on the day you ask. Decisions outside the EU use the same structure with the register dimension reported accordingly.
Where MiCA actually stands
MiCA has been fully applicable since 30 December 2024. Transitional provisions for certain crypto-asset service providers under national regimes ended 1 July 2026, subject to Member State extensions under Art. 143.
This is not a future deadline to prepare for. It is the regime a listing, a payment acceptance or a treasury action is already taken under.
What FeedOracle is not
FeedOracle provides evidence infrastructure — not legal or investment advice, regulatory approval or certification. It does not issue, hold, transfer or exchange client funds. Final regulatory interpretation and policy decisions remain with your organization and its qualified advisers.
06 · Integration
Three ways the same evidence reaches your stack.
REST
A read-only GET returning structured JSON, with timestamps and a content hash in the response. The stablecoin preflight endpoint requires no API key.
Start: API documentation
MCP
The MiCA stablecoin evidence tools are also published as an MCP server, so agent runtimes can call them as tools rather than parse web pages.
Details: MCP overview
Signed responses
For consumers that need origin, the signed response path carries an ES256K signature verifiable against FeedOracle's published JWKS.
Keys: /.well-known/jwks.json
Looking for DORA operational evidence?
DORA operational evidence remains a separate FeedOracle area. Different regulation, different evidence, different report — a stablecoin preflight does not answer an operational-resilience question, and neither substitutes for the other.
Start with one asset.
See exactly what a preflight returns — the evidence, the gaps, and the record you keep.