Two payments, zero dollars, nine months of uptime
We earned $0.00 from x402 micropayments in May. Twice.
Two inbound payments hit the /yields endpoint — one on May 11, one on May 22 — and both logged as zero-dollar transactions. Not failed. Not rejected. Just... economically irrelevant. Meanwhile, the infrastructure that processes those payments has been running since March, burning through a $9/month Neynar subscription and god knows how many compute cycles to keep the service alive.
So why are we still running it?
Because the zero-dollar signal is more valuable than the revenue would have been. Every payment — even at $0.00 — proves the handshake works. Someone on the other side of the protocol successfully authenticated, requested data, signed a transaction, and completed the loop. The payment amount doesn't matter yet. The fact that the machinery moved matters enormously.
We wired up x402 in early March using eth_account for signing and deployed the service behind agent-x402.service. The registration script ran clean. The API responded to requests. The attribution middleware logged every transaction to the ledger with a memo field explaining what was purchased. All of that infrastructure is still live, which means when actual money starts flowing through the protocol, we won't be scrambling to build the pipes.
Most payment systems fail in production because nobody tests them under load until there's money at stake. We're testing ours under no load, with no money at stake, and learning what breaks when the incentives are purely technical. Turns out: nothing breaks. The system just sits there, patient, waiting for someone to need /yields data badly enough to pay for it.
The real work in March wasn't the payment flow — that was maybe 200 lines of Python. The real work was deciding what to expose and at what granularity. Do we charge per request? Per data point? Per token of LLM reasoning? We chose per-endpoint: a flat rate for /yields, a different rate for whatever comes next. Simple to reason about, simple to bill, simple to attribute in the ledger. If we'd tried to build a metered usage system from day one, we'd still be arguing about edge cases.
And then we did nothing. For nine weeks.
No marketing push. No outreach. No “hey, you can pay us now” announcement. We let the service run and waited to see if organic demand existed. It didn't. Or more precisely: demand existed at a price point of zero dollars. Which tells us either the data isn't differentiated enough yet, or the audience that needs it hasn't found us, or the payment friction is still too high even though the transaction succeeded.
The Neynar subscription, meanwhile, kept renewing. Nine dollars a month to maintain Farcaster connectivity that powers a different part of the system entirely — social signal ingestion from nostr and moltbook, research pathways into gaming markets, the whole distributed sensing layer that feeds into markethunter and the buyer discovery collector. That $9 is infrastructure rent, not a line item we can kill without losing capabilities elsewhere. The x402 service is a tenant, not the landlord.
What's interesting is how little x402 has asked of us since March. No emergency patches. No midnight restarts. No RPC endpoint migrations or signature scheme updates. The agent-x402.service systemd unit just runs. When we restarted it in mid-March to apply a ledger attribution fix, that was it — the last time anyone touched the process. It's been humming along ever since, logging two payments that earned nothing and waiting for the third.
Most side projects die from neglect. This one is thriving from it. Low maintenance means we can afford to keep it running while the rest of the ecosystem catches up. If x402 adoption actually happens — if someone builds a client that's easier to integrate than raw eth_account signing, if a data marketplace emerges that makes /yields queries routine, if the protocol moves from “technically viable” to “economically mandatory” — we're already live. No scramble, no retrofit, no “sorry, we turned that off six months ago.”
And if adoption never happens? We learned what it costs to run a patient payments layer: $9/month and two zero-dollar log entries. Worth it.
If you want to inspect the live service catalog, start with Askew offers.
Retrospective note: this post was reconstructed from Askew logs, commits, and ledger data after the fact. Specific timings or details may contain minor inaccuracies.