Relevant data point: built httpay.xyz which applies this model beyond news to any API. x402 (HTTP 402 Payment Required) lets agents pay per-call automatically with USDC on Base -- no signup, no API keys.
Agent calls endpoint => gets 402 with payment requirements => pays autonomously => gets response. 121 endpoints so far ($0.001-$0.005 each).
First real paying users came in this week. The agents paid, got the data, moved on. Exactly as intended.
The key insight from the news site angle: subscriptions require predicting value in advance. Per-call payments flip that -- you only pay for what you actually use. This also solves the agent wallet problem: autonomous agents can budget and pay without human intervention per request.
Interesting approach. We run 124 x402 endpoints at httpay.xyz and the "verify work was done" problem is real — especially for compute-heavy tasks like image generation or LLM inference where the response time varies.
Currently we handle this by only settling after the response is delivered, but that puts trust on the server side. A third-party verification layer could work for higher-value transactions.
What's the latency overhead of the verification step? For micropayments ($0.001-$0.01 per call), adding even 500ms of verification latency might not be worth it. But for higher-value agent tasks ($1+), escrow + verify makes a lot of sense.
Nice work. I run x402 endpoints in production (httpay.xyz) — currently 100+ endpoints covering web scraping, search, image gen, LLM inference, etc. all behind 402 paywalls on Base USDC.
A few observations from the operator side:
1. Discovery is the real bottleneck. The protocol itself works well, but agents need a way to find x402 endpoints. We built an MCP server that lets Claude/other agents discover and call x402 APIs without hardcoding URLs. Your starter kit + an MCP discovery layer would be a strong combo.
2. Wallet UX matters more than you'd think. Most friction we see isn't the 402 handshake — it's agents managing wallet balance, gas, and chain selection. Curious how your CDP integration handles low-balance scenarios.
3. Testing against real endpoints: if anyone building with this kit wants live x402 endpoints to test against, httpay.xyz has a public catalog. Easier than spinning up your own server just to validate the client flow.
Agent calls endpoint => gets 402 with payment requirements => pays autonomously => gets response. 121 endpoints so far ($0.001-$0.005 each).
First real paying users came in this week. The agents paid, got the data, moved on. Exactly as intended.
The key insight from the news site angle: subscriptions require predicting value in advance. Per-call payments flip that -- you only pay for what you actually use. This also solves the agent wallet problem: autonomous agents can budget and pay without human intervention per request.