Intelligence,on your terms.

Route Key is an OpenAI-compatible AI API gateway and routing control plane. It exposes the models enabled in the current catalog, including GPT, Claude, Gemini, DeepSeek, Qwen, and compatible custom channels. Open the Models page to compare vendor, context length, endpoint support, group availability, and the exact model ID before sending production traffic.

Usually yes. Most integrations keep the familiar OpenAI request body and SDK code: replace the base URL with the Route Key compatible endpoint, set a Route Key API key, and choose a supported model ID. Test a short non-streaming request first, then add streaming, tools, or longer context after the response and usage log look correct.

The gateway evaluates available routes using configured group ratios, input and output token prices, cache settings, latency, and health. You can pin a model when consistency matters or let policy choose a healthy lower-cost route. Compare the selected model, tokens, group, and cost in Usage Logs so savings are measurable rather than assumed.

Yes. API keys are masked in the console, while Dashboard usage logs provide account visibility into request status, selected model, cost, input and output token counts, latency, and timestamps, subject to configured privacy controls. Use separate keys for applications or coding agents so access can be rotated and usage can be attributed cleanly.

Route selection happens before dispatch, so the gateway can avoid an unhealthy or unavailable channel before your request is sent. For streaming endpoints, Route Key retains SSE-style responses while selecting a healthy route. Check latency and error records after rollout, and configure a fallback policy for provider incidents instead of retrying blindly in every client.

Create a dedicated API key in the Dashboard, point your SDK to the Route Key compatible endpoint, select an exact model ID, and send a small test request. Confirm the response, quota, endpoint, token usage, latency, and cost in Usage Logs. Then add streaming, concurrency, retries, and fallback rules one at a time so a provider change is observable and reversible.