Routstr

What is Routstr

Routstr is a decentralized protocol for AI inference built on Nostr and Bitcoin. As of 2026-05-30, it operates as a reverse proxy network where independent providers host OpenAI-compatible API endpoints, and users pay per request using Cashu eCash tokens or Bitcoin Lightning. The project maintains open-source core infrastructure at routstr-core, a FastAPI-based proxy that handles authentication, billing, and request routing.

The service targets developers and privacy-conscious users who want API access to AI models without platform lock-in, subscription fees, or identity verification. Providers announce themselves via Nostr relays, creating a distributed discovery layer without central registries.

How no-KYC is it?

Routstr delivers on its "no accounts, no emails, no sign-ups" promise. Users generate or obtain Cashu eCash tokens-blinded, privacy-preserving Bitcoin bearer instruments-and use them directly as API keys. No personal information is collected at any stage. The setup explicitly avoids credit cards, billing addresses, or identity documents.

The protocol's architecture supports this: Nostr public keys serve as the only identifiers, and Cashu payments provide unlinkable transactions. This represents a genuine "Guaranteed no KYC" implementation rather than a policy claim that could change with regulatory pressure.

Privacy & security

Privacy is architectural, not merely promised. Cashu eCash provides blind signatures that prevent the mint from linking payments to specific requests. Nostr relays handle provider discovery without requiring user registration. The official documentation notes Tor support for additional network-layer privacy.

However, users should understand the threat model: individual providers see request content (prompts and completions), though not payment source identity. The protocol does not appear to implement end-to-end encryption between user and provider-traffic flows through the provider's inference endpoint. The 60% trust score from legacy assessments likely reflects this provider-risk model and the project's early-stage decentralization.

The open-source codebase (AGPL-3.0 per GitHub) permits security auditing, though no formal audit reports surfaced in the evidence.

Payments, fees & limits

Routstr uses a pure pay-per-request model with no subscriptions or minimum balances. Pricing is provider-determined, visible at discovery time, and settled in real-time via Cashu or Lightning. The official site emphasizes "pay precisely for the tokens you generate."

Cashu tokens function as prepaid API keys: users load value at any Cashu mint, then spend incrementally per inference call. Lightning enables direct payment flows without custodial accounts. No fiat on-ramps are mentioned or required.

The OpenClaw deployment option allows self-hosting with automatic top-up management, suggesting users can configure spending limits and automatic refills.

User experience & support

Integration appears deliberately simple for developers: change two lines in existing OpenAI SDK usage (base_url and api_key pointing to a Cashu token). The protocol is compatible with LangChain, desktop applications, and any OpenAI-compatible client.

For non-technical users, the barrier is higher. Obtaining Cashu tokens requires understanding Bitcoin Lightning wallets and eCash mints. The OpenClaw project extends accessibility by offering one-command VPS deployment via LNVPS (Lightning-paid hosting) with pre-configured Routstr connectivity.

Documentation exists at docs.routstr.com covering architecture, client/provider guides, and API references. No traditional support channels (chat, ticket system) were evident; community support likely flows through Nostr and GitHub.

Who it's for

Routstr suits developers building AI-powered applications who need programmatic access without platform risk, privacy-conscious individuals seeking uncensorable AI access, and Bitcoin-native users already comfortable with Lightning and Cashu workflows. It also appeals to hardware owners wanting to monetize GPU resources permissionlessly.

It is not yet suited for users needing consumer-grade simplicity, guaranteed uptime SLAs, or regulatory compliance assurances. The decentralized provider model trades convenience for censorship resistance and privacy.