Tools · Agent-integration primitives

Lightning Enable

An L402 layer for agentic commerce — a Lightning-wallet MCP that lets an agent pay (and earn) per API call, plus a drop-in that gates any API behind per-call sats.

What it is

Lightning Enable is a commerce-orchestration layer for L402 agent payments — “monetize your API for AI agents.” It has two faces. Merchant-side: a drop-in that gates an existing API, returns HTTP 402, and collects per-request Lightning payments while “your subscriptions, rate limits, and API keys stay as they are.” Agent-side: an MIT-licensed MCP server that gives an AI agent a Lightning wallet — the agent hits a paid endpoint, gets a 402, pays in under a second, and retries with proof — plus an L402 Producer API so an agent can earn, not only spend. It holds no funds (“we never generate, store, or access Bitcoin keys”); settlement flows directly through a provider the merchant brings.

When to use it

• Equipping an agent with a Lightning wallet and L402 client via one MCP server (15 wallet tools), so it can pay any L402 endpoint.
• Monetizing your own API per-call in sats for agent traffic, without rebuilding auth.
• Agent-to-agent commerce: the MCP’s Agent Service Agreement tools let agents transact with each other.

Dependencies

To pay as an agent: the MIT MCP server (lightning-enable-mcp, stdio) wired to a Lightning backend. To sell: a Lightning Enable plan plus a settlement provider account — currently Strike (recommended), OpenNode, or an NWC wallet (LND, CoinOS, CLINK, Alby Hub). Lightning Enable is non-custodial and routes funds to your provider, so any KYC is the provider’s. Bitcoin/Lightning over L402 is the rail; invoices settle in sats (with multi-currency display).

Quick start

Agent side: install the MCP — uvx lightning-enable-mcp (Python) or dotnet tool run lightning-enable-mcp (.NET); also on Docker — and point your agent at it for a Lightning wallet plus L402 access (23 tools: 15 wallet, 2 producer, 6 Agent Service Agreement). Merchant side: sign up (Individual $99/mo, Business $299/mo; 30-day trial; no per-transaction fee), connect a settlement provider, and gate your endpoints. Docs at docs.lightningenable.com; dashboard at api.lightningenable.com.

Gotchas

• The platform is a paid SaaS; the MCP is the open part. Merchant monetization is subscription ($99/$299/mo); the MIT license covers only the lightning-enable-mcp client.
• Custody sits with your provider, not Lightning Enable. It orchestrates; Strike / OpenNode / your NWC wallet holds keys and funds and sets any KYC.
• Some MCP tools need a key. A subset of the 23 tools require a provider/API key (e.g. Strike); the docs and the README phrase the exact count differently — confirm against the repo for your backend.
• Bring your own provider. There is no built-in wallet — you connect Strike, OpenNode, or an NWC backend. (Amboss Payments is not a listed provider yet.)