Configure Immersive Translate's custom Chat Completions API
Immersive Translate provides inline bilingual translation for web pages, PDFs, ebooks, and subtitles. Connect its custom OpenAI-compatible API to Router One and choose a model supporting Chat Completions. Compare the model's current rates and verify a short translation before processing a full document; gateway traces show the token usage and cost of each request.
Configure Immersive Translate to use the Router One base URL
In Immersive Translate, open Settings → Translation Services → OpenAI, switch the key type to Custom API Key, then expand the advanced options and fill in the custom endpoint — note it takes the full /chat/completions path, not just the base URL — plus a model ID from the /models page:
# Immersive Translate → Settings → Translation Services → OpenAI # 沉浸式翻译 → 设置 → 翻译服务 → OpenAI API Key type（API Key 类型）: Custom API Key（自定义 API Key） APIKEY: sk-your-router-one-key Custom endpoint（自定义 API 接口地址，须含 /chat/completions）: https://api.router.one/v1/chat/completions Custom model（自定义模型）: <model-id-from-/models>
Which model ID should Immersive Translate send?
Copy the exact model ID from /models, preserving case, hyphens, and version suffixes; do not substitute a display name. Open its detail page and match the supported API endpoints, context window, and capabilities such as tool calling to the provider and features selected in Immersive Translate. A catalog listing does not mean the client can use every feature of that model. Give each tool a dedicated API key with a maxSpend cap.
Which API protocol is Immersive Translate using?
OpenAI-compatible describes an interface format; it does not make Chat Completions (/v1/chat/completions), Responses (/v1/responses), and Anthropic Messages (/v1/messages) interchangeable. Check the installed client version, provider configuration, and actual request path against the model detail page and API compatibility fact sheet. A successful plain-text chat does not establish support for hosted tools, conversation state, or file-editing features.
Verify the Immersive Translate call in your request trace
Send a simple text request from Immersive Translate, then match its trace in Dashboard → Logs by time, model, and request_id: tokens, cost, latency, and status. Next, test streaming, tool calls, and multi-turn history separately. For failures, retain the actual request path, full error message, and request_id. If there is no matching log, check client configuration and connectivity before attributing the error to the gateway or upstream.
FAQ
Why does Immersive Translate reject my base URL?
The custom endpoint field expects the full path including /chat/completions — https://api.router.one/v1/chat/completions — not the bare /v1 base URL most SDKs take. If translations fail immediately, check that suffix first, then verify the model ID matches /models exactly.
Which models can Immersive Translate use through the gateway?
Choose a current catalog model that supports both the endpoint and the features Immersive Translate uses. Check /models and the model detail page for the exact ID, current rates, and capabilities; a family name such as GPT or Claude is not a compatibility guarantee. Seeing a model in the picker confirms discovery, so verify an actual request too.
Models are listed, but requests fail with 400 or 404. What should I check?
Record the actual request path and error message, then check the exact model ID. A 400 can indicate invalid parameters, unsupported tools, or a model/endpoint mismatch; a 404 can indicate an incorrect path or missing resource, so it does not by itself establish that a model was retired. If the error says must be called via, use the named endpoint or select a model supported on the current endpoint. Do not add or remove /v1 or /chat/completions across all clients indiscriminately.
Does this work from Mainland China?
Yes. The gateway is reachable from Mainland China without a VPN, and the configuration is identical to the global setup.
How do I debug a 401/402/403/429?
Match the request and error message in Dashboard → Logs. For 401, check whether the key was sent and is valid; for 402, check wallet balance and maxSpend; for 403, check key permissions and access restrictions. For 429, distinguish request/token limits from upstream throttling using the error details. Keep the request_id and follow the error-codes reference.