AI Agents NEW

Why Lightning Is Perfect for AI Agents

MCP Server

The SatsRail MCP server gives any AI agent with Model Context Protocol support the ability to create orders, generate invoices, and check payment status.

Connect to the hosted server

SatsRail hosts the server at https://app.satsrail.com/api/v1/mcp. It speaks Streamable HTTP (one JSON-RPC message per POST), so there is nothing to install: point your client at the URL and authenticate with a secret key.

{
  "mcpServers": {
    "satsrail": {
      "type": "http",
      "url": "https://app.satsrail.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer sk_test_your_key_here" }
    }
  }
}

Works in Claude Code, Claude Desktop, Cursor, Windsurf and any Streamable-HTTP MCP client. Stdio-only clients can bridge to the URL with mcp-remote.

No key to paste? A client that supports OAuth connects with the URL alone: you sign in, pick the business and approve. Those connections manage your catalog and payment links only, and you can revoke them any time under Settings → AI Assistants.

Available Tools

The hosted server exposes 43 tools: orders, invoices, payments, checkout, payment links, products and the catalog, webhooks, wallets and account data. These are the core payment tools; tools/list returns them all:

Agent Payment Flow

A complete payment takes 3 steps — no browser involved at any point.

Example Conversation

Payment Links for Agents

A payment link (https://www.satsrail.com/pay/prod_…) opens the hosted checkout for one product at one price. It never expires and can be paid any number of times. That makes it the thing an agent hands to a person:

• Selling. The merchant's agent calls create_payment_link with a name and a price and gets back payment_link_url to send the customer. Every product the API returns carries its payment_link_url too (null while the product is inactive).
• Buying for someone. An agent that needs to pay a SatsRail merchant for the person it works for doesn't need a wallet, a key or a card: it sends that person the merchant's payment link, and they pay from their own wallet. The money goes straight to the merchant; the agent never holds funds.

Before forwarding a link, read it: the same URL with .json (or Accept: application/json) describes it and opens no checkout. No key is needed.

GET https://www.satsrail.com/pay/prod_4f1c9e2a7b3d8e6f5a1c0b9d.json

{
  "object": "payment_link",
  "url": "https://www.satsrail.com/pay/prod_4f1c9e2a7b3d8e6f5a1c0b9d",
  "name": "Sunset kayak tour",
  "amount_cents": 4500,
  "currency": "usd",
  "formatted_amount": "$45.00",
  "merchant": { "name": "Ember Tours" },
  "payable": true,
  "payment_methods": ["lightning"],
  "how_to_pay": "Open the url in a browser and pay from a bitcoin wallet. ..."
}

payable is false while the merchant has no wallet that can take the price; say so rather than send a link that shows an unavailable page. An inactive or unknown link answers 404.

Example Conversation

Direct REST API

Don't need MCP? Any agent that can make HTTP requests can use SatsRail directly. The entire flow is JSON in, JSON out — no redirects, no HTML.

Create order + invoice in one call

curl -X POST https://app.satsrail.com/api/v1/m/orders \
  -H "Authorization: Bearer sk_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "order": {
      "total_amount_cents": 2500,
      "currency": "usd"
    },
    "generate_invoice": true,
    "payment_method": "lightning"
  }'

Check payment status

curl https://app.satsrail.com/api/v1/m/invoices/{invoice_id}/status \
  -H "Authorization: Bearer sk_test_..."

Full API Reference →

Use Cases

Configuration