ln.bot
The official Python SDK for ln.bot — Bitcoin for AI Agents.
Give your AI agents, apps, and services access to Bitcoin over the Lightning Network. Create wallets, send and receive sats, and get real-time payment notifications.
from lnbot import LnBot
ln = LnBot(api_key="uk_...")
w = ln.wallet("wal_...")
invoice = w.invoices.create(amount=1000, memo="Coffee")
ln.bot also ships a TypeScript SDK, C# SDK, Go SDK, Rust SDK, CLI, and MCP server.
Install
pip install lnbot
Quick start
Register an account
from lnbot import LnBot
ln = LnBot()
account = ln.register()
print(account.primary_key)
print(account.recovery_passphrase)
Create a wallet
ln = LnBot(api_key=account.primary_key)
wallet = ln.wallets.create()
print(wallet.wallet_id)
Receive sats
w = ln.wallet(wallet.wallet_id)
invoice = w.invoices.create(amount=1000, memo="Payment for task #42")
print(invoice.bolt11)
Wait for payment (SSE)
for event in w.invoices.watch(invoice.number):
if event.event == "settled":
print("Paid!")
break
An expired invoice is not always final: one paid just before it expired can turn settled a moment later. Before giving up, check again with w.invoices.get(invoice.number), or keep listening for invoice.settled on w.events.stream() or a webhook.
Send sats
payment = w.payments.create(target="alice@ln.bot", amount=500)
Leave max_fee unset. The server defaults it to 1% of the amount (minimum 20 sats), which covers the network fee (Spark's 0.25% plus Lightning routing) for most payments. Only the fee estimate plus a small buffer is held while the payment is in flight. On success the wallet is debited amount + actual_fee + service_fee.
If the fee estimate is above the limit, create raises BadRequestError (for example Network fee estimate (X sats) exceeds maxFee (Y sats).). Pass a higher max_fee only if you accept that fee.
A payment can stay pending for a while: it is retried automatically until it settles or fails. It fails if the invoice expires first, and after 24 hours at most. watch() closes after its timeout, so if it ends without an event, check again with w.payments.get(payment.number). A failed payment carries the reason in failure_reason.
Price a payment before sending
quote = w.payments.resolve(target="alice@example.com", amount=500)
print(quote.network_fee_estimate, quote.service_fee, quote.total)
if quote.fee_warning:
print(quote.fee_warning) # sending without max_fee would be rejected
For a BOLT11 invoice, leave out amount (or pass the invoice amount). quote.internal is True when the recipient is a wallet on ln.bot, which makes the transfer free.
Pricing a Lightning address or LNURL fetches an invoice from the recipient, so it is slower. Call it once the amount is settled, not on every keystroke.
resolve raises BadRequestError when the target can't be paid, for example Recipient not found. for an unknown ln.bot address or Cannot transfer to yourself. for your own. When the amount is outside the recipient's range, the JSON in the error's body also carries min and max.
Send everything
Resolve a Lightning address or LNURL without an amount to get max_sendable, the most this wallet can send there now after fees:
quote = w.payments.resolve(target="alice@example.com")
if quote.max_sendable:
w.payments.create(target="alice@example.com", amount=quote.max_sendable)
Don't pass max_fee here: max_sendable assumes the default. It is 0 when the balance can't cover the recipient's minimum.
Check balance
info = w.get()
print(f"{info.available} sats available")
Wallet-scoped API
All wallet operations go through a Wallet handle obtained via ln.wallet(wallet_id):
w = ln.wallet("wal_abc123")
# Wallet info
info = w.get()
w.update(name="production")
# Sub-resources
w.key # Wallet key management (wk_ keys)
w.invoices # Create, list, get, watch invoices
w.payments # Send, list, get, watch, resolve payments
w.addresses # Create, list, delete, transfer Lightning addresses
w.transactions # List transaction history
w.webhooks # Create, list, delete webhook endpoints
w.events # Real-time SSE event stream
w.l402 # L402 paywall authentication
Account-level operations stay on the client:
ln.register() # Register new account
ln.me() # Get authenticated identity
ln.wallets.create() # Create wallet
ln.wallets.list() # List wallets
ln.keys.rotate(0) # Rotate account key
ln.invoices.create_for_wallet(...) # Public invoice by wallet ID
ln.invoices.create_for_address(...) # Public invoice by address
Async support
Every method has an async equivalent via AsyncLnBot:
from lnbot import AsyncLnBot
async with AsyncLnBot(api_key="uk_...") as ln:
w = ln.wallet("wal_...")
info = await w.get()
invoice = await w.invoices.create(amount=1000)
async for event in w.invoices.watch(invoice.number):
if event.event == "settled":
print("Paid!")
break
Error handling
from lnbot import LnBot, BadRequestError, UnauthorizedError, NotFoundError, ConflictError, LnBotError
try:
w.payments.create(target="invalid", amount=100)
except BadRequestError:
... # 400
except UnauthorizedError:
... # 401
except NotFoundError:
... # 404
except ConflictError:
... # 409
except LnBotError as e:
print(e.status, e.body)
Configuration
from lnbot import LnBot
ln = LnBot(
api_key="uk_...", # or set LNBOT_API_KEY env var
base_url="https://api.ln.bot", # optional — this is the default
timeout=30.0, # optional — request timeout in seconds
)
The API key can also be provided via the LNBOT_API_KEY environment variable. If both are provided, the constructor argument takes precedence.
L402 paywalls
w = ln.wallet("wal_...")
# Create a challenge (server side)
challenge = w.l402.create_challenge(amount=100, description="API access", expiry_seconds=3600)
# Pay the challenge (client side). max_fee works as for payments: leave it unset for the default.
result = w.l402.pay(www_authenticate=challenge.www_authenticate)
print(result.fee) # network fee charged
# Verify a token (server side, stateless)
v = w.l402.verify(authorization=result.authorization)
print(v.valid)
Features
- Zero extra dependencies — only
httpx - Wallet-scoped API —
ln.wallet(id)returns a typed scope with all sub-resources - Sync + async —
LnBotandAsyncLnBotwith identical APIs - Typed exceptions —
BadRequestError,NotFoundError,ConflictError,UnauthorizedError,ForbiddenError - SSE support —
watch()returns an iterator/async iterator for real-time events - Dataclass responses — all responses are frozen dataclasses
Requirements
- Python 3.10+
- Get your API key at ln.bot
Links
- ln.bot — website
- Documentation
- GitHub
- PyPI
Other SDKs
- TypeScript SDK · npm
- C# SDK · NuGet
- Go SDK · pkg.go.dev
- Rust SDK · crates.io · docs.rs
License
MIT
Metadata
Release files for lnbot 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| lnbot-1.1.0.tar.gz | 34.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lnbot-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.5 kB
Release files / lnbot-1.1.0.tar.gz
| Download URL | lnbot-1.1.0.tar.gz |
|---|---|
| Size | 34.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6652883d8d398da03865f60c2fad611b83dd2e8c23759657fadc9cb419d1593f
|
|
BLAKE2b-256 checksum How to use checksums |
b62e03170d1a73c817b116822965f564619fd928200239dd78145c449111b90a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / lnbot-1.1.0-py3-none-any.whl
| Download URL | lnbot-1.1.0-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09da0276a9ce8fa4fb841f469116f378bb2c804414c84b500249861d40d8eee4
|
|
BLAKE2b-256 checksum How to use checksums |
3608af93c5b3655f71b03055c851cce9a831a20cca3d9ccf64deff1d71af7a19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for lnbot 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.