Cowrie Research

satoshiapi-primary-sources-2026-05-03

3 min read

SatoshiAPI primary sources — 2026-05-03

Project status in this pass

  • No canonical whitepaper or litepaper surfaced in this pass.
  • The clearest current sources of truth were the official homepage, the live /health endpoint, the satoshi-node-kit repository, and the GitHub org profile.
  • The materials consistently frame SatoshiAPI as agent-oriented Lightning commerce infrastructure rather than as only a hosted Bitcoin data API.

Primary-source snapshots

1) Official homepage

  • URL: https://www.satoshiapi.io/
  • Key excerpt:
    • The homepage positions SatoshiAPI around the question “If you run an agent, why not run a node?” and argues that agents should hold and route money through their own Lightning nodes.
    • It highlights L402, atomic escrow, MCP, OpenAPI 3.1, mainnet Bitcoin, and non-custodial operation as core building blocks.
    • It also markets a founding-node program with inbound-liquidity bonuses and a one-command setup path, showing that node participation is central to the product, not a side feature.

2) Live health endpoint

  • URL: https://api.satoshiapi.io/health
  • Key excerpt:
    • The health payload identifies the service as “Satoshi BTC Intelligence API” and lists priced endpoints such as /price, /mempool, /signal, /whale, /market/regime, and /risk/score.
    • It documents the authorization pattern as Authorization: L402 <macaroon_base64>:<preimage_hex>.
    • It separately exposes escrow endpoints for create, fund, deliver, cancel, and status, which is strong evidence that escrow is a first-class product surface rather than only homepage copy.

3) satoshi-node-kit repository

  • URL: https://github.com/SatoshiAPI/satoshi-node-kit
  • Key excerpt:
    • The repo says the node kit “bootstraps your LND node and connects it to the SatoshiAPI Agent Network.”
    • It ties that network explicitly to agent-to-agent commerce, L402 micropayments, and AI-native services.
    • The README documents one-command bootstrap, tiered inbound-liquidity bonuses, uptime requirements, channel minimums, and cluster peering scripts, which makes the project look like routing and network-formation infrastructure.

4) GitHub org profile

  • URL: https://github.com/SatoshiAPI
  • Key excerpt:
    • The org profile describes SatoshiAPI as “Bitcoin-native Bionic” and says it is “Building L402 Lightning services.”
    • It also points back to satoshiapi.io and surfaces satoshi-node-kit as the main public repository.
    • This helps connect the hosted API, the node-bootstrap tooling, and the Lightning-services framing into one first-party source set.

5) Node identity surfaced by the homepage

  • URL: https://amboss.space/node/03176f9948d333f9cc1d7d409353f995816e44b3c90a3300b5a08ceba811faf989
  • Key excerpt:
    • The homepage publishes a specific Lightning node pubkey and links it on Amboss.
    • Even without treating Amboss as an authority on its own, the explicit first-party linkage is useful because it shows SatoshiAPI wants to be evaluated as a real Lightning-routing participant, not just an API facade.
    • This supports the categorization of SatoshiAPI as a payment-and-routing infrastructure project.

Working conclusion

SatoshiAPI is best cataloged as agent-run Lightning commerce infrastructure. The decisive signals are the combination of L402-priced Bitcoin intelligence endpoints, native MCP/OpenAPI surfaces, non-custodial atomic escrow, and a one-command LND cluster-onboarding flow that recruits additional sovereign routing capacity into the network.

Graph View