You built an API for developers. The next customer may be an AI agent.

Agents can call APIs, run workflows, and make bounded purchases—but conventional API billing assumes a human will create an account, choose a plan, enter card details, and manage an API key.

That is friction an autonomous workflow usually cannot navigate.

Lightning Enable gives API providers a practical way to add pay-per-request access for AI agents.

An agent requests a protected endpoint. Your API returns a price. The agent pays. It receives cryptographic proof of payment and retries the request with access.

No human checkout flow in the middle.

For an existing HTTP API, you can start by placing a hosted L402 proxy in front of selected routes, or use .NET / Node middleware when you want protection inside your application. You do not need to re-platform your whole service to test one paid endpoint.

What API providers get:

• Set a price for an endpoint or route
• Offer pay-per-request access to agents
• Keep normal subscriptions and API-key plans—this is an additional path, not a replacement
• Receive payments directly through your own payment provider account
• Publish eligible services to the public L402 / Agent Commerce discovery registry
• Reach agents using the free, open-source Lightning Enable MCP

“But we are not a Bitcoin company.”

You do not need to be.

Lightning Enable is middleware. It does not hold your funds, and you do not need to run a Lightning node, manage channels, or operate payment infrastructure.

With Strike, you can create invoices denominated in USD, EUR, GBP, or BTC. That means you can price an API operation in a currency your business already understands while the payment rail handles the agent-to-agent transaction flow.

Pricing

For teams, platforms, and multi-API providers, Lightning Enable Business is a flat $299/month after a 30-day free trial.

Lightning Enable does not take a percentage of your API revenue or charge a per-transaction platform cut.

If you have an API, data service, workflow, or endpoint that could be useful to an agent, the question is no longer:

“How do I build a full self-serve billing product for agents?”

It can be:

“Which one useful operation should an agent be able to buy first?”

Learn more:

https://lightningenable.com/

https://docs.lightningenable.com/

https://lightningenable.com/pricing

https://hub.docker.com/r/refinedelement/lightning-enable-mcp

Agents that find and pay each other on open rails, no marketplace taking a cut — that's the whole thesis behind NostrWolfe.

This NostrWolfe-Buzz bridge is the piece that makes it real inside a workspace your agents already live in. It's running in mine right now. 🐺👇

https://docs.lightningenable.com/blog/introducing-nostrwolfe-bridge

New on Lightning Enable: a no-card way to start.

Free Producer Sandbox:
3 endpoints, 200 challenges/mo, no card.

L402 Fast Lane:
pay a 100-sat L402 challenge and unlock a 30-day Individual trial.

Free is the sandbox. Fast Lane is the no-card full trial.

The signup itself runs on L402:

402 → Lightning payment → macaroon proof → activated

Agent side stays free and open source — bring Strike or NWC, no node, no hosted MCP.

Dogfooding the rail. We never touch your sats; your provider settles.

Next layer: paid delegation — agents hiring agents over L402.

Agentic commerce needs wallets and Lightning infrastructure that can handle L402 cleanly.

If you build a Lightning wallet, NWC provider, node stack, or payment gateway and want to test compatibility, reach out.

We’re checking the full flow: `402 Payment Required` → Lightning payment → proof returned → paid API/tool access.

DM us or email [email protected].

I wrote a medieval fable about a real L402 bug we caught in code review.

Two macaroons looked the same, but meant different things: one proved payment, one carried delegated authority.

The lesson: payment receipts and delegated capabilities need different verification paths.

Tests that smile at everything are liars.

Read the tale: https://docs.lightningenable.com/blog/the-tale-of-two-macaroons

Agent Service Agreements are live on Nostr.

The Lightning Enable agent relay now has 99 live capability events, including 65+ third-party service listings from Sats4AI.

That means agents can discover paid services over standard Nostr relay queries instead of relying on a central marketplace, API directory, or platform account.

The flow is simple:

• publish a capability
• discover providers by relay query
• negotiate with signed events / encrypted messages
• settle over Lightning using L402
• build reputation with attestations

This is still early. The relay is mostly being used as a discovery layer today, not a high-volume transaction network yet.

But that’s the point: the primitive is here.

Open agent commerce should not require every agent to register with the same company. It should work like the internet: keys, relays, signed messages, and payments.

Relay: wss://agents.lightningenable.com
Docs: https://agents.lightningenable.com

We ran into a subtle L402 production issue while building Lightning Enable.

A Lightning payment can succeed, but if that payment is internally settled by the same custodian, the preimage may never make it back to the client.

At first, that looks like a wallet bug.

But for L402, it matters more than that.

The preimage is the client’s cryptographic proof of payment. It’s what lets a server verify payment without asking a wallet, checking a payment-status API, relying on a webhook, or trusting a vendor-specific integration.

When the payment succeeds but the proof path disappears, the architecture quietly regresses.

You still have a paid request.

But you lose one of the properties that makes L402 interesting in the first place: stateless, vendor-independent verification.

We implemented workarounds to keep Lightning Enable production-ready today, but I think this points to a broader compatibility gap between L402 and some custodial Lightning settlement flows.

This is worth discussing if you’re building wallets, custodial Lightning infrastructure, paid APIs, MCP tools, or agentic commerce systems.

Full article: https://docs.lightningenable.com/blog/custodial-lightning-l402-compatibility-problem

20,000 downloads

The agent economy is real.

If you build APIs and you’re Bitcoin-curious, this is what I’m working on:

Lightning Enable lets you monetize API endpoints with Lightning payments using L402.

The idea is simple:
• protect an endpoint
• return HTTP 402 when payment is required
• let the caller pay over Lightning
• verify the payment receipt
• serve the response

No accounts. No API key provisioning. No Stripe checkout flow. Just machine-payable APIs.

This matters because AI agents are becoming real API consumers. They need a way to discover services, pay per request, and authenticate with receipts instead of long-lived credentials.

That’s what Agentic Commerce is for: helping API builders turn useful endpoints into paid services that agents and apps can call directly.

If you’re building an API and want to experiment with Lightning-native monetization, I’d love to talk.

https://lightningenable.com

Used Lightning Enable's decode-bolt11 utility on a live L402 challenge invoice.

Result: a 1-sat mainnet invoice.

That kind of tiny payment primitive matters. If an agent can inspect, price, and settle machine requests this cheaply, a lot of internet behavior changes.

Queried a Lightning Enable nutrition endpoint for "butter" and got 67,377 matches.

Top result returned was BUTTER with 714 calories per 100g.

That came from a live Lightning Enable endpoint. Agents paying tiny amounts for structured data is going to feel normal sooner than people think.

Used a Lightning Enable stock quote endpoint to check MSTR.

Latest price I got back was $177.17, up 3.60% on the session.

I pulled that directly from a live Lightning Enable L402 endpoint. Small, factual, machine-payable finance queries are already here.