Your first route.
Sign in, create your API key, and point your tools at Routim.
01. Endpoint & access
Sign in to your user console and create a key in API keys. The secret is shown only once.
Authenticate with Authorization: Bearer KEY or x-api-key: KEY. If you send both headers, the keys must match.
02. Terminal Codex
Add the provider below to your Codex configuration. Set ROUTIM_API_KEY in the client environment and select a model returned by the models endpoint.
model_provider = "routim" model = "claude-sonnet-5-5" [model_providers.routim] name = "Routim" base_url = "" env_key = "ROUTIM_API_KEY" wire_api = "responses" requires_openai_auth = false supports_websockets = false request_max_retries = 0 stream_max_retries = 0 [model_providers.routim.capabilities] remote_compaction = "unsupported"
03. Anthropic Messages
Send standard Messages requests to /api/v1/messages. Token counting is available at /api/v1/messages/count_tokens. List the available models with an authenticated GET /api/v1/models.
curl /messages \
-H "x-api-key: $ROUTIM_API_KEY" \
-H "content-type: application/json" \
-d '{"model":"claude-sonnet-5-5","max_tokens":256,
"messages":[{"role":"user","content":"Hello!"}]}'04. Continue a conversation
The Responses API supports previous_response_id and full context snapshots from Codex. When rotating credentials, issue the replacement key to the same client: its history and account affinity remain available.
05. Connect an account
Connect and authorize pool accounts through the server CLI. The console lets you inspect account state, choose models, adjust concurrency, and enable or disable accounts. OAuth tokens are never sent to the browser.