L402 Kit
Call L402 micropayment-gated HTTP APIs from your agent using Bitcoin Lightning sats per request instead of flat API subscriptions.
Overview
l402-kit is a MCP server for the Build phase that connects agents to L402-protected APIs using Bitcoin Lightning pay-per-call pricing in sats.
What is this MCP server?
- MCP server for L402-protected APIs with Bitcoin Lightning pay-per-call in sats
- npm package l402-kit (registry v1.8.7) with stdio transport
- Enables metered AI tool usage without traditional API key billing alone
- Targets HTTP APIs that return 402 Payment Required with Lightning flow
- Useful for indie builders experimenting with open paid tool marketplaces
- Registry version 1.8.7
- npm identifier: l402-kit
- Transport: stdio; protocol focus: L402 + Bitcoin Lightning
Community signal: 2 GitHub stars.
What problem does it solve?
You want agent-callable paid APIs but subscription keys and flat billing do not match occasional or per-task usage.
Who is it for?
Builders already using or offering Lightning/L402 APIs who want MCP-native pay-per-call tool access from Claude Code-style hosts.
Skip if: Teams that need card-based SaaS billing only, or anyone without Lightning/L402 infrastructure on the client or API side.
What do I get? / Deliverables
Your agent can complete L402 Lightning payment flows and invoke metered external tools per request in sats.
- stdio MCP server that negotiates L402 Lightning payments for protected API calls
- Agent-accessible metered tool endpoints billed per request in sats
Recommended MCP Servers
Journey fit
Shelved under Build integrations because you wire pay-per-call API access while composing agent tools and backend hooks. integrations fits an MCP bridge to external paid APIs protected by L402 and Lightning invoices.
How it compares
Lightning L402 payments MCP bridge, not a Stripe billing skill or generic REST API wrapper.
Common Questions / FAQ
Who is l402-kit for?
Solo builders and tool authors integrating Bitcoin Lightning micropayments into agent workflows via L402-gated HTTP APIs.
When should I use l402-kit?
When you are wiring Build-phase integrations to APIs that require L402 payment per call rather than a simple static API key.
How do I add l402-kit to my agent?
Install the npm package l402-kit, configure it as a stdio MCP server in your host, and ensure your Lightning/L402 wallet setup matches the APIs you call.