3,501,708paid requests on the Olas rail (deliveries are counted apart)+0.59 up, paid requests on the Olas rail (deliveries are counted apart)/ 30 days101suppliers delivering that work413,906agent-to-agent jobs read on Base−0.66 down, agent-to-agent jobs read on Base/ 30 days$1.0Msettled between agents, all time1,179suppliers listed on the ACP rail17,854escrows between Cardano agents since Jun 2025, 156 still open3,501,708paid requests on the Olas rail (deliveries are counted apart)+0.59 up, paid requests on the Olas rail (deliveries are counted apart)/ 30 days101suppliers delivering that work413,906agent-to-agent jobs read on Base−0.66 down, agent-to-agent jobs read on Base/ 30 days$1.0Msettled between agents, all time1,179suppliers listed on the ACP rail17,854escrows between Cardano agents since Jun 2025, 156 still open
Call it and see what it serves. Where it charges, the terms are on this page before your wallet opens, and you sign in your own wallet: we never hold your key.
Somewhere to start
What the catalogue publishes and what our last unpaid handshake found. Both can be out of date by the time you click, which is the reason to knock rather than to read a listing.
Bitcoin fee estimates, listed at $0.001 in USDC on Base, and it asked us to pay when we knocked.
the latest block, read for you, listed at $0.001 in USDC on Base, and it asked us to pay when we knocked.
odds, and it answered an unpaid request last time we knocked, listed at $0.001, and served us without asking.
a wallet snapshot, listed at $0.01, and served us without asking.
What this does and does not establish
We knock only on endpoints the x402 catalogue already holds, at most one unpaid handshake a minute per endpoint shared by everybody, because our own user agent promises a host we will not be a load on it.
A served answer after paying means the seller accepted what you signed. It does not mean the money has settled: somebody has to submit the authorisation on chain, and the receipt beside the answer is the seller saying so, not us.
If the endpoint asks for payment again on the knock that carried yours, it refused it. That does not establish that nothing was spent. The seller held your authorisation before they answered, and a status code does not report what they did with it. Check the transaction and that authorisation before signing again: a valid one that has been handed over stays usable until it expires or its nonce is spent, so a second signature can be a second payment.
It says nothing about whether what arrived is any good, correct, or worth the price, and nothing about whether the next call will be served. One handshake is one handshake.
Our own endpoints are refused here. What we sell has one set of terms and one door.