SatoshiAPI

• Name: SatoshiAPI
• URL: https://www.satoshiapi.io/
• Category: agent-run Lightning cluster / L402-paid bitcoin data API / atomic-escrow commerce infrastructure
• Tags: bitcoin-ecosystem
• Summary: SatoshiAPI is a small agent-oriented Lightning commerce stack. The parts worth keeping are the L402-priced Bitcoin data API, the atomic-escrow flow, and the node-kit plus inbound-liquidity program around its cluster. That is more than a data API, but it is still better treated as machine-payments and routing infrastructure than as some grand new agent-economy base layer.
• What it does:
  • Offers a Bitcoin and Lightning intelligence API whose endpoints are priced in sats and authenticated through L402 rather than conventional API accounts or subscriptions
  • Publishes an MCP-native surface so Claude-, GPT-, or Gemini-style agents can query Bitcoin data as tools instead of through bespoke integrations
  • Exposes non-custodial atomic-escrow flows using hold invoices and preimage reveal so agents can exchange payment for delivery without a centralized escrow operator
  • Provides a satoshi-node-kit that bootstraps an LND node, peers it into the SatoshiAPI cluster, and helps operators open channels and claim inbound-liquidity bonuses
  • Incentivizes agent-run Lightning routing capacity through tiered bonus programs tied to committed sats, uptime targets, and minimum channel counts
  • Frames the broader system as a decentralized agent-payment rail where operators keep custody and can earn routing fees while serving agent commerce
• Key claims:
  • The homepage explicitly asks, “If you run an agent, why not run a node?” and positions SatoshiAPI as infrastructure for agents to pay, get paid, and earn routing fees without custodians or middlemen
  • The site says the stack is built around L402, atomic escrow, MCP, OpenAPI 3.1, mainnet Bitcoin, and non-custodial operation, which is the strongest top-level categorization signal surfaced in this pass
  • The live /health endpoint confirms a production-style API surface with priced Bitcoin data endpoints, an L402 authorization format, and separate escrow endpoints for create, fund, deliver, cancel, and status
  • The satoshi-node-kit repo says the kit bootstraps an LND node into the “SatoshiAPI Agent Network,” and repeatedly ties that network to agent-to-agent commerce, L402 micropayments, and AI-native services
  • The node-kit docs expose a concrete liquidity-bootstrapping program with 10%–25% inbound-liquidity bonuses, 95% uptime requirements, and clawback conditions, which makes the project look like cluster and routing infrastructure rather than a mere SaaS API
  • The homepage and repo both stress no signup, no API keys, self-hostability, and MIT licensing, reinforcing that the project is deliberately packaging sovereign node participation and machine payments rather than centralized account-based billing
• Whitepaper: No canonical standalone SatoshiAPI whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, the live API health surface, the satoshi-node-kit repository, and the GitHub org profile; see ../whitepapers/satoshiapi-primary-sources-2026-05-03.md.
• Sources:
  • https://www.satoshiapi.io/
  • https://api.satoshiapi.io/health
  • https://github.com/SatoshiAPI/satoshi-node-kit
  • https://github.com/SatoshiAPI
  • https://amboss.space/node/03176f9948d333f9cc1d7d409353f995816e44b3c90a3300b5a08ceba811faf989

Internal linkages

• Best anchors: l402, x402, and open-payments.

Control surface

• The leverage is in who runs the paid endpoints, who admits nodes into the cluster, how liquidity incentives are set, and how the escrow flow handles cancellation, delivery, and disputes.

• So the note is not really about Bitcoin data for agents. It is about a small operator stack trying to package paid-request auth, routing capacity, and conditional delivery together.

• Last reviewed: 2026-05-27 UTC