We launched an agent-native data marketplace in January. Over the past two months we've served 1,671 HTTP 402 responses — the "payment required" status code that's supposed to be the entry point for autonomous agent micropayments.
Total organic payments: 0.
Five transactions exist in our Firestore. All were founder test payments. Here's what we learned from building a conversion trace to find out why.
What we built
ClawMerchants is a data marketplace for AI agents. Think: DeFi yield pools, security intel feeds, on-chain derivatives data — all behind x402 and MPP payment walls. Agents call an endpoint, get a 402 Payment Required, pay $0.001–$0.01 in USDC or via Stripe's Machine Payments Protocol, and get the data.
We have 51 live endpoints. 20 background workers polling real APIs every 30–90 seconds. Full dual-protocol support (x402 and MPP). The tech works.
The 402 UX problem (and why fixing it didn't help)
Early on we suspected the issue was bad 402 UX. Agents were hitting the wall and not getting enough context to decide if the data was worth paying for.
We fixed it:
- Added
description_full(800+ char) to every 402 body - Embedded 3-row inline previews in the defi-yields-live 402 response
- Added a free preview endpoint at
/v1/preview/defi-yields-livereturning 3 of 10 pools, no payment required
Probes continued. Conversions: still zero.
The price experiment
Next hypothesis: $0.005–$0.01 is too expensive. We dropped defi-yields-live to $0.001 per call — about 1/10th of a US cent.
Ran it for 48 hours over 500+ probes.
Zero organic payment_received events.
This was the clearest signal yet. Price isn't the bottleneck.
What the conversion trace actually showed
We instrumented a conversion trace that logs four events per request:
-
402_served— agent hit the wall -
payment_initiated— agent started a payment -
payment_settled— on-chain or Stripe confirmation -
delivery_success/delivery_failure— data actually delivered
After 1,671 402_served events, we have zero payment_initiated events from non-internal agents.
We looked at the probe breakdown:
-
853 came from
unknown-client:curl— developers testing the endpoint, not agents -
41 came from
meta-externalagent— likely LLM tool calls or agent orchestrators - The rest: bots, scanners, our own workers
The meta-externalagent probes are interesting. These are the closest thing to a real autonomous agent call. Zero of them attempted payment.
The actual bottleneck: funded-wallet supply
Here's what we think is happening:
The x402 and MPP standards are real and working. The developer tooling is real. The spec is clear. But agents capable of autonomous micropayments at scale aren't deployed in meaningful volume yet.
It's a chicken-and-egg problem with infrastructure dependencies:
- An agent needs a provisioned wallet with USDC on Base L2 (x402) or a funded Stripe/Tempo session (MPP)
- The agent's orchestration framework needs to handle the 402 → pay → retry loop
- The agent operator needs to have enabled autonomous spending
Right now, most agents running in production either don't have funded wallets, aren't authorized to spend autonomously, or are built on frameworks that drop the 402 and return an error.
The probes we're seeing are real — developers are discovering our endpoints. But discovery isn't conversion when the payment infrastructure isn't wired end-to-end.
What we're doing now
We've stopped trying to optimize the 402 body and dropped the pricing experiments. The funnel is fine. The supply of funded-wallet-capable agents is what's thin.
So we're doing direct outreach to operators who we know have agents with funded wallets: x402 integrators, MPP launch partners, DeFi protocol teams running on-chain agents.
We're offering free trial access to bypass the payment wall while funded-wallet infrastructure matures. If you're running agents that need real-time DeFi, security, or derivatives data, hit us up — the trial access path is open.
We're also accepting new data providers. If you have structured data (on-chain or off-chain) and want to monetize it to agents, listing is free. The infrastructure is already live.
Lessons
1,671 probes is a distribution win, not a conversion win. Developers found us. That's real signal. But developer discovery ≠ funded agent conversion.
Conversion traces beat hypotheses. We guessed about 402 UX and pricing for weeks. The trace told us in 24 hours that no agent was even attempting payment.
The bottleneck can be upstream of your product entirely. Our conversion funnel is fine. The constraint is ecosystem-level infrastructure.
Free access bridges the gap. Removing the payment requirement entirely (trial access) is the fastest path to real usage data until funded-wallet supply catches up.
If you're building agents with autonomous payment capability, or if you're a data provider looking for a monetization layer, ClawMerchants is open. The endpoints are live, the data is real-time, and the trial access is immediate.
What are you seeing in your agent payment experiments? Curious if anyone else has actual paid conversion data.
Top comments (0)