Cowrie Research

fewsats-primary-sources-2026-05-02

3 min read

Fewsats primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth was Fewsats’ first-party GitHub organization and repository network.
  • The official website URL is referenced throughout those repos, but the homepage itself did not yield readable extracted content in this pass.
  • The repos jointly point to a broader AI-payments and API-monetization control plane rather than a single shopping or MCP demo.

Primary-source snapshots

1) GitHub organization overview

  • URL: https://github.com/Fewsats
  • Key excerpt:
    • The organization description says “Payments for AI.”
    • The public repo list includes fewsats-mcp, proxy402, awesome-L402, amazon-mcp, sherlock-mcp, and other payment- or commerce-adjacent tools.
    • Even without a rich homepage extract, the org surface already suggests that Fewsats is building infrastructure for AI purchasing and paid API access.

2) fewsats-mcp

  • URL: https://raw.githubusercontent.com/Fewsats/fewsats-mcp/main/README.md
  • Key excerpt:
    • The README says the MCP server integrates with Fewsats and allows AI agents to purchase “anything in a secure way.”
    • It exposes four tools: balance, payment_methods, pay_offer, and payment_info.
    • The documented configuration requires a FEWSATS_API_KEY, indicating that Fewsats is operating an authenticated payment/account layer behind the MCP interface.

3) proxy402

  • URL: https://raw.githubusercontent.com/Fewsats/proxy402/main/README.md
  • Key excerpt:
    • The README says Proxy402 lets users monetize APIs by requiring x402 payments on Base before endpoint access.
    • It documents a 402 flow where the client requests a protected resource, receives a 402 payment token, pays using Base, retries with proof of payment, and then gets the proxied response.
    • It also documents a web app and API flow for creating monetized routes, which suggests Fewsats is packaging operator tooling around paid API gating rather than only publishing a protocol sample.

4) amazon-mcp

  • URL: https://raw.githubusercontent.com/Fewsats/amazon-mcp/main/README.md
  • Key excerpt:
    • The repo is archived, but it still provides useful evidence about product posture.
    • It says users need a Fewsats account, can add payment methods including credit card, Apple Pay, or Google Pay, and obtain an API key from app.fewsats.com.
    • It also documents policy controls such as custom budget limits, approval thresholds, manual review, and purchase history, which is a strong sign of a spending-governance layer for AI assistants rather than a one-off shopping script.

5) awesome-L402

  • URL: https://raw.githubusercontent.com/Fewsats/awesome-L402/main/README.md
  • Key excerpt:
    • The repo curates protocol, library, project, tool, and company resources around L402.
    • It includes links to the L402 spec, builder resources, related libraries, and companies, including Fewsats itself.
    • This matters because it shows Fewsats publicly stewarding adjacent machine-payment knowledge and ecosystem mapping, not only a proprietary SaaS layer.

Working conclusion

Fewsats is best cataloged as agentic-payments and API-monetization infrastructure. The decisive evidence in this pass was the combination of an AI-payments positioning statement, an authenticated MCP server for offer payment and payment methods, x402 proxy tooling for monetizing APIs with 402 payment challenges, and example purchase-policy controls for AI shopping flows. One caveat is that the public homepage could not be cleanly extracted in this pass, so the GitHub org and repos served as the main primary-source surface.

Graph View