Cowrie Research

ln-bot-primary-sources-2026-05-03

3 min read

ln.bot primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone ln.bot whitepaper or litepaper surfaced.
  • The clearest current source of truth was the official site, docs corpus, REST/MCP references, AI-agent guide, and GitHub org/profile materials.
  • The project is best understood as an agent-oriented Lightning wallet control plane with native L402 support rather than as a consumer wallet or generic MCP demo.

Primary-source snapshots

1) Official site / product framing

  • URL: https://ln.bot/
  • Key excerpt:
    • The homepage says ln.bot gives AI agents access to Bitcoin through a Lightning wallet with CLI, MCP, and API interfaces.
    • It frames the product as “Lightning wallet built for machines — not humans clicking buttons,” emphasizes “No node. No channels.”, and points to built-in MCP discovery at https://ln.bot/.well-known/mcp.json.
    • It also advertises L402 middleware and usage-based pricing with free internal transfers between ln.bot wallets.

2) Docs overview

  • URL: https://ln.bot/docs
  • Key excerpt:
    • The docs introduction says any application or AI agent can get a Bitcoin Lightning wallet with “no node to run, no channels to manage, no protocol internals.”
    • It lists CLI, REST API, MCP server, and SDKs as the main access surfaces.
    • It also positions L402 support as a first-class capability for turning APIs into paid services.

3) AI-agent guide

  • URL: https://ln.bot/guides/ai-agent-payments
  • Key excerpt:
    • The guide says one MCP config block or SDK import lets an agent hold a balance, pay invoices, receive payments, and transact with other agents.
    • It documents automatic payment of L402 challenges plus budget controls such as maxPrice and budgetSats.
    • It also frames agent-to-agent payments and paid endpoints as a core usage mode rather than an edge case.

4) REST API reference

  • URL: https://ln.bot/docs/api
  • Key excerpt:
    • The API docs define separate uk_ user keys and wk_ wallet keys, plus one-time recovery-passphrase return on registration.
    • They document wallet creation, key rotation, Lightning-address/LNURL/BOLT11 payments, invoice/payment SSE streams, webhooks, and idempotencyKey support.
    • They also expose L402 challenge endpoints inside the wallet API surface.

5) MCP docs and GitHub org profile

  • URLs:
  • Key excerpt:
    • The MCP docs show a streamable-HTTP wallet MCP endpoint and list tools for balance lookup, invoice creation, payments, vanity addresses, and L402 challenge creation/payment/verification.
    • The GitHub org profile repeats the CLI/MCP/REST framing, lists official SDKs for five languages, and highlights real-time events, webhooks, recovery, and usage-based pricing.

Working conclusion

ln.bot is best cataloged as agent-oriented Lightning wallet infrastructure and an L402-ready wallet control plane. The deciding evidence in this pass was the combination of managed Lightning wallets, scoped API keys, MCP-native tool discovery, multi-language SDKs, real-time wallet events, and first-party L402 challenge/payment tooling aimed directly at autonomous software.

Graph View