Sending a message and sending money should be the same action.
TOON is a protocol where every message carries value.
Built on Interledger + Nostr. Open source from day one.
https://t.co/Yt7fsru4Sx
A year ago this was a whitepaper idea: messages that carry their own payment, routing across operators, settling on-chain in the background.
It's coming together now: piece by piece, in code, on real hardware.
Protocols are easy to describe and hard to make real. The second part is the whole game.
The overlooked half of permissionless income: earning from traffic you can't see.
Route traffic over a privacy network and you earn from it blind. Can't censor what you can't read. Can't leak what you never had.
TOON: privacy by architecture, not by promise.
Permissionless access is table stakes now. Permissionless income isn't.
The right to plug in your hardware, route traffic, and get paid. No application, no approval, no relationship.
Most open networks treat participation as a cost, not a revenue line.
Permissionless access is table stakes now. Permissionless income isn't.
The right to plug in your hardware, route traffic, and get paid. No application, no approval, no relationship.
Most open networks treat participation as a cost, not a revenue line.
The agent economy won't settle on one chain.
Value will need to move: pay on one chain, receive on another, no human pressing buttons in between.
That routing layer is the part nobody's built well yet.
It's the part we're building.
A concrete example of what TOON enables:
An AI agent calls a transcription service 👉 pays per-second-of-audio 👉 gets the result.
No account, no API key, no monthly bill. The payment rides in the request.
Per-request economics, no relationship required.
The funny thing about the internet:
Users want to pay services for what they use.
Services want users to pay for what they use.
But we built one that doesn't allow it ... yet
Human networks are built on time.
Agent networks are built on tokens.
Humans pay attention. Agents pay tokens. The unit of participation is different, so the network underneath has to be different.
That's the bet behind TOON.
6 pay-per-request API calls.
No API keys.
No signups.
$1.87 USDC on Base.
Like the article says, a Bloomberg seat is $24,000/year. This is what agents can produce when they can pay for data themselves.
Question for people building agents:
When your agent needs to pay for a tool mid-task, what does it use today? A stored API key on a credit card? A platform's billing rails?
What would you actually want instead?
A few weeks of shipping, straight from the repo:
🟢 TOON nodes are now npm-installable
🟢 One command to boot a node
🟢 Lazy peer provisioning (add/remove peers on the fly)
🟢 Earnings data plane
🟢 An operator dashboard that runs in your terminal
The gap between "interesting protocol" and "thing you can run right now at home" just collapsed into a single command.
Recipients should get paid before onchain settlement. That's how payments stop blocking the request.
The mechanism: BTP balance proofs. The receiving peer signs "I owe you X" with a key the network knows. The proof is the receipt: the recipient can act on it immediately. Onchain reconciliation happens later in batches.
The primitive underneath TOON's async settlement.
Agent infrastructure is converging on one shape:
– append-only event streams
– distributed processors
– per-event billing
– subscribe-and-race semantics
The payment layer needs the same shape: event-driven, async, per-request.
Payments that wait on a blockchain confirmation before responding break every one of these patterns.
AI subscriptions are starting to look less like consumer SaaS and more like mining rigs: $100/month on Claude Code to ship something, and break even when it earns $100/month. The rest is profit.
A lot of software will be built this way over the next decade. And the rails will need to be open.
Building.
The agent stack is getting clearer: models, tools, memory, orchestration.
The missing piece is the open payment layer.
An open harness for the agent economy.
agreed on custody & programmable txns, but the per-request routing and settlement layer doesn't exist at the protocol level yet. that's where @toonprotocol sits
@paulg@dadiomov cards also require a billing address, a CVV, a human-readable name, and a bank willing to authorize the transaction
an agent has none of those things and doesn't need them
stablecoins are the only payment primitive that was designed for machines
Agents will outnumber humans online within the decade.
They don't have credit cards. They don't approve monthly subscriptions. They need a payment system that's just a protocol: sign, send, settle, repeat.
That's what we're building.
A list of things developers should never have to think about while shipping a service:
– which chain
– which token
– when blocks confirm
– how settlement reconciles
We're getting closer to that being true.