Sats4AI primary sources — 2026-05-03

Project status in this pass

• No canonical standalone Sats4AI whitepaper or litepaper surfaced.
• The clearest current source of truth is the homepage, llms.txt, the L402 services manifest, the MCP manifest, the OpenAPI spec, and the official GitHub READMEs.
• The project is best understood as Lightning-paid AI-services and paid-request infrastructure rather than as a generic AI-tool website.

Primary-source snapshots

1) Official homepage

• URL: https://sats4ai.com/
• Key excerpt:
  • The homepage says Sats4AI is a permissionless communication supercharger for humans and AI agents.
  • It emphasizes no account, no subscription, no API key, and no KYC, and says a Lightning invoice is the only credential.
  • It also advertises both human-facing and agent-facing use, with MCP configuration examples and more than 40 tools.

2) Official llms.txt

• URL: https://sats4ai.com/llms.txt
• Key excerpt:
  • The file explains the MCP endpoint, direct L402 HTTP routes, and the payment flow built around invoice creation and later tool invocation.
  • It lists free discovery endpoints alongside paid tools for image generation, text, translation, TTS, OCR, fax, SMS, AI calls, and more.
  • It notes that failed paid calls include an LNURL-withdraw refund link.

3) L402 services manifest

• URL: https://sats4ai.com/.well-known/l402-services
• Key excerpt:
  • The manifest says Sats4AI supports both L402 and MPP, publishes an onion service, and exposes model discovery, cost-estimation, and error-code endpoints.
  • It includes detailed service metadata such as pricing mode, latency p50/p95, reliability notes, and failure modes.
  • It also explicitly flags some endpoints as producing untrusted_output and provides prompt-injection handling guidance.

4) MCP manifest

• URL: https://sats4ai.com/.well-known/mcp
• Key excerpt:
  • The manifest describes a remote JSON-RPC MCP server with tools, resources, and async-task support.
  • It points to discovery endpoints, GitHub issues/discussions, and the hosted MCP package URL.
  • It reinforces that Sats4AI is packaging a first-class agent integration layer, not only a human website.

5) OpenAPI spec

• URL: https://sats4ai.com/api/openapi.json
• Key excerpt:
  • The spec repeats the L402 and MPP authentication formats, machine-readable error-code catalog, callback support, deduplication headers, async job mechanics, and refund behavior.
  • It shows that the product is not just a single payment pattern but a fairly mature paid-API platform with operational controls for routing, retries, and job tracking.

6) Official GitHub READMEs

• URLs:
  • https://raw.githubusercontent.com/cnghockey/sats4ai-mcp-server/main/README.md
  • https://raw.githubusercontent.com/cnghockey/sats4ai-l402-examples/main/README.md
• Key excerpt:
  • The MCP README frames the product as 33+ AI tools paid with Bitcoin Lightning and explains remote MCP use, stdio proxy fallback, helper tools, refunds, and service discovery.
  • The L402 examples README documents dual auth formats, async 202 Accepted polling, and LNURL-withdraw refunds, which helps confirm the platform is intentionally built as machine-usable paid-request infrastructure.

Working conclusion

Sats4AI is best cataloged as Lightning-paid agent-services infrastructure. The deciding evidence in this pass was the combination of MCP + HTTP delivery, dual L402/MPP payment auth, rich machine-readable discovery documents, refund and async-job handling, and explicit prompt-injection guidance for untrusted outputs.