Data & Intelligence
Noisy signals in, data that systems can rely on out.
Oracle services, structured pipelines and machine-readable data, each value with a source, a time and a signature. Where quality is limited, we say so.
Noisy signals in, data that systems can rely on out.
Oracle services, structured pipelines and machine-readable data, each value with a source, a time and a signature. Where quality is limited, we say so.
Data that can be traced, checked and used by machines.
A value is only useful to a machine if it knows where it came from, how old it is and whether it was changed.
Data rarely arrives clean. Sources disagree, feeds go stale and fields go missing. A system that decides on that data needs those limitations stated, not smoothed over.
We build oracle services and structured pipelines that carry provenance and freshness with every value, sign what they deliver and describe themselves in machine-readable form, so agents can use them directly.
Three areas. Every capability carries the status its evidence supports.
Data from many sources in one documented, machine-readable form.
Documented endpoints for macro, energy, grid and trade data.
Implemented / documentedFeedOracle APIsEvidenceMCP servers for XRPL and Base data, and further blockchain data through ToolOracle.
Implemented / documentedXRPLOracle, BaseOracle, ToolOracleEvidencellms.txt files on feedoracle.io and tooloracle.io describe services for agents. Both retrieved on 31 October 2026.
DemonstratedFeedOracle, ToolOracleEvidenceWhere a value came from, how old it is, and whether it was changed.
Responses carry a content hash and a request ID, signed with ES256K.
Implemented / documentedFeedOracle APIsEvidenceResponses state when the data was generated and until when it is valid.
Implemented / documentedFeedOracle APIsEvidenceDocumented: evidence carries a freshness status (current, stale or superseded), responses state data freshness, and a preflight can answer that evidence is insufficient. Not tested here.
Implemented / documentedFeedOracleEvidencefeedoracle.io publishes ES256K and ML-DSA-65 keys as a JWKS. Checked on 31 October 2026.
DemonstratedFeedOracleEvidenceData that agents can find and use without a custom integration.
A FeedOracle MCP server answered a live status call on 31 October 2026.
DemonstratedFeedOracle MCPEvidenceToolOracle routes agent intents to suitable data services.
Implemented / documentedToolOracleEvidenceDocumented separately in the API documentation.
Implemented / documentedFeedOracle APIsEvidenceA pipeline with checkpoints. Each one adds something the recipient can check later.
A named origin for every value.
Timestamped on arrival.
One documented schema.
Freshness and completeness are checked.
Missing or stale inputs are meant to be reported, not hidden.Content hash and ES256K signature.
Through the REST API or MCP.
The recipient checks the signature against the published keys.
Independent developments that use this field.
Routes agents to data services across many categories and chains, and publishes its capabilities in an A2A Agent Card.
An AI governance development that relies on this field: authorization rests on current, source-bound evidence.
Where data meets the other three fields.
Agent decisions rest on current, source-bound evidence.
Implemented / documentedBlockchain data from XRPL, Base and other chains, delivered to agents.
Implemented / documentedExperiment records with raw counts and an independent verifier, as in our public hackathon code.
Implemented / documentedThis field feeds algorithmic research: methods for combining sources, judging freshness and stating uncertainty. Research results only move into the pipeline once they are demonstrated.
FeedOracle Research CenterReal starting points only. Pages that do not exist yet are not linked.
Start with the endpoint catalogue and the documentation for agents.
Bring a question about provenance, data quality or verification to the Research Center.