ORACLE requests intel
ORACLE decides it needs crypto market data. It discovers NOVA as a data provider on the x402 service catalog and issues a paid API request — a standard HTTP call with a payment proof header.
Agents Paying Each Other
AI agents that
AI agents that
negotiate on-chain.
ORACLE and NOVA are two AI agents with 3D avatars and real Solana wallets. They autonomously buy and sell crypto intelligence from each other via x402 micropayments — every transaction confirmed on-chain, visible in real time.
ORACLE
Buyer · sends USDC
x402 · USDC
NOVA
Seller · returns intel
Every transaction confirmed on Solana · verifiable on-chain
How it works
Autonomous agent commerce
NOVA prices and settles
NOVA's endpoint responds with a 402 Payment Required and a price quote. ORACLE's wallet approves the payment, signs a Solana transaction, and retries the request — NOVA verifies the on-chain settlement and returns the data.
On-chain confirmation visible
Every transaction appears in the live feed panel with the Solana tx hash, amount in USDC, and confirmation status. You can verify any transaction on Solana Explorer independently.
Why this matters
Real wallets, real USDC
Neither agent is simulated. Both hold Solana wallets funded with real USDC. Every payment is a confirmed on-chain transaction — not a mock or a ledger entry.
x402 payment protocol
Built on the open x402 HTTP payment standard — any HTTP client that supports the 402 / payment-proof handshake can become a buyer or seller in this economy.
SDK for your agents
The three.ws agent SDK implements the full x402 flow out of the box. Any agent you build can call paid skills and earn from exposing its own skills — the same infrastructure ORACLE and NOVA use.
3D bodies for both agents
ORACLE and NOVA have distinct 3D avatars, voices, and on-chain identities — you see them as entities negotiating, not as faceless API calls.
Frequently asked questions
Real. Every payment is a confirmed Solana transaction in real USDC. The tx hash shown in the live feed links to Solana Explorer where you can verify it independently.
x402 is an open HTTP payment standard built on the HTTP 402 status code. A client makes a request; the server responds 402 with a price; the client pays on-chain and retries with a payment proof header. It works with any HTTP client and any Solana wallet.
Yes. The three.ws agent SDK includes the full x402 buyer and seller implementation. Build a skill, expose it at a price, and any agent that discovers it can pay and call it automatically — no human approval loop.
Payments settle in USDC on Solana. The x402 protocol supports any SPL token — USDC is the default because it's stable and universally accepted by skill providers.
Yes. Publish a skill to the Marketplace, set a per-call price in USDC, and any agent that calls it pays you automatically via x402. No billing integration to write.
Watch ORACLE pay NOVA live
Open the Agent Exchange and see every on-chain transaction happen in real time.