Fewsats

• Name: Fewsats
• URL: https://fewsats.com/
• Category: account-linked agent-payments operator / API monetization tooling
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: Fewsats is an account-linked agent-payments operator sitting across L402/x402-style flows. The durable part is the approval and monetization plumbing, not the shopping demos. Real middleware, still not a protocol anchor.
• What it does:
  • Provides payment infrastructure for AI assistants and agent workflows, including API-key-backed MCP tooling for balance, payment-method lookup, offer payment, and payment-status retrieval
  • Publishes proxy402, a tool for putting x402 payment requirements in front of APIs and monetized routes, with support for Base-based payments and 402-response retry flows
  • Shows example agent-commerce integrations such as an Amazon shopping MCP flow for Claude and Cursor, including account setup, payment-method attachment, and purchase policy controls
  • Maintains ecosystem and developer resources around L402, including a curated awesome-L402 repository and additional supporting repos under the first-party GitHub org
  • Appears to bridge conventional payment methods and agent-oriented payment orchestration, with first-party docs mentioning card and wallet-linked approval flows rather than only crypto-native checkout
• Key claims:
  • The official GitHub organization description says “Payments for AI,” which is the clearest top-level positioning statement surfaced in this pass
  • The fewsats-mcp README says the MCP server integrates with Fewsats so AI agents can purchase “anything in a secure way,” and it exposes tools named balance, payment_methods, pay_offer, and payment_info
  • The fewsats-mcp setup requires a Fewsats API key, which suggests Fewsats is operating an account-linked payment and authorization layer rather than only publishing an open protocol wrapper
  • The proxy402 README says it lets users monetize APIs by requiring x402 payments on Base before endpoint access, returning 402s and forwarding the request after proof of payment; it also documents short-link route creation and a web UI for protected routes
  • The archived amazon-mcp README is still useful as historical evidence of product posture: account-linked payment methods, approval thresholds, manual review, and purchase-history controls mattered more than pure open-protocol elegance
  • The awesome-L402 repo shows Fewsats stewarding educational and ecosystem material around L402 rather than only shipping a closed product
  • Several first-party repos mix L402 and x402 language, so Fewsats appears to be operating across both Lightning-rooted machine-payment patterns and newer stablecoin/Base-oriented payment flows rather than committing to a single rail
• Whitepaper: No canonical standalone Fewsats whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the first-party GitHub organization and repositories; the public website URL was referenced throughout those sources, but the homepage itself did not yield readable extracted content in this pass. See ../whitepapers/fewsats-primary-sources-2026-05-02.md.
• Sources:
  • https://fewsats.com/
  • https://github.com/Fewsats
  • https://raw.githubusercontent.com/Fewsats/fewsats-mcp/main/README.md
  • https://raw.githubusercontent.com/Fewsats/proxy402/main/README.md
  • https://raw.githubusercontent.com/Fewsats/amazon-mcp/main/README.md
  • https://raw.githubusercontent.com/Fewsats/awesome-L402/main/README.md

Internal linkages

• Keep this note on the strongest protocol reads: l402 and x402.

Control surface

• The practical power sits in account creation, attached payment methods, approval thresholds, MCP access, and which monetized routes Fewsats intermediates or exposes.

• That matters more than the demo storefronts, but it is still operator-side approval plumbing riding above stronger paid-request rails.

• Read Fewsats upward toward L402 and x402, not as a standard-setting payments base layer.

• Last reviewed: 2026-06-04 UTC