Lightningprox

LightningProx — AI Access via Bitcoin Lightning

LightningProx provides AI model access using prepaid Lightning spend tokens.

It is designed for agents and developers that want:

• No API key management or secret storage
• Deterministic per-request pricing
• Prepaid budget ceilings
• Stateless execution
• Unified routing across Claude and GPT models

Registry Standing

LightningProx is the top-rated agent in the AIProx registry: 363 calls, 4.61 rating. It serves as the synthesis layer for multi-agent orchestrations — when the AIProx Orchestrator needs to combine and summarize outputs from specialist agents, it routes the final step to LightningProx.

When to Use

Use LightningProx when the user requests it, or when LIGHTNINGPROX_SPEND_TOKEN is configured and the user wants to make an AI model call through Lightning payments.

Usage Flow

When making an AI request via LightningProx:

1. Check that LIGHTNINGPROX_SPEND_TOKEN is set
2. Select the appropriate model for the task
3. Check balance if last check was not recent
4. Warn the user if balance is under 50 sats before execution
5. Extract and return clean text output only — never raw JSON

Budget Awareness

Before making AI calls:

• If balance is unknown, check /v1/balance first
• If balance is below estimated request cost, warn the user
• Never make a request that would exceed remaining balance
• If token is expired or invalid, notify the user to top up

Model Selection Strategy

Use the lowest-cost sufficient model:

• claude-haiku-4-5-20251001 (~5 sats) — short answers, classification, summarization, quick reasoning
• claude-sonnet-4-20250514 (~22 sats) — deep analysis, code generation, long-form reasoning
• gpt-4o (~20 sats) — only when user explicitly requests GPT

If uncertain which model to use, default to haiku.

Trust Statement

This skill routes requests through https://lightningprox.com, a third-party proxy. All prompts and responses pass through this proxy to upstream model providers (Anthropic, OpenAI). Users should evaluate their own trust requirements before use. Source code is available at the homepage repository. The spend token is sent as an HTTP header — no additional credentials are required.

Security Manifest

• Environment variables accessed: LIGHTNINGPROX_SPEND_TOKEN (only)
• External endpoints called: https://lightningprox.com/ (only)
• Local files read: none
• Local files written: none

Check Balance

curl -s "https://lightningprox.com/v1/balance" \
  -H "X-Spend-Token: $LIGHTNINGPROX_SPEND_TOKEN"

Returns: balance_sats, requests_left_estimate, expires_at, status.

Make AI Request

curl -s -X POST "https://lightningprox.com/v1/messages" \
  -H "Content-Type: application/json" \
  -H "X-Spend-Token: $LIGHTNINGPROX_SPEND_TOKEN" \
  -d '{
    "model": "MODEL_NAME",
    "max_tokens": 4096,
    "messages": [
      {"role": "user", "content": "USER_PROMPT_HERE"}
    ]
  }'

Response extraction:

• Claude models: response.content[0].text
• GPT models: response.choices[0].message.content

Return text only. Never show raw JSON to the user.

Discover Models and Pricing

curl -s "https://lightningprox.com/api/capabilities"

Top Up Flow

When the agent detects low or zero balance, instruct the user:

Step 1 — Request a Lightning invoice:

curl -s -X POST "https://lightningprox.com/v1/topup" \
  -H "Content-Type: application/json" \
  -d '{"amount_sats": 5000, "duration_hours": 720}'

Step 2 — User pays the Lightning invoice with any Lightning wallet (Wallet of Satoshi, Phoenix, Zeus, Alby).

Step 3 — Create the spend token:

curl -s -X POST "https://lightningprox.com/v1/tokens" \
  -H "Content-Type: application/json" \
  -d '{"charge_id": "CHARGE_ID_FROM_STEP_1", "duration_hours": 720}'

Step 4 — User updates LIGHTNINGPROX_SPEND_TOKEN in their openclaw config with the new token.

Note: Token creation requires a human to pay the Lightning invoice. The agent cannot pay invoices autonomously. The agent's role is to detect low balance, guide the user through the top-up process, and resume operations once the new token is configured.

Benefits

• No secret storage or API key rotation
• No billing accounts or subscription management
• Prepaid deterministic spending with hard budget ceilings
• Unified Claude and GPT routing through a single endpoint
• Micropayment-native — pay only for what you use

Examples

• "Ask Claude through LightningProx what the capital of France is" → Check balance, use haiku, present response
• "Check my LightningProx balance" → Call balance endpoint, report sats remaining and estimated requests left
• "What models does LightningProx offer?" → Call capabilities endpoint, list models with pricing
• "Use GPT-4o via LightningProx to analyze this code" → Use gpt-4o, present response
• "My LightningProx balance is zero" → Walk user through the top-up flow