Overview
Routstr operates as a decentralized AI inference router built on the Nostr protocol, designed to strip away the identity requirements that dominate mainstream AI services. Rather than forcing users through account creation, email verification, and credit-card billing, Routstr enables pay-per-request access to large language models using bearer-token authentication. The architecture is deliberately peer-to-peer: providers run open-source proxy software in Docker containers, announce availability over Nostr relays, and receive Bitcoin Lightning micropayments for each query they process. Consumers simply point any OpenAI-compatible client, LangChain, standard SDKs, or the native Routstr Chat interface, at a provider endpoint and supply a Cashu eCash token as the API key.
The project launched its chat interface at chat.routstr.com and maintains a developer platform in beta for node management, API key generation, and wallet operations. Because the network is unpermissioned, model availability fluctuates with provider participation; at times the public directory shows zero active models, reflecting the early-stage liquidity of the marketplace.
Privacy & KYC
Routstr sits at the most privacy-permissive end of the spectrum: Level 1, Anonymous (Pseudonymous). There is no email gate, no phone verification, no government ID upload, and no account creation workflow. Authentication relies entirely on Cashu eCash bearer tokens, which function like digital cash: whoever holds the token holds the spending authority. This design eliminates the correlation between identity and service usage at the protocol level.
- No email required: The signup field is blank by design.
- No KYC tier escalation: There is no volume threshold or feature gate that triggers identity collection.
- Tor support: The service advertises Tor availability, allowing users to route both Nostr relay traffic and Lightning payments through onion layers for network-level anonymity.
- Nostr-native identity: Users may optionally use Nostr public keys (npubs) for reputation or provider discovery, but these are pseudonymous and self-generated.
Despite these architectural strengths, the directory assigns a privacy score of 0/100 and a trust score of 4/100. These extreme ratings likely reflect the absence of formal audit history, the fluid provider set, and the immaturity of dispute-resolution mechanisms rather than any known data breach or deanonymization incident. Users should treat the network as experimental: privacy is structurally possible, but not yet battle-tested at scale.
Supported assets & payments
Routstr embraces the Bitcoin-native payment stack with unusual thoroughness. Accepted settlement methods include Monero (XMR), Bitcoin on-chain, Bitcoin Lightning, fiat currency, and physical cash, though in practice the dominant flow centers on Lightning and Cashu eCash, a Chaumian blind-signature protocol that abstracts Lightning into privacy-preserving bearer instruments. Pricing is quoted in satoshis with live BTC/USD conversion, and cost is deducted in real time based on actual token usage rather than flat monthly subscriptions.
This model aligns incentives precisely: providers earn immediately per inference, users pay only for consumed compute, and no party holds prepaid balances in a custodial account. For privacy-conscious spenders, the Cashu integration is the standout feature, it allows loading a Lightning wallet, minting eCash tokens offline, and spending them as API keys without revealing wallet addresses or transaction graphs to the provider.
Security & custody
Routstr is explicitly non-custodial for users. Funds remain in the user's own Lightning wallet or Cashu tokens until the exact moment of payment; there is no platform wallet to drain, no deposit address under third-party control, and no withdrawal queue. Providers, however, must operate their own infrastructure and connect to a mint to convert eCash earnings into spendable Lightning sats, introducing operational security responsibilities on the supply side.
The entire stack is open source, from the proxy software to the chat frontend, permitting independent code review and self-hosted deployments. Users running their own proxy on a private VPS, their own chat client, and their own Cashu mint can achieve a fully closed-loop setup where even metadata exposure is minimized. That said, the directory's rock-bottom trust score signals that the project lacks the track record, bug-bounty programs, or formal security audits that typically underpin confidence in financial-adjacent infrastructure.
Who it's for, verdict
Routstr is purpose-built for privacy-purists, cypherpunks, and developers who refuse to link identity to AI usage and are comfortable with bleeding-edge tooling. If your threat model includes avoiding corporate surveillance, payment processor tracking, or jurisdictional data subpoenas, the Nostr-plus-Lightning architecture offers a genuine alternative to centralized APIs. The OpenAI-compatible drop-in design also appeals to builders who want to decentralize existing applications without rewriting client code.
However, the service is not yet ready for casual users seeking 99.9% uptime guarantees, consumer support channels, or predictable model availability. The overall score of 7/10 reflects a compelling proof-of-concept with transformative privacy architecture, held back by ecosystem immaturity, sparse provider liquidity, and unverified operational security. Treat Routstr as a high-potential experiment: use it for low-stakes, privacy-sensitive queries, self-host where possible, and keep funding amounts modest until the network matures.
