FeedOracle turns EU register evidence, issuer disclosures, reserve disclosures, peg signals and source freshness into one preflight response — timestamped and content-hashed.
One response for your decision process. One record for the evidence trail.
For exchanges, payment platforms and automated treasury systems.
01 · When this is the question
Not "improve compliance". A specific decision, taken on a specific day, that someone may ask you to justify later.
The problem. A token is proposed for listing. The issuer's own page says one thing; the EU register may say another, or nothing at all.
What comes back. Whether an EU register entry for the issuer was found at time of lookup, which authority and licence reference it names, which reserve model and redemption terms are disclosed — and which of these are absent.
What survives. The response, its observation time and its source links — attachable to the listing decision.
The problem. A payment service or merchant is asked to accept settlement in a token it has never assessed, often at the speed of a checkout decision.
What comes back. Register status of the issuer, current peg observation with its source and fetch time, disclosed redemption path, and an explicit gap where an attestation date is missing.
What survives. A dated record of the evidence that was available at the moment of acceptance — not a reconstruction attempted months later.
The problem. An automated system is about to move, convert or hold a stablecoin. It needs a machine-readable answer, and the operator needs to know afterwards what the machine knew.
What comes back. One structured JSON object with named fields, an explicit policy classification separated from the evidence, and its own validity window.
What survives. The stored response is the evidence trail: named fields, its own observation time, and a content hash you can recompute against the payload you hold.
02 · The response
A real response, captured read-only from the public endpoint. Nothing here is illustrative: the request and the capture time are printed with it. Re-running the same request returns a fresh snapshot with a new timestamp.
| Stablecoin | USDC — USD Coin
Field subject.symbol / subject.name |
|---|---|
| Issuer evidence | Evidence found
Circle Internet Financial · Ireland (EU)
Field subject.issuer / subject.issuer_jurisdiction. Issuer-level, not token-level. |
| Regulatory register evidence | Evidence found
register_entry_found — “EU EMI register entry found at time of lookup” Central Bank of Ireland · E-Money Institution (EMI) · reference C187865 Fields mica_assessment.*. Wording taken from the endpoint’s own status_legend. A register entry for the issuer is not a statement that this token or your intended use of it is permitted. |
| Reserve document freshness | Evidence gap
model: fiat-backed · attestation_provider: Deloitte · attestation date: not present in this response
Field reserve_info. The reserve model and the named attestation provider are reported; this response carries no attestation date, so reserve freshness cannot be established from it. The gap is shown rather than filled. |
| Peg signal | Observed
0.999706422779771 USD
Field market_data, source defillama, fetched 2026-08-19T11:08:16Z. Quoted in USD — for a non-USD-denominated token the quote currency must be read before the number. |
| Redemption evidence | Issuer-reported
“1:1 USD redemption via Circle”
Field reserve_info.redemption_rights. This is the redemption term as reported, not a tested or guaranteed redemption. |
| Source timestamps | generated_at 2026-08-19T11:08:16.360826Z · valid_until 2026-08-19T11:13:16.360826Z The response states its own observation time and how long it considers itself current. It is a snapshot, not a live stream. |
| Content hash | Present
SHA-256 · d447a3933d0c360c7335f4984adaa03be9203c397eb3f8b60ae209380fa9d31c
Field integrity. The response includes a SHA-256 content hash that can be independently recomputed: SHA-256 over the JSON with the integrity object removed, keys sorted, standard ", " / ": " separators.What that shows: this payload and this hash agree. What it does not show: who returned the bytes, or when. The hash travels inside the response it describes, so it cannot establish origin or delivery. That requires a signature, or a hash bound to a record outside the response. This REST response carries neither; FeedOracle’s ES256K keys are published at /.well-known/jwks.json for the signed response path. |
control_result field in the raw responseThe raw response contains "decision": "allow". That value is a policy classification, not a regulatory or legal determination. It reports how the evidence found maps onto a policy rule set — and that rule set is configurable by the customer, so the same evidence can classify differently under a different policy. What is not configurable is the evidence itself: the register status, the source and the timestamp are printed alongside it, including where evidence is missing.
{"control_result":{"decision":"allow","reason_code":"EU_EMI_REGISTER_ENTRY_FOUND"},"disclaimer":"Data infrastructure only. Not legal advice, compliance certification, or regulatory determination. FeedOracle does not certify or validate underlying data.","eu_issuer_authorization":null,"eu_issuer_entity":null,"evidence_links":[{"desc":"CBI Register","type":"regulator","url":"https://registers.centralbank.ie/"},{"desc":"Circle Licenses","type":"issuer","url":"https://www.circle.com/en/legal/licenses"}],"evidence_type":"MICA_ISSUER_AUTH_CHECK","generated_at":"2026-08-19T11:08:16.360826+00:00Z","integrity":{"algorithm":"SHA-256","hash":"d447a3933d0c360c7335f4984adaa03be9203c397eb3f8b60ae209380fa9d31c"},"market_data":{"fetched_at":"2026-08-19T11:08:16.416094Z","mcap":71918855024.15492,"price":0.999706422779771,"source":"defillama"},"methodology_version":"mica-checks/1.0.0","mica_assessment":{"art66_supported":true,"license_authority":"Central Bank of Ireland","license_reference":"C187865","license_type":"E-Money Institution (EMI)","status":"register_entry_found"},"policy_version":"mica-policy/1.0","reserve_info":{"attestation_provider":"Deloitte","model":"fiat-backed","redemption_rights":"1:1 USD redemption via Circle"},"subject":{"issuer":"Circle Internet Financial","issuer_jurisdiction":"Ireland (EU)","name":"USD Coin","symbol":"USDC"},"valid_until":"2026-08-19T11:13:16.360826+00:00Z"}
Captured 2026-08-19T11:08:38Z · HTTP 200 · 1405 bytes · SHA-256 of these exact bytes: 9407c359249dafc1d98e202756a6d480dc6ce54dde7d0e9191beff9ea7f654c0
Displayed with soft wrapping only; the character sequence is unmodified.
03 · The dimensions
Every dimension reports what was found, where it came from and when it was observed. Where nothing was found, that is the output — not a silent omission.
Whether an EU register entry for the issuer was found at time of lookup, with the naming authority, licence type and reference where present.
States: evidence found · no entry found · pending · not applicable
Issuer identity, jurisdiction of the entity, and links to the regulator register and the issuer’s own licence disclosures — so the claim can be checked at its source.
Returned as: named entity, jurisdiction, source links
The disclosed reserve model and the named attestation provider. Where the response carries no attestation date, freshness is reported as a gap.
States: disclosed · evidence gap · review required
Observed market price with the named data source and the time it was fetched. Quote currency is part of the reading.
Returned as: value + source + fetched_at
The redemption terms as disclosed by the issuer, reported as issuer-stated rather than as a tested or assured outcome.
Returned as: disclosed terms, attributed
Each response states when it was generated, how long it considers itself current, and which methodology and policy version produced it.
Returned as: generated_at · valid_until · versions
04 · Access
For the people who have to explain the decision afterwards.
For the software that has to decide before a human is in the loop.
05 · Why
Every statement names where it came from and links back to the regulator register or the issuer’s own disclosure.
Observation time and validity window are part of the response, so a stored answer can never quietly pass as a current one.
The response includes a SHA-256 content hash that can be independently recomputed. It shows the payload and the hash agree — it is not a proof of origin.
The classification layer is yours. The evidence layer is separate from it and is reported either way.
The same evidence serves a compliance reviewer and an automated system, without two different truths.
Absent evidence is an output, not a rounding error. A missing attestation date is reported as a missing attestation date.
06 · MiCA
MiCA is the European evidence layer of a stablecoin preflight — an important one, and not the whole of it. It 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.
On top of that register context sit the disclosures a preflight actually reads: the reserve model and its attestation, the redemption terms, the issuer documents, and how fresh each of those is on the day you ask.
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.
FeedOracle provides evidence infrastructure. It does not provide legal advice, investment advice, audit certification or regulatory approval, and it is not a supervisor or a certification body. A register entry for an issuer is not a determination that a specific token, or your specific use of it, is permitted. Final regulatory interpretation remains with qualified legal, compliance and audit professionals. FeedOracle does not issue, hold, transfer or exchange client funds, and is not a stablecoin payment platform.
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.
One read-only request. Register evidence, disclosures, peg signal, timestamps and a content hash.