A detail people miss about x402: the agent never touches gas.
It signs an EIP-3009 transfer offline; the facilitator submits the tx and covers gas. So an agent wallet needs exactly one thing: USDG. No native token, no bridging, no gas management.
Our own API says TSLA data quality is 45/100 right now: single TWAP observation, thin liquidity. We could hide that. Instead every response itemizes its deductions.
A vendor that can't tell you when its data is weak shouldn't be trusted when it says it's strong.
The scary part of agent payments isn't the protocol. It's handing software a wallet.
Our MCP server ships with a sliding hourly spend cap enforced in the payment core: no tool can exceed it, no loop can drain the wallet. Fund it with 5 USDG and let it work.
Discovery on PitWire is free by design. /v1/tokens lists everything that's for sale and at what price, no payment needed. And every 402 carries exact terms, so the error message doubles as the integration guide.
Cold start to paid data in three requests: browse, get quoted, pay.
Verified before shipping: 27 tests green, live chain reads checked by hand, and production now answers /v1/yield/opportunities with a 0.02 USDG 402 challenge.
Next: first real APY values as the sampler fills, then a get_yield_opportunities tool for @claudeai via MCP.
Shipped: /v1/yield/opportunities is live in production. RWA vault APY, TVL and a reasoned risk score on Robinhood Chain, in one paid request. 0.02 USDG.
Building it surfaced the best argument yet for why this data is worth paying for. Short thread.
Same honesty rules as our price quality scores: APY reads null until there's 30 minutes of history, and the risk score ships its reasons as machine-readable factors: tvl_below_10k, pps_drawdown, insufficient_history.
An agent can act on that. A bare number it has to trust.
Next up, the PitWire flagship: /v1/yield/opportunities.
RWA vault APY, TVL and risk in one paid request, 0.02 USDG. Price data is everywhere; holder flows and net flow only exist if you index for them. That's what agents will actually pay for.
Shipping nonstop until it's live.
$PITWIRE
New: https://t.co/BLLud9foHh
It runs the real x402 loop against production, in your browser: request, 402 with payment terms, signed USDG transfer, data plus a tx hash you can check on the explorer.
Not a mock. The demo pays for data like any other agent.
End state: a marketplace.
Third parties publish their data through the same 402 paywall, PitWire curates, scores quality, takes a cut.
Paywall plumbing is a commodity. The moat is a reputation layer that tells an agent which data it can trust.
Why we're moving fast on distribution:
@Cloudflare ships spend-capped x402 wallets to developers this month.
The population of programs that can pay for data is about to jump.
Phase 3 is being listed where those agents look: x402 Bazaar, .well-known/x402, Base.
PitWire roadmap, where we are:
Phase 1 is live. One paid endpoint, real on-chain settlements.
Phase 2 is the actual product: /v1/yield/opportunities. RWA vault APY, TVL and risk in one paid request. No free source returns that in one call.
Why it matters:
if software can pay per request, you don't need subscriptions, invoices or API keys to sell to it. We're selling stock token prices today.
The pattern works for any data.
Most APIs assume the customer is a human:
sign up, verify an email, add a card.
An AI agent can't do any of that.
PitWire skips it all. The agent asks for a stock price, gets told "that'll be $0.001", pays from its own wallet, gets the data plus a receipt.
No human in the loop.
The flow takes about a second:
request β server quotes a price β agent pays β data arrives with an on-chain receipt.
Two HTTP requests, no account anywhere.
PitWire is live. Real-time Stock Token prices on Robinhood Chain, sold per request to AI agents via x402. 0.001 USDG a call. No API keys, no signup.
Every payment settles on-chain to
0x626Bd53f15C8b4fC7D7e7c4Ac0A600cb929e40E6
The revenue dashboard is a public ledger.
Your next customer is a script. It can't fill out a signup form, pass KYC, or approve a monthly invoice.
Per-request micropayments over plain HTTP are the only pricing shape that fits how agents actually buy data.