One model layer

Codex, Cursor, Aider, Continue, Claude Code, OpenHands, OpenClaw, and SDK clients can use stable profiles such as sage-router/frontier while the router handles provider policy.

429 failover

When a model, provider, API key, or subscription path rate-limits, Sage Router can fail over to another authorized route instead of forcing each coding tool to implement its own fallback stack.

Local plus hosted

Keep local Ollama and Tailnet routes in the fallback chain, then use hosted sk_sage_* keys for quotas, analytics, activation, and public edge access.

60-second coding agent setup

export OPENAI_BASE_URL=https://api.sagerouter.dev/v1
export OPENAI_API_KEY=sk_sage_your_generated_key

cat >> ~/.codex/config.toml <<'TOML'
[model_providers.sage-router]
name = "Sage Router"
base_url = "https://api.sagerouter.dev/v1/"
env_key = "OPENAI_API_KEY"
wire_api = "responses"

[profiles.sage-router]
model_provider = "sage-router"
model = "sage-router/frontier"
TOML

Multimodal routing

Image, audio, video, and document inputs route only to capable models, so coding agents do not accidentally send multimodal tasks to text-only routes.

Provider custody

Bring authorized provider keys, OAuth profiles, Dario paths, or local models. Sage Router public plans do not grant unauthorized provider access.

Route telemetry

Hosted routing records privacy-safe activation and route metadata so operators can see which path served a request without exposing provider secrets.

Why coding agents need a router

Agent teams tend to accumulate one-off configs for every tool. That creates drift: one provider key burns out, one tool cannot use local fallback, one client lacks multimodal routing, and one coding session fails when a provider 429s. A shared model router centralizes the policy once.

Next steps

Create an API key, configure Codex, browse integrations, or estimate routing fit.