FeedOracle
Specialized verticals · tested 2026-08-23 · re-test due 2026-11-23 · by the Hlido desk, not the vendor
In short: Stablecoin compliance evidence built on an unusually disciplined premise: it reports what a named source showed at a named time, marks the gaps as gaps, and refuses to hand you a verdict.
5 PASS · 0 FAIL of 5 public-surface claims
Quick answer
FeedOracle scores 80/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-23). STEADY (80) on the strength of an evidence model that is honest by construction — explicit gap states, per-field timestamps, a content hash in every response, and a stated refusal to convert evidence into a legal verdict
FeedOracle turns fragmented stablecoin disclosures and market signals into structured, timestamped evidence — MiCA register status, issuer disclosures, reserve attestation dates, peg observations, redemption terms — delivered as read-only JSON with a SHA-256 content hash and an observation timestamp in every response. Fintech product teams, compliance operations, treasury and risk functions, and builders of autonomous agents are the stated audience, and the API shape (a single GET against an asset) is exactly right for the last of those. What distinguishes this surface is the epistemics, and they are stated rather than implied. The sample response shows an explicit EVIDENCE GAP status next to a reserve attestation date — a product that renders its own missing data as a first-class value, rather than defaulting to a silent null or an optimistic pass. The page says outright that facts age at different speeds (a peg observation is minutes old, an attestation can be months old or undated) and that a decision record hiding that difference hides the risk. And it draws the boundary most compliance-adjacent vendors blur: data, policy and legal judgment are three different things; the evidence states what was found, the customer's policy classifies it, and the legal determination belongs to qualified professionals — not to a data feed, and not to FeedOracle. That is a company declining to sell the most valuable-sounding thing it could sell, which is the strongest trust signal a surface of this kind can carry. The caveats are scope and youth. Coverage breadth across issuers is not stated, the captured snapshot is explicitly not a live feed, and there is no independent audit of the collection methodology linked. The discipline is visible; the track record is not yet.
Why STEADY
STEADY (80) on the strength of an evidence model that is honest by construction — explicit gap states, per-field timestamps, a content hash in every response, and a stated refusal to convert evidence into a legal verdict. That posture is rare and directly aligned with what Hlido measures. Held out of the top band because coverage breadth is unstated, the data is explicitly snapshot rather than live, and no independent review of the collection methodology is linked; the discipline is asserted well but not yet externally corroborated.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — Stablecoin decision infrastructure — verifiable stablecoin evidence.
- PASS Cta present (required) — Run a preflight
- PASS Pricing or access — Pricing nav item present
- PASS Evidence or demo — 4 screenshots captured; live sample API response with real values rendered on the page
What we saw
4 screenshots captured by the Hlido engine during the reviewed run (run-050718475a1031db-feedoracle-io). Our own captures — not vendor marketing material.
What it does well
- Renders missing data as an explicit EVIDENCE GAP rather than a null or an optimistic default
- SHA-256 content hash and observation timestamp in every response
- States plainly that facts age at different rates and that hiding this hides risk
- Draws a hard line between data, policy, and legal judgment — and declines the last one
- Read-only GET API returning structured JSON — directly consumable by an agent
- Names the specific sources it reconciles (EU register, issuer disclosures, market)
- Explicitly labels captured snapshots as 'not a live feed' rather than implying real-time
What it fails at
- Coverage breadth across issuers and assets is not stated on the surface
- No independent audit of the collection methodology linked
- Snapshot rather than live data — freshness depends on capture cadence, which is undocumented here
- Young product with no visible customer references or track record
- MiCA and DORA framing is EU-specific; other jurisdictions are not addressed
Best for
- Fintech and treasury teams that must record why a stablecoin decision was made, not just what it was
- Compliance operations needing timestamped, hashable evidence for an audit file
- Autonomous agents that need machine-usable status vocabulary rather than prose disclosures
- EU entities working through MiCA and DORA obligations
Not recommended for
- Anyone wanting a single pass/fail verdict on an asset — the product deliberately refuses to give one
- Real-time trading decisions requiring live feeds
- Non-EU regulatory frameworks
- Buyers needing an audited methodology before adoption
Pricing & access
- Pricing findable on the public surfacePASS Pricing nav item present (tested 2026-08-23)
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-23.
Compared to
-
x402-index/x402search-mcp
evidence-over-discovery
x402search indexes an emerging payments ecosystem for discovery; FeedOracle produces dated compliance evidence about specific assets. Discovery versus decision record — adjacent corners of the same stack, not substitutes.
Agent relevance
API Behavioral-testable
Agentic-Commerce Readiness 58/100 · INTEGRABLE
Independent readiness for agent delegation & transaction. How it’s scored · check live
A documented read-only REST API (GET api.feedoracle.io/api/v3/stablecoin/mica/{asset}) returning structured JSON with an explicit status vocabulary, per-field timestamps and a content hash — directly consumable by an agent with no scraping. The product explicitly names 'developers of autonomous agents' as a target audience. No MCP server or webhook surface is published.
Agent-friendly score: 8/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- Read-only GET API returning structured JSON with timestamps and content hash — source (2026-08-23) verified
- Surfaces explicit EVIDENCE GAP states for missing data — source (2026-08-23) verified
- SHA-256 content hash shown in the sample response — source (2026-08-23) verified
- Data is explicitly a captured snapshot, not a live feed — source (2026-08-23) verified
- States that legal determination is not provided by the product — source (2026-08-23) verified
- Pricing and API documentation are published navigation items — source (2026-08-23) verified



