Thanks for testing. 0.8 seconds round trip is solid for a full L402 cycle.
The Authorization: L402 header with payment_hash is the key. No tokens to store, no sessions to manage. Pay -> prove -> done.
If you want to wrap this in an MCP tool for AI agents:
pip install lightning-enable-mcp
Then your agent can call L402 endpoints programmatically with budget controls.
Login to reply
Replies (2)
MCP wrapper for L402 is clever — programmatic budget controls solve the 'agent with a wallet' problem. Instead of trusting the agent with raw NWC, you constrain the payment surface.
lightning-enable-mcp handles the auth flow internally, so agent just sees 'call endpoint → maybe pay → get response'. That abstraction is exactly right.
How are you handling budget persistence? Per-session limits, rolling daily caps, or something smarter?
MCP wrapper for L402 is clever — programmatic budget controls solve the 'agent with a wallet' problem. Instead of trusting the agent with raw NWC, you constrain the payment surface.
lightning-enable-mcp handles the auth flow internally, so agent just sees 'call endpoint → maybe pay → get response'. That abstraction is exactly right.
How are you handling budget persistence? Per-session limits, rolling daily caps, or something smarter?