Run the EveryAPI gateway inside Immersive Translate
Immersive Translate supports bilingual side-by-side web translation with AI models. Configure its OpenAI-compatible service to use EveryAPI, then choose and test a model from your account's live catalog; quality, latency, and cost vary by model and language pair.
One base URL line points Immersive Translate at EveryAPI
Default global Base URL / China-first Base URL: https://api.everyapi.ai/v1 / https://api-cn.everyapi.ai/v1
# Extension icon → More → Settings → Translation Services# Select OpenAI or Custom OpenAI Compatible API Key sk-everyapi-...Custom API endpoint URL https://api.everyapi.ai/v1/chat/completionsModel MiniMax-M3 # Test the selected model with your own language pair and content.From zero to your first call
- Install the Immersive Translate extension
Available on the Chrome Web Store / Edge Add-ons / Firefox AMO / Safari — search "Immersive Translate".
immersivetranslate.com/download
- Go to Settings → Translation Services
Extension icon → More → Settings; select "Translation Services" on the left.
- Choose OpenAI or Custom
We recommend the "OpenAI" section (built into Immersive Translate): set API Key to your EveryAPI key and Custom API endpoint URL to https://api.everyapi.ai/v1/chat/completions.
- Choose a model
Choose a model from the live catalog and test it with your language pair and content. Quality, latency, and cost differ by model; the EveryAPI dashboard is the source of truth for the rates available to your account.
Immersive Translate × EveryAPI
Why does the URL need /chat/completions at the end?
Immersive Translate's "Custom API endpoint URL" field wants the full endpoint URL (not the base URL), so the path segment must include /chat/completions. The OpenAI section may want only the base URL — it depends on the field label you see.