Skip to main content
This page answers the most common questions about Inferoute. If you cannot find what you are looking for here, reach out via the dashboard chat or email support@inferoute.ai.
Yes. Inferoute exposes an OpenAI-compatible API, so you can use the official OpenAI SDK by pointing it at the Inferoute base URL and supplying your Inferoute API key:
python
node.js
No other code changes are required.
Inferoute currently routes requests across the following providers:
  • OpenAI — GPT-4o, GPT-4o mini, o1, o3, and more
  • Anthropic — Claude 3.5 Sonnet, Claude 3 Opus, Claude 3 Haiku, and more
  • Google — Gemini 1.5 Pro, Gemini 1.5 Flash, and more
  • Mistral — Mistral Large, Mistral Small, Codestral, and more
  • Meta / Llama — Llama 3.3, Llama 3.1, and more
Call GET /v1/models to retrieve the current list of available models.
No. Inferoute handles provider relationships on your behalf. You only need a Inferoute account and a Inferoute API key. You do not need to create accounts with OpenAI, Anthropic, Google, or any other provider, and you do not need to manage separate provider API keys.
Your bill is based on two components:
  1. Provider token costs — the cost of the tokens consumed at the provider level, passed through at the provider’s published rates.
  2. Inferoute routing fee — a small per-request fee that covers routing infrastructure, fallback logic, and platform features.
Both components are aggregated and billed monthly. You can view a breakdown by key, model, and provider in the Usage section of the dashboard.
Inferoute monitors provider availability continuously. If a provider becomes unavailable or returns errors above a threshold, Inferoute automatically routes your request to a backup provider that serves an equivalent model. This fallback happens transparently — your application receives a successful response without any code changes. You can configure fallback behavior and preferred backup providers in the Routing section of the dashboard.
Yes. Use provider-prefixed model names in your request to pin traffic to a specific provider. For example:
python
Supported prefixes include openai/, anthropic/, google/, mistral/, and meta/. When you use a prefixed model name, Inferoute does not attempt automatic fallback to another provider.
By default, Inferoute does not store the content of your requests or responses. Requests are routed to the selected provider and the response is forwarded back to you. Inferoute retains metadata (such as token counts, latency, and provider used) for billing and analytics purposes. If you need data residency guarantees or a custom retention policy, contact support@inferoute.ai to discuss Enterprise options.
The routing layer typically adds less than 10 milliseconds to end-to-end latency. The dominant factor in response time is the provider’s own inference time, not the Inferoute routing step. If you need to minimize latency further, enable the latency-optimized routing strategy in the dashboard, which selects the provider with the lowest observed response time for each request.
Yes. Set stream: true in your request exactly as you would with the OpenAI API. Inferoute transparently streams the provider’s response back to your client.
python
You can reach the Inferoute support team through two channels:
  • Dashboard chat — click the chat icon in the bottom-right corner of any dashboard page for real-time help.
  • Email — send a message to support@inferoute.ai. Include the X-Inferoute-Request-Id header value from any failing request to help the team diagnose the issue faster.