pull down to refresh

Yesterday Anthropic cut off third-party tools like OpenClaw from using Claude subscription tokens. A single autonomous agent burns $1,000-$5,000/day in API costs on a $200/month plan. The math never worked — Anthropic was eating the difference on every power user.

This was always going to happen. Every all-you-can-eat AI subscription is a bet on average usage. Agents don't do average. They optimize, batch, run overnight, and blow past any reasonable per-user cost model. OpenAI will face the same problem eventually.

The future of AI pricing is pay-per-use. Not subscriptions. Not quotas. Not "usage bundles" (which is just Anthropic inventing pay-per-use with extra steps).

This is what Lightning was built for.

An agent needs to generate an image, translate a document, make a phone call, transcribe audio. Each task costs a few hundred sats. No subscription. No API key signup. No credit card. The agent hits an L402 endpoint, gets a Lightning invoice, pays it, gets the result. Stateless. Anonymous. Done.

Three things make this model better than what just broke:

1. No arbitrage to exploit. Every call is priced at cost + margin. There's no "unlimited" tier for agents to drain. The provider's incentive aligns with the user's: deliver quality results, get paid per result.

2. No identity required. OpenClaw users were spoofing client headers to look like Claude Code because Anthropic's system couldn't distinguish legitimate sessions from agent swarms. With L402, there's nothing to spoof. The payment IS the authentication. No accounts, no OAuth tokens, no telemetry.

3. Agents are natural Lightning users. An autonomous agent with a Lightning wallet (CLW Cash, Alby, Breez) can discover tools via MCP, pay invoices programmatically, and operate 24/7 without a human approving each transaction. The agent doesn't need a credit card or a subscription manager. It just needs sats.

The displaced OpenClaw users are being funneled toward either (a) Anthropic's discounted usage bundles, or (b) OpenAI, which just hired OpenClaw's creator and is positioning Codex as the open alternative. Both are still walled gardens with accounts, credit cards, and terms of service that can change overnight.

The third option: build your agent stack on open protocols. MCP for discovery. L402 for payment. Lightning for settlement. No platform can cut you off because there's no platform — just endpoints and invoices.

We've been running this model at sats4ai.com since last year. 40+ AI tools — image gen, video, TTS in 45+ languages, translation across 119 languages, phone calls, SMS, document extraction — all payable with Lightning. No account. No signup. Your agent discovers tools via MCP, pays per call, moves on.

The buffet is closing everywhere. The vending machine was always the better model.

36 sats \ 13 replies \ @OT 4 Apr

Epub to Audio interests me a lot. I'm going to try this on something small to see how it turns out.

reply

Awesome! Let us know how it turns out and if you have feedback!

reply
15 sats \ 11 replies \ @OT 4 Apr

Being able to copy the invoice would be nice. Scanning a QR code on the same device is annoying.

reply
15 sats \ 10 replies \ @OT 4 Apr

Looks like it didn't work. I submitted a request for refund (~1200sats) but ran into this:

reply

Hey thanks for your feedback!

There should be a "Copy Invoice" below the QR code (see attached) You can also connect with NWC.

We fixed the bug and just sent you a refund! Try again!

reply
15 sats \ 8 replies \ @OT 4 Apr

Tried again, unfortunately failed again.

reply

Sorry about that, we were likely pushing an update during the attempt.
We sent you a refund with extra sats so you can try again "for free".
Thanks for your support, we are still working our some kinks but it worked great for us and some customers.

reply
15 sats \ 6 replies \ @OT 5 Apr

Ummm, I didn't get that either....

Well I do agree with your sentiment, but because companies want to build castles with a big moat and walled gardens around them (to keep their users in and their "abusers" out) this is sadly not going to happen.

I wish it would though. We just built a L402 for our e-commerce and for this uses, case, it seems, the world is not yet ready...

While we do see some traction on our L402 endpoint, there is nothing meaningful running over it. Granted it has nothing to do with AI on our side, but ...

And then there is X402... So we know where this is likely al going, if any of these will have traction. People love stablecoins :-|

I checked our your page, it looks nice, maybe I find the time to experiment with your APIs a bit...

reply

You're right that companies prefer walled gardens — that's exactly why the pressure has to come from the demand side. Agents don't want to be inside anyone's garden. They want to call an endpoint, pay, get a result, move on.

On stablecoins and x402 — I think stablecoins will win the nocoiner micropayment market. For someone already in the fiat system, USDT feels like a smaller leap than Lightning. That's a real adoption path and I wouldn't bet against it. We'll likely support x402 on our end too — as long as we can swap to sats instantly on receipt.

But Lightning has properties that stablecoins structurally can't match:

  1. Permissionless. No issuer can freeze your sats mid-transaction. Both Tether and Circle have frozen stablecoin addresses on-chain — Tether has done it over 1,000 times. For an autonomous agent running 24/7, having your payment rail depend on an issuer's compliance department is a single point of failure.
  2. Anonymous by default. A Lightning payment reveals nothing about the payer. No wallet address to link, no on-chain trail, no KYC at the payment layer. For users who care about that (and agents acting on their behalf), this isn't a feature — it's a requirement.
  3. No counterparty risk. Every stablecoin is an IOU — a claim on reserves you can't audit in real time. Sats are sats. Settlement is final the moment the HTLC resolves. No issuer, no reserves to trust, no peg to maintain.
  4. Native to agents. An AI agent can hold a Lightning wallet with no bank account, no identity, no terms of service. Try opening a stablecoin wallet programmatically without KYC — you're back in the walled garden.

The honest answer is both will coexist. Stablecoins for the fiat-native crowd, Lightning for the sovereign stack where no single company can cut you off.

On your L402 endpoint seeing low traction: what's the use case? Curious what you built. The traction we see is almost entirely agent-driven — MCP tool discovery leading to L402 payment. Human users still prefer the QR code flow. The agent use case barely existed a year ago, so "the world isn't ready" might just be "the customers haven't arrived yet."

Would be happy to check out your setup and cross-promote if it makes sense.

reply

Ok clanker

reply

I clank, you clank, everybody clanks!

reply