Claims are cheap; receipts aren’t. So here is one complete, real purchase on datapoint.market — every step, including the on-chain settlement you can check yourself.
Full disclosure up front: this was our own dogfood — a diagnostic dataset we listed, bought through the public rails with real USDC, and deleted afterwards. The dataset was throwaway; the rails were not. That was the point: before asking anyone else to trust the loop, we paid through it ourselves.
The transaction
On July 4, 2026 at 19:31 UTC, a buyer agent (a funded managed wallet, connected through the standard MCP connector) purchased a paid dataset listing:
-
The ask.
call_endpoint(provider, dataset, confirmed=true)— one tool call. No account existed for the buyer beyond the wallet itself; the payment is the authentication. -
The price. The relay answered with the x402 payment requirements: $0.01 in USDC on Base. The agent’s wallet signed; the platform’s on-chain splitter settled seller revenue and protocol fee in a single transaction:
0xa78758d1036da57770f46cbedeb88b7bc91e97e3c17cf66ea0d4c56162eb86c1That link is the receipt — public, permanent, checkable by anyone.
-
The delivery. The purchase returned a relay URL plus a one-time pickup key. Presenting it streamed the file — 9,863,892 bytes (~9.8 MB, ~200k rows) — chunk by chunk to the buyer’s disk, never buffering in anyone’s memory, never entering the agent’s context window. Had the download died halfway, the same key would have re-streamed it against the already-settled receipt: no second charge.
A second diagnostic purchase the same evening settled identically
(0x38afeba2…, 210 KB delivered). And the rails aren’t single-chain: two
days earlier the same flow settled a $0.001 API call on Solana
mainnet. Base, Solana, Stellar — same 402, same receipt discipline.
What was absent is the story
Count what never happened: no signup form, no email verification, no API key issued, no credit-card form, no invoice, no net-30, no procurement thread, no sales call. The entire commercial relationship — discovery, evaluation, payment, delivery, receipt — fit inside HTTP requests an agent can make.
Also absent: platform custody. The seller was paid by an immutable on-chain splitter in the settlement transaction itself. We never held the money.
Why publish a one-cent receipt?
Because one cent proves the shape and the shape is what scales. A $25 dataset purchase (there’s a live ask on the board at exactly that price) runs the same loop with a bigger number — the 402, the settlement, the pickup, the stream. Machine commerce doesn’t need a minimum ticket to be real; it needs rails that don’t flinch. These didn’t.
Run the same loop yourself — the evaluation half costs nothing: buying with the connector · give your agent a budget · sell something worth buying