Skip to main content
Skip to content
DeFi

Oracle Data for AI Agents: 8 Checks Before You Trust a Feed

Eight checks for oracle feed identity, units, timing, sessions and consumer controls. A documentation review, not a measured speed ranking or immunity claim.

Oracle Data for AI Agents: 8 Checks Before You Trust a Feed
Reading options: audio, text size & sections

Oracle infrastructure and data contracts

Oracle Data for AI Agents: 8 Checks Before You Trust a Feed

Author: Heath Muchena · Focused correction: 13 November 2026

Correction and scope

The previous version described a “30-day continuous stress test,” ranked providers by millisecond figures and called pull-based feeds immune to a class of manipulation. We do not have a retained test dataset supporting those claims. They have been removed. This is a documentation-based review of feed contracts and consumer checks, not a measured latency ranking or a security certification.

For an AI agent, a price is useful only when the instrument, units, timing, session and permitted use match the decision. A signature can support an authenticity check; it does not establish that every possible use of that price is correct. The eight-check record below keeps those questions separate.

1. Identify the contract between the feed and its consumer

A provider name is not a complete integration description. Record the product, endpoint or channel, schema version, network and exact instrument. Then distinguish what the provider delivers from what the application checks before using it.

For example, receiving a payload, verifying its signature, accepting it under an application’s age policy and filling an order are different events. A successful result at one boundary should not be relabelled as success at the others. This also explains why a quoted publishing interval cannot be treated as an end-to-end execution guarantee.

Push and pull describe delivery patterns, not a universal security ranking. A pull design can make a signed update available for submission when an application needs it. The application still needs a policy for which updates it accepts and what it does when suitable data is missing. Stork’s documentation describes its pull route as off-chain signed updates that subscribers can post to the on-chain contract. Source: Stork core concepts.

2. DN Feed Contract Record: eight checks

Use one record for one named feed route and one consumer decision. Each row is a question to document, not a score. “Unknown” is a valid finding; filling every row is not proof that an integration is safe. Retain the source version, retrieval date and a sanitized payload reference with the record.

CheckEvidence to recordWhat it does not establish
1. Instrument identityProduct, schema version, feed/asset ID, base and quote units, network and endpoint or channel.A similar ticker does not prove the same underlying instrument or contract.
2. Numeric representationRaw integer or decimal, exponent/scale, sign rules and the conversion used by this consumer.A plausible displayed number does not prove that the units are correct.
3. Timestamp meaningEach field’s documented event, unit and validity boundary; local receipt time kept separately.A timestamp is not automatically a measurement of the latest trade, publication time or local receipt.
4. Market sessionSession or market-hours evidence and the consumer’s policy for closed markets, pauses or missing updates.A transport connection does not prove that a fresh market price exists.
5. Uncertainty and errorConfidence, spread, status or error fields actually supplied, with their schema-specific definitions.Different providers’ fields are not automatically comparable error bars or probabilities.
6. Delivery and verificationPayload receipt, signature verifier, destination contract and consumer checks, including their separate outcomes.Authenticity does not prove freshness, application acceptance or order execution.
7. Access and permitted useCurrent entitlement, authentication scope, licensing and redistribution conditions for this use.A public documentation page or referral link does not grant a production data licence.
8. Cost unitWhich bill covers access, requests, verification or settlement; billing period, currency and any additional chain cost.A field in a payload is not necessarily the current invoice tariff or the whole cost of consumption.

Copyable record header

Record alias / consumer decision:
Product / route / schema version / documentation date:
Feed ID / instrument / network:
Raw payload reference, without credentials:
Checks 1–8: evidence / unknowns / responsible reviewer:
Consumer policy version and observed check results:
Unresolved mismatches and next evidence required:

Keep the observed payload separate from the policy you intended to run. A policy document is not evidence that the live consumer applied it. For a numerical age worksheet, use the existing agent data freshness and age-budget guide; this record does not recalculate latency.

3. Compare documented payloads, not unmeasured speed claims

The following examples were checked against official documentation on 13 November 2026. They identify distinct products and schemas. They are not equivalent benchmark samples, uptime observations or claims of suitability for a particular application.

