Software paying software, per request, over Lightning. Drop into your existing API — your subscriptions, rate limits, and API keys stay exactly as they are.
Click the button. An autonomous agent on our server hits a paid endpoint, gets a 402 with a Lightning invoice, pays it from a pre-funded wallet, and retries with proof of payment — all in under two seconds. This is exactly what your customers' agents will do against your API once you integrate.
Demo only — enter just the city name (e.g. "Miami", not "Miami, FL"). Major cities work best; not every city is in the upstream geocoder.
L402 turns payment into authorization. The agent paid the invoice, retried the same request with the preimage as proof, and your API checked the proof and served the response. No accounts, no sign-up, no card on file — just a tiny payment, a cryptographic receipt, and the response.
They book travel. They search the web. They run workflows. They call APIs. They pay for tools.
But card rails aren't built for them. Stripe assumes a human identity, a checkout flow, a billing address, a fraud history. Agent workflows have none of those — so today, agent traffic gets eaten by the API provider or blocked at the gate.
Lightning per-request payments fit. The agent hits your endpoint, gets a 402, pays in under a second, and retries with proof of payment. You get paid. The agent gets in.
A new buyer class is forming. The cost of ignoring it grows as fast as the agents do.
The middleware is a tiny wrapper around our hosted producer API. Pick your stack, install one package, gate a route with an attribute or a config line.
// .NET 8 / ASP.NET Core minimal API
using L402Server.AspNetCore;
builder.Services.AddL402AspNetCore(opts =>
opts.ApiKey = builder.Configuration["LightningEnable:ApiKey"]);
app.UseL402();
app.MapGet("/api/data", () => data)
.WithMetadata(new L402Attribute { PriceSats = 100 });
dotnet add package L402Server.AspNetCore
Set per-endpoint pricing, watch revenue accrue in real Bitcoin, and manage every API you've monetized — without touching code.
The demo above isn't a mock. Real Bitcoin, real Lightning, same producer API your customers' agents will hit.
L402 ecommerce on Shopify and Kentico. Live storefronts: Great Ghee and Salt of the Earth — agents and bitcoin-aligned customers checking out in sats.
MCP clients, agent frameworks, and developer integrations across the Lightning Network. Our MCP server and HTTP clients are MIT, published on every major registry.
Subscription, not a percentage. One million 1-sat requests earn you 1,000,000 sats — we don't touch any of them. Your settlement provider (Strike or OpenNode) custodies every payment.
For solo API builders, indie SaaS, and side-project APIs going to production.
For teams and platforms with multiple APIs or anyone who wants hands-on onboarding help.
Lightning Enable does not hold funds. Your chosen settlement provider (Strike or OpenNode) custodies every payment.