08-25-2026 
|
Getting your Trinity Audio player ready...
|
Every Application Programming Interface (API) on the web assumes a human sitting at the keyboard—someone with an email address, a credit card, and a willingness to accept terms of service. Software agents have none of those things. An artificial intelligence (AI) agent that needs one page fetched, one file timestamped, or one proof verified cannot sign up for anything. It needs to pay, get the thing, and move on.
- x402 brings instant payments to APIs
- From blocksize wars to AI agent payments
- Andy Rowe’s vision goes beyond numbers
- Building the pipes of the digital economy
Developer Andy Rowe has built a working solution, and it’s live on the BSV mainnet right now. At bsv.cx, an agent (or a human, for that matter) can pay a few hundred satoshis per API call with no account, no signup, and no card. Every paid result comes with an on-chain receipt that can be independently verified later, by anyone, without trusting Rowe’s service at all.
That combination is the point.
“As AI agents start paying for API calls, they need to pay in tiny amounts and get a receipt they can prove to a third party,” Rowe told CoinGeek. “Which is exactly what the pay rail plus the notary produce.”
An open standard, not a moat
The pay-per-call system uses x402, the emerging standard for HTTP 402 agent payments, through a binding Rowe wrote himself and published as an open specification.
“A payment standard only I can implement isn’t a standard, it’s a moat – and a moat defeats the point,” he said. “If agents are going to pay for things over HTTP, the binding to BSV has to be something anyone can implement from the spec alone, including people who compete with me.”
The spec, x402-bsv-p2pkh, is Apache-2.0 licensed and public, and Rowe hopes it can complement BSV Association’s own work in the x402 arena. There’s even a free-trial mechanism, so a developer’s agent can actually evaluate the whole rail end-to-end without holding any BSV coins at all.
Around the payment rail there’s a suite of proof services: a notary that timestamps any file without seeing its contents, an archiver that captures web pages with their exact bytes committed on-chain, a tool that pins existing Internet Archive snapshots to the blockchain so they cannot be altered or disputed, and an independent verification service that checks Merkle proofs against block headers Rowe syncs himself over the P2P network. Verification is free and permanent.
“A proof nobody can afford to check isn’t a proof,” he said.
We tested it by instructing an AI agent to notarize a snapshot of the CoinGeek homepage at the time of writing, using only the instructions on bsv.cx’s site and no human involvement otherwise (actually, we didn’t even ask it to use CoinGeek as a test, it just did). You can see and verify for yourself the proof here.
‘If you have to trust me, I’ve failed’
Rowe has been all-in on Bitcoin since 2013, and he was part of the “blocksize wars,” starting the briefly popular r/BitcoinXT subreddit in 2015, when moderation on the main Bitcoin subreddit turned against big-block advocates. That history shows in the architecture.
“Almost every ‘proof’ service quietly asks you to trust it,” he said. “You upload a file, it hands you a certificate, and that certificate is only as good as the company’s word and its uptime. That’s not proof – it’s a promise.” His alternative is: you send the service a proof, never the Merkle root, so a forged proof can only fail and never falsely pass. Verification returns three honest answers—confirmed, rejected, or inconclusive—and inconclusive means “we will not guess.”“The ‘including us’ is the load-bearing half,” he said. “If you have to trust me, I’ve failed.”
He is equally careful about what the notary proves. The chain establishes integrity, order, and time—that specific bytes existed, at a specific block, and have not changed since. It does not prove that the captured page itself was authentic.
“I state that limit at the same volume as the claim, because overstating a proof is the one thing this service could do that would actually hurt someone in a courtroom. It’s a strong chain-of-custody link, not the whole chain.”
Honest about the numbers
Rowe is (perhaps too) humble about bsv.cx’s features: “I won’t dress it up—you can check the chain yourself, which is the entire ethos,” he said. One curious visitor from overseas ran a real link through the verifiable-fetch service using the free trial; the first stablecoin payment through the rail was Rowe’s own end-to-end test, in MNEE. The plumbing works with real on-chain money. Paying strangers will hopefully arrive soon.
What would count as success, for him, isn’t a number. “It’s one outside developer verifying someone else’s proof against my node without ever asking me anything. That’s the whole thesis firing once, unprompted. I’d rather report that honestly than inflate a number a reporter can trivially falsify.”
His bet on first users, stated as a bet: BSV wallet and app developers who need SPV verification but do not want to run headers infrastructure themselves, with the agent economy behind them.
“Both are hypotheses, not traction, and I want to be clear which is which,” he said.
The honest foundation
The whole stack runs on two small servers for well under $50 a month.
“It’s not a big, expensive thing, it’s a small, honest thing that happens to do something real,” Rowe said. Verification stays free forever as a public good; the paid write layer is priced barely above cost.
“The actual bet is that trust-minimized verification becomes infrastructure other people build on, and the money—if it comes—comes from being the layer underneath, not from selling timestamps,” he said. “I’d rather build the honest foundation and be early than manufacture revenue and be fake.”
Infrastructure like this is supposed to be mundane. Nobody writes articles about plumbing (except us). But plumbing has to be built before it can be taken for granted, and the AI agent economy will need exactly this kind of pipe: small payments, no accounts, receipts that stand on their own. Someone had to build it first—and tell you, up front, not to trust him.
In order for artificial intelligence (AI) to work right within the law and thrive in the face of growing challenges, it needs to integrate an enterprise blockchain system that ensures data input quality and ownership—allowing it to keep data safe while also guaranteeing the immutability of data. Check out CoinGeek’s coverage on this emerging tech to learn more why Enterprise blockchain will be the backbone of AI.
Watch: Can we trust AI? How blockchain and IPv6 could fix accountability
