Theseus sits where your AI agents already talk. Work stays on your own models at your own prices — tool-driven agent turns included, on any inference server, no redeploy — and never reaches a third-party model provider. The frontier gets only what your levers send it. Every request is verified in the request path and every decision is recorded with its reason.
AI spend today is a maze: every prompt goes to whichever frontier model someone configured, at frontier prices, carrying whatever data it carries — and nobody can retrace a single hop. Theseus leaves a thread. Every request is routed deliberately, verified on the way, and recorded with the reason it went where it went.
Every routed request carries the pool, the resolved model, and the reason — audit-ready, per team.
Agents hard-code one frontier model and send it everything — the two-line commit message and the ten-file refactor cost the same premium tokens.
Prompts carry code, credentials and customer context to third-party APIs by default — even the traffic your own hardware could have served.
Model choice lives in scattered configs and env vars. When finance or security asks which model handled what, there is no record to point at.
Your agents keep speaking the protocols they already speak — OpenAI or Anthropic. Point them at Theseus, set the model to theseus-auto, and routing starts. No SDK, no rewrite, no sidecar.
{
"env": {
"ANTHROPIC_BASE_URL": "https://theseus.ciphero.ai/api/proxy",
"ANTHROPIC_AUTH_TOKEN": "your-router-key",
"ANTHROPIC_MODEL": "theseus-auto",
"ANTHROPIC_SMALL_FAST_MODEL": "theseus-local"
}
}
# Claude Code's background traffic now stays on your own models.
The whole integration is configuration. Cursor is one base-URL override; an OpenAI SDK is one base_url argument.
You define two destination pools: local — self-hosted, OpenAI- or Anthropic-compatible endpoints like a vLLM fleet, on infrastructure you control — and frontier — the third-party providers you already pay for. The router reads each request's shape and sends it to the cheapest pool that can actually do the job. Requests pass through Ciphero's router to get there; it keeps the decision and a digest of the prompt, never the prompt itself.
Destinations are plain provider endpoints with a key and a default model — added in the dashboard in a minute.
Every routed request passes through the Ciphero verification engine — the same layer that protects Orpheus's coding agents and Perseus's production apps. Secrets, PII and high-confidence prompt injection are caught in the request path, before the prompt reaches any provider — including the cheap one. Enterprise adds context-aware PII, your own thresholds, and review of what the model asks the agent to run.
A blocked request comes back as a well-formed model response your agent already knows how to display — streaming included. No broken sessions, no mystery 500s.
Pool, resolved model, routing reason, verification verdict — one record per request, per team. When someone asks "why did this go there," the answer is a filter, not an investigation.
The Overview shows what routed where and why — how much traffic stayed local, what it would have cost at frontier prices, and every individual decision in a feed you can read.
Decisions: every routed request across your team's agents — pool, model, and reason, the moment it happens.
Being straight about what isn't built yet is part of being a vendor worth trusting. These are in build now, not shipping today.
Ciphero's own routing model grades each request's difficulty and category against your pools' measured capabilities — routing by evidence, not just request shape.
"If this team's monthly spend passes $1,000, prefer the local pool." Policies compile into routing rules the same way Orpheus compiles verifiers from documents.
Daily and monthly token limits per destination that actually stop spend, with an alert before they do — not just a report after the fact.
OpenCode, Codex CLI and friends — anything that speaks the OpenAI or Anthropic protocol already works today; first-class setup guides are on the way.
Both tiers verify every request before it is routed. Community detects and routes. Enterprise governs — deeper detection, review of what comes back, and no ceiling.
Start on the free Community tier — 2,500 routed requests a month, no credit card — or book a 30-minute walkthrough and watch your own traffic route.