Documentation
Community and ecosystem integrations in the NexoRouter documentation.
Community and ecosystem integrations
Status: Not verified yet.
Use this page for community plugins, workflow builders, browser extensions, and one-off tools that are not listed as dedicated NexoRouter guides.
Compatibility rule
A community tool can be a NexoRouter candidate only when it supports all of these:
| Requirement | Why it matters |
|---|---|
| OpenAI-compatible Chat Completions | NexoRouter's stable public API is POST /v1/chat/completions. |
| Custom base URL | The tool must send requests to https://api.nexorouter.com/v1. |
| Custom API key | The tool must accept a NexoRouter key. |
| Manual model ID or model list refresh | The tool must use model IDs from Models or GET /v1/models. |
| Server-side secret handling | Browser-visible or shared configs can leak keys. |
Do not use NexoRouter when
- The tool only supports native Claude, native Gemini, image, video, audio, or Responses API paths.
- The tool has no base URL field.
- The tool stores API keys in public client-side config.
- The tool silently routes through its own provider instead of the configured endpoint.
First verification
- Create a low-budget key.
- Configure one model only.
- Send one short non-streaming text request.
- Confirm the request appears in Usage Logs.
- Add larger workflows only after the first request is proven.