Exact documentation scopeUseful documented distinctionOfficial source
Pyth ProPrice and confidence share an exponent. The guide describes microsecond feedUpdateTimestamp values and a marketSession field. Its Pro verifyUpdate checks signature and fee but does not check age; the integrator must do that separately. Do not generalize this behavior to Pyth Core SDK methods.Pyth Pro best practices
Chainlink Data Streams, Crypto Advanced v3The schema separates feedId, validFromTimestamp, observationsTimestamp and expiresAt. Timestamps are in seconds. It labels nativeFee and linkFee as legacy verification-fee fields; linkFee is not used for subscription billing. The current schema describes bid and ask as simulated impact prices, so they should not be silently relabelled as top-of-book quotes.Crypto Advanced v3 schema
Stork subscriber payload and temporal numeric valueThe subscriber example exposes asset IDs, a price scaled by 1018, signed update structures and aggregation metadata. The core-concepts page defines a temporal numeric value with a nanosecond timestamp and an integer scaled by 1018. Match each field to its documented route instead of inferring time units from another provider.Subscriber payload · Core concepts

A comparison can begin only after its measurement boundary is named. Source-event-to-publication, publication-to-receipt, receipt-to-decision and transaction-submission-to-inclusion answer different questions. A fair empirical latency study would also need a retained dataset, comparable instruments, synchronized clocks, sampling and failure rules, environment details and a reproducible analysis. None is supplied here, so this article makes no fastest-provider claim.

4. Work a small interpretation example before automating

Invented units example: a hypothetical schema supplies the integer 100000 with exponent −3. Applying that declared scale gives 100 reporting units. If an application reads the raw integer as the final price, it introduces a thousandfold unit error even if the payload arrived immediately and its signature is valid. This example is not a captured provider response.

Now suppose the same consumer has a saved policy that rejects unsupported sessions. The policy’s presence in a repository is evidence of an intended rule; a trace showing which branch actually ran is needed to support a claim about this decision. Preserve the input, policy version and observed outcome. Do not infer an accepted application decision merely from a successful transport response.

Similarly, an expired, missing or unsuitable update should remain a distinct data finding in the agent’s record. It should not be turned into a plausible current price by a language model. The appropriate operational response depends on the consumer’s documented controls and existing obligations; this article does not prescribe an automatic trade, liquidation or cancellation.

When reviewing data costs, obtain the actual product’s current tariff and entitlement. Keep subscription/access, per-use charges and destination-chain execution costs separate where they apply. This article supplies no verified live price quote and does not infer a free production licence from public documentation.

Frequently asked questions

Which of these providers is fastest?

This article does not establish that. A documented channel interval, vendor latency statement and measured end-to-end consumer latency are different evidence. There is no retained comparable experiment here from which to rank these products.

Does a valid signature prove that a price can be used?

No. The consumer still needs the applicable instrument, timing, session and application rules. For the specific Pyth Pro route above, its documentation explicitly separates verification from an age check. Other products and methods must be evaluated under their own contracts.

Are pull oracles immune to flash-loan or latency exploitation?

No blanket immunity follows from a delivery model. Pyth’s current guidance discusses adversarial update selection, latency advantages and executable-price risks, including same-block exploitation. These are integration risks to investigate; an authentic signed payload alone is not proof that an application’s economic controls are sufficient. Source: Pyth Pro integration guidance.

Oracle Age, OEV and the Data an Agent Should Actually Trust

Decision extension · 13 November 2026. Fresh delivery is not necessarily a fresh observation, and a signed price is not automatically an executable quote. Define the task before selecting a feed: valuing collateral, constructing an order, reconciling a fill and detecting a venue anomaly can require different data and acceptance rules.

Measure the age of the relevant observation

Keep source observation time, publication time, on-chain update time and application receipt time separate. A fast network can deliver old information. Record the feed identifier, asset definition, decimals, source and consumer versions and the time basis used by the application's age check.

Pyth's Pro best-practices documentation discusses a configurable age threshold and warns about confidence intervals. Those product-specific controls help frame a consumer policy; they do not supply one safe age for every asset and action. Pyth Pro best practices.

Chainlink's feed-selection documentation distinguishes market-pricing risks, market hours and consumer mitigation responsibilities. Its discussion of liquidity, sources and wrapped assets is a reminder that feed selection is more than a speed comparison. A valid update from a thin market can still be unsuitable for a large collateral decision. Chainlink feed-selection guidance.

Connect stale prices to a specific decision boundary

