A pool that knows its limits.
The router selects an eligible account from the operator-managed pool. Account state, concurrency, and cooldowns determine availability.
Connect your tools to a shared Claude account pool. One endpoint, saved conversation context, and API keys you control.
Codex, Claude Code,
or your own integration.
Route requests.
Carry context forward.
/api/v1Account availability,
concurrency, and cooldowns.
Your keys, usage, and conversations.
Pool credentials stay with the operator.The routing layer between a managed account pool and your everyday workflow.
Explore the consoleThe router selects an eligible account from the operator-managed pool. Account state, concurrency, and cooldowns determine availability.
Saved conversations retain their history and account affinity across turns. Stable prompt prefixes support upstream caching; cache hits depend on the provider.
Issue and revoke keys for your tools. Conversations belong to your client identity, so replacing a key keeps its history and account affinity.
Use Anthropic Messages or OpenAI Responses with a Routim base URL and API key. Choose a configured model and follow the connection guide for your client.
Connection guideCodex / Claude Code / Your API client
curl /messages \ -H "x-api-key: $ROUTIM_API_KEY" \ -H "content-type: application/json" \ -d "{ \"model\": \"$ROUTIM_MODEL\", \"max_tokens\": 256, \"messages\": [{ \"role\": \"user\", \"content\": \"Hello, Routim.\" }] }"
curl /responses \ -H "authorization: Bearer $ROUTIM_API_KEY" \ -H "content-type: application/json" \ -d "{ \"model\": \"$ROUTIM_MODEL\", \"input\": \"Hello, Routim.\", \"stream\": true }"
Set ROUTIM_API_KEY to your key and ROUTIM_MODEL to a configured model. Examples are copied, never executed here.
Sign Up and Login both open the same secure sign-in window in the console. Use Google, GitHub, or email when enabled by the operator. Then create an API key and follow the connection guide. Service availability depends on the configured account pool.
Routim supports Anthropic Messages and OpenAI Responses, including streaming and tool cycles. OpenAI Responses is an API format here; requests are routed to Claude. Model availability and request limits depend on the configured pool.
Issue the replacement key to the same client. Conversation history and account affinity belong to that client, so they stay available after the old key is revoked.
Routim stores account credentials and conversation content encrypted in PostgreSQL, and stores API keys as hashes. Your console is scoped to your keys, usage, and conversations; the operator manages the global pool separately.