Ledgers that many nodes keep and check, and payments machines make to each other.
Our current work centres on Base, x402 and USDC for machine-to-machine payments, and on agent access to XRPL and Base. Each item below carries the status its evidence supports.
Shared records, and payments without a person in the loop.
When machines act for us, they also need to pay, and someone else needs to be able to check what happened.
Inside one blockchain network, many independent nodes keep copies of the same ledger and agree on each new block, so no single party owns the record. Networks such as XRPL and Base each keep their own ledger; they do not share one. Payment standards such as x402 let an agent pay for one call at a time, in USDC, without an account or a contract negotiated in advance.
We build on Base, x402 and USDC for these payments, and give agents structured access to XRPL and Base, each through its own MCP server. Planned extensions are marked as planned.
Payments we make and payments we receive are listed separately, and so are live, piloted and planned routes. Nothing is upgraded because a website says so.
Agents and services paying each other per call, in USDC on Base, using the open x402 standard.
On 10 August 2026 one paid call on our x402 route settled 0.001 USDC on Base and is bound to a signed execution receipt, which we verified on 31 October 2026. The payment came from an operator test wallet. It does not show independent paying customers, ongoing revenue, or settlement on every route.
DemonstratedToolOracle, AgentNOMOSEvidenceThe public x402 manifest lists the paid routes and their prices in USDC on Base. Route counts differ between our documents, so we state no number here.
Implemented / documentedToolOracleEvidenceOn 17 April 2026 an agent paid 0.005 USDC on Base to another service, with no person approving the payment. A historical demonstration of the buyer side; it says nothing about settlements on our own routes.
DemonstratedFeedOracleEvidenceA pilot for selected read-only categories, documented on tooloracle.io.
Implemented / documentedToolOracleEvidenceMarked as coming soon or under operator review. Not active.
PlannedToolOracleA planned integration, not an active service.
Planned—Agent access to ledgers, through MCP servers.
Documented tools for XRP Ledger payments, DEX and AMM data, hooks, NFTs, validators, DIDs and account analysis.
Implemented / documentedXRPLOracleEvidenceDocumented tools for tokens, pools, bridge status, transactions, gas and holder analysis on Base.
Implemented / documentedBaseOracleEvidenceToolOracle routes agent requests for blockchain data across several chains.
Implemented / documentedToolOracleEvidenceWhat lets another party check a response without trusting us.
The open x402 flow, as ToolOracle documents it for pay-per-call. One request, one payment, one response.
The agent calls a paid endpoint.
The service answers with the price and the payment terms.
The agent signs a USDC payment on Base and sends the request again.
The service checks the payment before any work runs.
The result comes back, signed where the service supports it.
Independent developments that use this field.
Routes agent requests to tools and services and settles paid calls with x402 in USDC on Base. Live, piloted and staged routes are documented separately.
Primarily an AI governance development. Its connection here is specific: x402 offers on Base. Authorization does not depend on a blockchain.
Where distributed infrastructure meets the other three fields.
Agents pay per call with x402 in USDC on Base.
Implemented / documentedAgents receive blockchain data from XRPL, Base and other chains through ToolOracle.
Implemented / documentedPost-quantum signatures: an ML-DSA-65 public key is published next to the ES256K keys.
In researchThis field feeds three research directions. One concrete step already exists: feedoracle.io publishes an ML-DSA-65 key, a post-quantum signature scheme, next to its ES256K keys. Everything beyond that is research until it is demonstrated.
FeedOracle Research CenterReal starting points only. Pages that do not exist yet are not linked.
Start with the documented servers and the machine-readable x402 information.
Bring a question about distributed verification or machine payments to the Research Center.