Documentation
Translation tools in the NexoRouter documentation.
Translation tools
Status: Candidate setup pattern, not yet verified by NexoRouter for specific translation clients.
Many translation apps and browser extensions can use NexoRouter only if they expose an OpenAI-compatible custom provider with a base URL field.
Use this pattern when the tool has
| Required field | NexoRouter value |
|---|---|
| Provider type | OpenAI-compatible or Custom OpenAI |
| Base URL / API URL | https://api.nexorouter.com/v1 |
| API key | YOUR_NEXOROUTER_API_KEY |
| Model | A model ID copied from Models |
If the tool only supports a native Gemini, native Claude, or official-provider-only field, do not put the NexoRouter base URL there.
First test
Use a short text translation:
Translate this sentence to Spanish: NexoRouter is connected.Then open Usage Logs and confirm the request appears with the expected key and model.
Known limits
- Browser extensions may expose keys client-side; avoid production keys.
- Long webpages can generate many requests and consume quota quickly.
- Streaming, file translation, OCR, image translation, and glossary features need separate verification.
- Use a low-budget key for translation clients.