Summary: Routstr is a Cashu-paid AI access market. The point is the packaging: provider onboarding, Nostr discovery, upstream-model resale, per-request billing, and change or refund handling. Useful operator middleware, not a base AI rail.
What it does:
Provides an OpenAI-compatible API surface for paid AI inference
Lets users pay for requests with Cashu ecash directly or with balance-backed API keys
Lets providers run Routstr nodes that connect to upstream AI APIs and resell that access with configurable margins
Uses Nostr for node identity and discovery so clients can find providers in an open network
Exposes provider dashboards for upstream configuration, pricing, balances, withdrawals, and admin controls
Supports stateless per-request payment flows with Cashu plus change/refund handling on API responses
Key claims:
The main README says Routstr is a decentralized protocol for permissionless, private, and censorship-resistant AI inference, combining Nostr for discovery with Cashu for private Bitcoin micropayments
That same README says Routstr Core is a FastAPI-based reverse proxy in front of OpenAI-compatible APIs that handles pay-per-request billing
The docs homepage says Routstr enables an open marketplace where anyone can buy and sell compute using Bitcoin eCash and explicitly separates client, provider, and API-reference workflows
The provider quick-start guide says a Routstr provider node connects to upstream AI providers such as OpenAI, Anthropic, or OpenRouter, accepts Bitcoin payments via Cashu ecash, and serves AI requests to clients on the network
The provider docs also say operators bring their own API keys while Routstr handles billing, payments, and client management, which makes the project look like reseller and marketplace infrastructure rather than a single hosted AI app
The API overview says Routstr exposes a complete OpenAI-compatible API plus payment-management endpoints, supports normal Authorization: Bearer sk-... keys, and also allows Cashu tokens directly in the Authorization header
That same API overview documents an X-Cashu flow where clients send a Cashu token per request and receive change in the response header, which is a strong sign that the project is designing stateless machine-payment infrastructure, not only prepaid user accounts
The docs say rate limits, dashboard endpoints, node info, and payment-required error semantics are all part of the platform surface, reinforcing that Routstr is an operational compute-and-payments control plane
Whitepaper: No canonical standalone Routstr whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official repo README and the first-party docs portal covering overview, provider setup, and API behavior; see ../whitepapers/routstr-primary-sources-2026-05-02.md.