Cowrie Research

lightning-enable-primary-sources-2026-05-03

3 min read

Lightning Enable primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Lightning Enable whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official product site, the docs portal, and the open-source Lightning Enable MCP repository.
  • The project is best understood as Lightning commerce orchestration middleware layered on top of third-party payment-provider accounts rather than as a custodian or direct processor.

Primary-source snapshots

1) Official product positioning

  • URL: https://lightningenable.com/
  • Key excerpt:
    • The official site describes Lightning Enable as “the infrastructure layer that turns payment into authentication.”
    • It says the product supports both L402 and MPP, positions itself around AI agents and API monetization, and emphasizes that users can “bring your own API key.”
    • It also says Lightning Enable is API middleware and explicitly states “we never hold funds or control keys.”

2) Docs introduction / architecture framing

  • URL: https://docs.lightningenable.com/
  • Key excerpt:
    • The docs introduction calls Lightning Enable a “commerce orchestration layer” for integrating Bitcoin Lightning payments.
    • It says the customer connects a payment provider such as Strike or OpenNode, while Lightning Enable itself never touches funds.
    • The same page says provider KYB/KYC is required and that custody, settlement, and compliance remain with the chosen provider.

3) Product overview and pricing model

  • URL: https://docs.lightningenable.com/products/product-overview
  • Key excerpt:
    • The product overview says all plans use a BYOA model where customers bring their own Strike or OpenNode API key and funds flow directly to their account.
    • It lists both the Individual and Business Agentic Commerce plans, each with REST API, L402, MCP, and producer features, while platform integrations like Shopify Commerce and Kentico Commerce are included with any plan.
    • It also emphasizes flat subscription pricing rather than per-transaction fees from Lightning Enable itself.

4) Open-source MCP server surface

  • URL: https://raw.githubusercontent.com/refined-element/lightning-enable-mcp/main/README.md
  • Key excerpt:
    • The repository README describes an open-source MCP server with 23 tools: 15 free wallet tools, 2 producer tools, and 6 Agent Service Agreement tools for agent-to-agent commerce on Nostr.
    • It says agents can pay invoices, access L402 APIs, discover APIs, create invoices, send on-chain bitcoin, and use producer tools to create L402 challenges and verify payments.
    • It also documents support for Strike, LND, and Nostr Wallet Connect wallets including CoinOS and Alby Hub.

5) Agent-commerce and discovery claims

  • URL: https://github.com/refined-element/lightning-enable-mcp
  • Key excerpt:
    • The GitHub repository says the project enables AI agents to make Lightning payments and participate in agent-to-agent commerce.
    • It explicitly lists Nostr-based ASA tools for discovering, requesting, settling, and reviewing services between agents.
    • This is a useful clue that Lightning Enable is not just a merchant checkout layer but also a broader agent-commerce coordination surface.

Working conclusion

Lightning Enable is best cataloged as Lightning commerce orchestration middleware and an agentic-payments control plane. The deciding evidence in this pass was the repeated combination of BYOA provider routing, explicit “we never touch funds” language, subscription-priced L402/MPP infrastructure, platform integrations, and an open-source MCP server that spans both spending and selling workflows for humans and agents.

Graph View