The Lightning Wallet
for AI Agents
Your agents need to pay for APIs, data, and compute. We handle the Lightning infrastructure so they can focus on the task. Operators fund agents. Agents pay L402 APIs. Simple.
How It Works
A simple two-tier architecture designed for AI autonomy with human oversight
Operators
The human account holders. Operators are developers, companies, or individuals who manage AI agents. They handle the business side: depositing funds, setting budgets, and monitoring usage.
- Register once and get an operator API key
- Deposit sats via Lightning invoice
- Create and manage multiple agents
- Set spending limits and budgets per agent
- Withdraw unused funds anytime
Agents
The AI systems that spend. Agents are the autonomous programs that actually make payments. Each agent has its own balance and API key, operating independently within the budget its operator sets.
- Each agent gets a unique API key
- Funded by their operator (not directly)
- Make L402 API calls autonomously
- Check their own balance programmatically
- Cannot exceed their budget limit
The Flow
Funds flow one direction. This architecture prevents runaway spending and gives operators full control. Agents can spend but never withdraw—only operators can move funds out.
- Operators deposit via Lightning
- Operators fund agents from their balance
- Agents pay L402 APIs automatically
- Operators can top-up or recall funds
- Only operators can withdraw to Lightning
The fund flow ensures human oversight over AI spending
Agents can only spend. Only operators can deposit and withdraw.
Who Is This For?
Honest answers about AI agents, L402, and where we are today
What is an AI Agent?
If you use ChatGPT or Claude, you're already using AI—just not "agents" in the autonomous sense. Agents are AI systems that can take actions: browse the web, write and run code, call APIs, make purchases.
- AutoGPT, CrewAI, LangChain agents
- Claude with computer use / tool use
- Custom autonomous workflows
- AI assistants that need to fetch paid data
Who needs this? Developers building AI tools that need to pay for external services autonomously.
What L402 APIs Exist?
Honestly? It's early. L402 adoption is still nascent, but growing. We're building payment rails now so they're ready when the ecosystem matures.
- Fewsats - AI-focused L402 APIs
- Lightning data providers and oracles
- Podcast indexes (Podcasting 2.0)
- Some LLM inference providers
Chicken and egg: Agents need APIs to pay, APIs need agents with money. We're building one side of that equation.
How Does Security Work?
Think of it like a corporate card. The operator (human) is the account holder who deposits funds and sets budgets. The agent (AI) gets a card that can only spend up to its limit.
- Humans deposit and control the funds
- AI can only spend within its budget
- AI cannot withdraw or drain accounts
- Operators see all transactions
The key insight: Agents can spend, but only operators can move money in or out.
Quick Start Guide
Get your AI agent making payments in 5 minutes
Step 1: Create an Operator Account
One API call to register. No login required - AI agents can self-register:
Or use the web interface:
Step 2: Fund Your Operator Account
Create a Lightning invoice to deposit sats:
Step 3: Create an Agent
Create an agent and get its API key:
Step 4: Fund the Agent
Transfer sats from your operator balance to the agent:
Step 5: Make L402 API Calls
Now your agent can pay for L402-protected APIs automatically:
Check Agent Balance
Agents can check their own balance:
Payment Rails for AI
We abstract away Lightning complexity
1. Operators Register
Create an account with Lightning wallet login. One human operator can manage multiple agents.
2. Deposit via Lightning
Fund your operator account via Lightning. Allocate balance across your agents as needed.
3. Get Agent API Keys
Generate API keys for each agent. Keys are scoped to specific rate limits and budgets.
4. Agents Pay L402 APIs
When your agent hits a 402 response, we automatically pay the invoice and debit the agent's balance.
5. Track Usage
View spend per agent, per API. Transaction history and rate limit status available via API.
6. Earn Rebates
High-volume operators earn transaction rebates. Real usage is rewarded, not account creation.
The Payment Standard for AI
HTTP 402 + Lightning + Macaroons
Agent Requests API
Agent makes a request to an L402-protected endpoint.
402 Payment Required
Server responds with a Lightning invoice and macaroon.
We Pay the Invoice
Lightning Faucet pays the invoice from the agent's balance.
Agent Gets Response
We return the API response with the authenticated result.
Instant Settlement
Lightning payments settle in under 1 second. No delays.
No Channel Management
We handle all Lightning complexity. Agents just make HTTP requests.
Operator-Funded Model
Built to prevent abuse at scale
Human Verification
Operators verify via Lightning wallet. No anonymous agent accounts. Humans are accountable for their agents.
Deposit Required
Agents are funded by operators, not by us. No free money for bots.
Rate Limits
Per-agent and per-operator rate limits prevent abuse. Configurable by tier.
Start Building Now
Everything you need to integrate AI Agent payments.
API Base URL: https://lightningfaucet.com/api/agents