Axiomancer

Get started with RouteShift

Sign up for RouteShift, add a provider, mint a virtual key, and proxy your first request — ship a routed LLM call against any model in under ten minutes.

RouteShift analytics dashboard showing requests, actual spend, savings versus list price, a spend chart, model routing breakdown, and a recent requests table
RouteShift proxy analytics — spend versus list price, model routing, and a live request log.

Create your workspace

Sign up at app.routeshift.io. You'll need an admin email — a personal email is fine for solo accounts.

Add a provider key

Open Settings → Providers and paste in at least one upstream key (OpenAI, Anthropic, or any of the supported providers). RouteShift encrypts the key at rest with PROVIDER_KEY_SECRET and never returns the plaintext after save.

Mint a virtual key

Open Keys → Create key. Optionally set:

  • Allowed models — restrict which models this key can call.
  • Expires at — auto-revoke on a calendar date.
  • RPM / TPM — per-key requests- and tokens-per-minute caps.
  • Monthly budget — hard cap with optional soft-alert threshold.
  • Metadata — arbitrary key=value tags for cost attribution.

The dialog returns a one-time sk-proxy-… token. Copy it immediately — RouteShift hashes it on save and cannot show it again.

Proxy your first request

RouteShift is OpenAI-compatible. Any client that takes a base URL works — swap https://api.openai.com for https://api.routeshift.io and use your sk-proxy-… key:

curl https://api.routeshift.io/v1/chat/completions \
  -H "Authorization: Bearer sk-proxy-…" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o-mini",
    "messages": [{"role": "user", "content": "hello"}]
  }'

Review the request log

Open Activity. The request appears within seconds with tokens, cost in microcents, latency, the resolved upstream model, and an inferred activity category.

Need help? Email support@routeshift.io.

Was this page helpful?

On this page