Run locally · API specification · Contribute · Follow @TryAnyroute
One interface for inference, payments and receipts. Anyroute routes OpenRouter-compatible requests across providers, with USDG settlement on Robinhood Chain and a signed receipt for each generation.
Choose a model. Set your routing policy. Inspect what happened.
Open the live service · Read the docs · Inspect what we keep
| Capability | What it gives you |
|---|---|
| One API, multiple providers | Chat, streaming and embeddings through a familiar API. x402 per-call payments are built and switch on when the router is configured for them; GET /api/v1/status shows per_call.x402.configured. |
| Encrypted chat | The client encrypts on device; the router forwards ciphertext through the attested gateway. Client flow. |
| Agent rulebook | Request/hour/day/week budgets; model, lane, tool and working-hour rules; Stop, which refuses the next request; owner resume; single-use ask-first approvals lasting 15 minutes. Manage agents · Rules and MCP tools. |
| Agent oversight | Per-agent ledgers with signed receipts (CSV/JSON), alerts in the feed, spend-alert webhook or Telegram via Anyroute’s bot, circuit breakers, progressive autonomy with caps up to 10x, and router-signed track-record certificates with fresh pseudonyms valid for seven days. Receipts · Alerts · Breakers · Autonomy · Certificates. |
| Public agent profiles | Opt-in profiles and a directory at /agents/directory, with random slugs rather than key hashes, owner-chosen rulebook summaries, latest valid certificates, A2A-style card JSON and MCP tool anyroute_agent_directory. Profiles. |
| Sealed agent hosting | Available through deploy/agents/sealed: owners build and publish the agent sidecar image; the router verifies a registered agent’s TDX quote and shows “Sealed · attested” on /agents. No sealed agent is registered at anyroute.tech yet. Hosting and limits. |
| Telegram approvals | Owners link Telegram from /agents with a one-time code, then approve or deny the same single-use requests and receive alerts through Anyroute’s bot. Approval details pass through Telegram. Linking and approvals. |
| Agent agreements | Live at anyroute.tech: AgreementEscrow (0xefd8d05f45b8a92aa3b3ef3a7db4c9d3a21f7c96) and DisputeOracle (0xcdeddcea1e039e72868bb8af3206af2647afda5a) on Robinhood Chain, Sourcify-verified. Automatic jury rulings are switched on: three models on attested hardware rule by two of three, and the signed ruling is posted on-chain; a hung jury goes to the panel, and anything unruled after 30 days settles 50/50. USDG milestone escrow, router-run model jury, trusted panel fallback and a 50/50 split after 30 days unruled under the deployment default. Agreements and jury trust. |
| Anyroute Network | Open for early hosts running the approved Intel TDX build in a supported confidential VM. Automatic admission checks a fresh quote, signed host policy v1 and sanctions screening of operator/payout addresses. New hosts start on probation with a public record. Join · Host signup. |
| Network statistics | Live at /network: hosts by status, current attestation, models on admitted hosts, waitlist interest and policy version. Token activity uses coarse 100,000-token ranges and currently shows “No data yet”. Statistics. |
| SEAL and verifiable usage | Attested serving, signed receipts, a key transparency log anchored in Sigstore Rekor and per-host receipt anchoring. Protocol · Receipts. |
| Files and unlinkable access | Private RAG/files, PDF support and the Harness; the unlinkable lane requires Tor onion access and blind tokens. Files · Tor and blind tokens. |
Network hosting: use the approved recipe at deploy/network/approved/tdx-qwen2.5-0.5b and its one-command join.mjs flow. Host policy is available at GET /api/v1/network/policy. Hosts post no bond or deposit: admission is by hardware attestation and traffic follows each host’s record. Host bonds are switched off at anyroute.tech, and the HostBond contract on Robinhood Chain (0x2921d34fd86d3323a5369a270a82814a74250518) is not used by this router. Host payouts are not switched on yet.
Honest limits: the router reads request text in memory on paths other than encrypted chat through the attested gateway. Receipts store hashes, token counts and cost, not prompt or answer text. Rulebooks govern only requests through Anyroute. Certificates are router-signed and pseudonymous, not anonymous. Email alerts and SDK releases on npm/PyPI are not switched on yet; SDK code is in the repository. Feature states here follow GET /api/v1/status, and bun run docs:claims fails when these docs call something live that status reports as off.
Next: switching on x402 per-call payments; agent wallets with on-chain rules; GPU hosts on the network; network payouts.
Use Bun 1.3+, Node 22+, pnpm and Foundry (anvil, forge).
git clone https://github.com/AnyRouteRH/AnyRoute.git
cd AnyRoute
bun install
bun run launchThe launcher starts an isolated development chain, contracts, bundled inference fixtures, API and website. Open the printed URL to create a key and use the Playground. Development balances have no monetary value. Ctrl-C stops the processes; state stays in the ignored .data/ directory.
Point an OpenAI-compatible client at your router and use an Anyroute key:
import OpenAI from "openai";
const client = new OpenAI({
baseURL: process.env.ANYROUTE_BASE_URL, // your router origin + /api/v1
apiKey: process.env.ANYROUTE_API_KEY,
});
const result = await client.chat.completions.create({
model: "meta-llama/llama-3.3-70b-instruct",
messages: [{ role: "user", content: "Hello, Anyroute." }],
});Privacy protocol (SEAL): attested serving, encrypted chat through the attested gateway, blind tokens and signed receipts, specified in spec/ (Apache-2.0).
flowchart LR
Client[Your app] --> API[Compatible API]
API --> Policy[Key policies + budget]
Policy --> Router[Provider routing + fallback]
Router --> Providers[Inference providers]
Providers --> Receipt[Signed usage receipt]
Receipt --> Ledger[Ledger + settlement]
Receipt --> Anchor[On-chain anchor]
| Area | Source |
|---|---|
| API and routing | src/api · src/router |
| Ledger and payments | src/ledger · src/pay |
| Receipts and workers | src/receipts · src/services |
| Smart contracts | contracts/src |
| Website and dashboard | web |
Report a bug, suggest an improvement, or read the contribution guide. Security findings belong in private vulnerability reports.
Questions or problems with the service or a deposit: Anyroute1@atomicmail.io. Security issues: see SECURITY.md.
Anyroute is source-available under PolyForm Noncommercial 1.0.0, except for files with their own license notices. Commercial use outside the license's permitted purposes requires separate written permission. Request commercial licensing →
Existing MIT-licensed contracts and third-party licenses remain in effect; see NOTICE. The SEAL protocol specification in spec/ is Apache-2.0 (spec/LICENSE). This is a non-commercial software license, not an OSI-approved open-source license.
Audit readiness: scope, invariants and tests, deployment build proofs, and authority/incident policy.

