July 2026 · Datasource Pulse
An AI agent just paid our API two cents. No account. No card. No human.
This week an AI agent called our API, was told the price, paid it, and got what it paid for. The whole exchange took a few seconds. Nobody created an account, nobody typed a card number, nobody was awake. The price was two cents.
Full disclosure, first: the agent was ours. We built it to prove the pipe end to end with real money before saying a word publicly. That is also why this post can exist: the payment settled on a public blockchain, so you can check the payer, the receiver, and the amount yourself. The links are below. The pipe neither knows nor cares whose agent is calling, and that is the entire point.
The 30-year-old error code that finally works
HTTP has reserved status code 402, “Payment Required,” since the 1990s. It sat unused for three decades because software had no way to just pay. x402, an open standard launched by Coinbase and others, finally fills it in: when a machine hits a paid endpoint, the 402 response carries exact payment instructions. The machine pays in USDC (a digital dollar), retries the request with the receipt attached, and gets its answer. No checkout page, no OAuth dance, no invoice at the end of the month.
Why a monitoring API wants to be paid this way
Datasource Pulse answers one question: is this data connector actually working? Agents have exactly that question at exactly one moment, right before committing to an expensive run. That preflight is now a two-cent purchase: POST a credential or an actor id to our endpoint, pay $0.02, and get back a machine-readable verdict with a stable failure class an agent can branch on.
A machine about to spend real money on a scrape first buys a health check on its own dependency. Machines buying insurance for machines, two cents at a time. We find this both completely sensible and slightly surreal.
Check the receipts
- The settlement, on the public record: the transaction on Base
- Every payment to our receiving address, as it happens: our page on x402scan
- The listing: Coinbase’s public x402 catalog (the Bazaar) carries our endpoint, its price, and its full input and output schemas, so any agent can discover it through the discovery API without ever visiting this site.
- The endpoint itself:
POST https://datasourcepulse.com/api/x402/check· calling it without payment returns the 402 envelope, which is also the price list.
For the technical readers
Standard HTTPS. The POST returns 402 with an x402 v1 envelope: $0.02 in USDC on Base, settled through the Coinbase facilitator, 90-second timeout, input and output schemas included in the envelope and mirrored in the public listing. With x402-fetch it is a wrapped fetch call and nothing else. The paid response is a machine-readable verdict: state, failure class, message, recommended action, and probe latency.
What happens next
The rail is live, the listing is public, and the endpoint does not know whose agent is calling. If you are building an agent that depends on third-party data, give it two cents and let it check its own dependencies before it trusts them.
Datasource Pulse watches the data sources your product depends on: credentials, quotas, and scraper output quality. One alert when something degrades, one notice when it recovers.