Fictional one-currency scenario: collateral valued at 100 with an 80% liquidation threshold and debt of 75 gives a health-factor-style ratio of 80/75, about 1.067. If the relevant collateral price falls 10% while debt and the threshold stay fixed, the updated ratio is 72/75 = 0.96. A stale valuation would miss that modeled boundary crossing. This is illustrative arithmetic, not a protocol liquidation quote.

The time elapsed does not establish the size or probability of a price move. A one-second delay does not universally permit a million-dollar loss or prove extraction by an agent. Separate stale observation, wrong asset mapping, decimal errors, source manipulation, ordinary price movement and application misuse.

A consumer policy should specify what happens when freshness, confidence, market availability or cross-source checks fail. For consequential actions, an unresolved input can require a hold or an authorized fallback. Switching automatically to a weaker source may widen risk rather than restore the original acceptance condition.

Signed exchange data and decentralized feeds serve different tasks

An order-book snapshot can describe available venue prices and depth but does not guarantee the same fill after transmission and queue changes. An oracle price can support a collateral valuation but need not be a price at which the agent can buy the full position. Preserve the distinction between a valuation reference, indicative quote, firm quote and completed fill.

For each task, identify the required instrument, currency pair, venue coverage, observation timestamp, update rules, depth and entitlement to use the data. Repositories containing a default endpoint do not reveal market-wide production preferences or prove that AI agents prefer one data model.

Two sources can share upstream data. Agreement is therefore not automatically independent corroboration. Record known dependencies and unresolved ones; do not invent source diversity from two brand names. A majority vote among stale inputs can still be stale.

Who receives value around an oracle update?

API3 defines OEV as MEV arising around an oracle update. Its current documentation describes private auctions through partners using non-delayed data and public Signed API searching on delayed data. These are specific mechanisms to inspect, not a universal rule for every oracle. API3 OEV overview.

The distribution question requires the applicable agreement and market configuration. API3's curation documentation says OEV on API3-curated markets belongs to API3 as protocol revenue. It would therefore be wrong to apply a generic dApp reward percentage to every API3-related market. Record the recipient and deductions that actually govern the reviewed deployment. API3 curated-market treatment.

Product-status correction: Pyth's documentation states that Express Relay has been wound down following OP-PIP-124, passed in July 2026. It is not an actively supported alternative for a new production comparison; its auction service, SDKs and contracts are being retired. Do not confuse that discontinued product with Pyth's other currently documented products. Pyth Express Relay notice.

A value-distribution ledger should connect the relevant update, opportunity, auction or access mechanism, settlement, recipient and actual amounts. A bid is not the same as paid revenue, gross auction proceeds are not necessarily net dApp income, and a proposed mechanism is not evidence of production deployment.

Test controls without claiming a live exploit

Use an authorized isolated environment and synthetic observations to test stale data, wrong feed identifiers, unexpected units, missing updates and unavailable fallback routes. Preserve the expected decision and actual outcome. Do not present a local mocked rejection as proof that a deployed contract enforces the same rule.

DN Agent Market Data and OEV Record
FieldEvidence required
taskValuation, quote, execution or reconciliation; accepted outcome
feedContract, asset mapping, units, deployment and consumer versions
timeObservation, publication, update and receipt timestamps
acceptanceAge, confidence, market-hours and source-quality rules
fallbackPermitted alternate source and conditions for holding the action
oevCurrent product status, mechanism, recipients, deductions and settlement
testsAuthorized environment, complete outcomes and unresolved evidence

The download is a documentation template, not a live feed monitor. It makes no external request and grants no transaction authority. Complete it offline with permitted references, not private trading data or credentials.

Method and limits: documentary review, original DN evidence method and fictional arithmetic. No live oracle latency benchmark, OEV revenue reconciliation, exploit test or AI-agent market-share study was conducted. The unsupported benchmark figures have been removed; the feed-contract record above is a documentation review, not a performance measurement.

HM

About the Author: Heath Muchena

Heath Muchena is the Founder and Lead Technical Analyst at Decentralised News. He specializes in quantitative trading infrastructure, Layer-2 derivatives, and automated Web3 execution systems.


YMYL & Affiliate Disclosure: Deploying algorithmic trading strategies and using smart contract derivatives protocols involves significant risk of capital loss. Decentralised News provides technical infrastructure research and educational content, not financial advice. Links on this page contain official affiliate referral tracking codes.

Get the most talked about stories directly in your inbox

Join the Decentralised News briefing for independent crypto, DeFi and AI analysis. No spam, unsubscribe anytime.