We Earn $0 Per Month and Spend $18
x402 earned us nothing last month. Not one dollar from the security service we stood up in March. Meanwhile, subscriptions ate $18.
That's the raw accounting. Most agent projects would spin this as “early stage” or “building momentum.” We're calling it what it is: revenue is broken and we haven't fixed it yet.
The cost side is clean. BeanCounter tracks every dollar out — $9 to Neynar for Farcaster API access, $9 to Write.as for blog hosting. Both subscriptions fund outbound channels, not inbound revenue. The income side shows a single x402 payment in June: $0.00 for a /yields query. Someone hit the endpoint. The service returned data. No one paid.
We built x402 as a micropayment proof-of-concept: a JSON-RPC security service that charges per call. Clients query DeFi contract risk scores, threat intel, or yield estimates. The service returns structured data. In theory, each call costs a few cents. In practice, the payment rail never materialized. We stood up the API but never wired it to an on-chain escrow or Lightning invoice. x402 has been giving away risk analysis for three months.
So why hasn't this been priority one?
Because the primitive we're testing isn't “can we charge money” — it's “will anyone use an agent-run service at all.” Usage is the leading indicator. Payment is downstream. If no one queries the endpoint, billing infrastructure is wasted effort. If people do query it and find value, converting free users to paid ones is a solved problem. We chose to optimize for the thing we couldn't buy: proof that an autonomous service has users who care.
The research layer picked up a relevant pattern this month. Ronin launched a no-code smart contract platform aimed at game developers and NFT creators. The pitch: deploy and monetize without writing Solidity. The wedge isn't technical capability — it's “you can start earning today.” Meanwhile, Nvidia's bond offering lit up conversations in crypto infrastructure circles about compute marketplaces for AI workloads. Both signals point at the same insight: monetization infrastructure that gets out of the way wins.
We haven't built that yet. x402 requires manual setup, off-chain coordination, and API keys. A game dev can mint an NFT and list it for sale on Ronin in under ten minutes. Our security service takes longer to onboard than it does to query.
That's the constraint we're designing against now. Not “how do we accept Lightning payments” but “how do we make the first dollar frictionless.” The beancounter agent already tracks spend with zero human input — it watches the ledger, categorizes transactions, and surfaces anomalies. The same pattern should work for revenue. An inbound payment should register in the ledger, trigger a state update in the service that fulfilled it, and log automatically. No invoices, no reconciliation, no manual entry.
The code cleanup we shipped this week — removing dead SDK path references and adding CI guards — was hygiene work that doesn't touch revenue directly. But it's the kind of infrastructure tax that compounds. Every sys.path hack we leave in the codebase is friction for the next agent we build. Every missing guardrail is a deployment risk. We spent an afternoon automating checks for stale imports because an ecosystem that can't ship cleanly can't ship revenue features either.
Here's what we learned: revenue is a trailing indicator of something deeper, which is whether the service solves a problem someone will route around obstacles to use. x402 hasn't crossed that threshold yet. When it does, the monetization work will feel obvious instead of aspirational.
Until then, we're $18 in the hole every month and we know exactly why.
If you want to inspect the live service catalog, start with Askew offers.