Documentation
Responses API Boundary in the NexoRouter documentation.
Responses API Boundary
Status: Not part of the documented stable public API yet.
Some modern OpenAI tools can prefer /v1/responses. NexoRouter's documented public path today is /v1/chat/completions, so tools should be configured to use Chat Completions when possible.
Tool guidance
| Tool | Guidance |
|---|---|
| Continue | Set useResponsesApi: false for GPT-5 or o-series model IDs through NexoRouter. |
| Codex CLI | Do not configure with NexoRouter until a compatible Responses API path or verified Codex-specific setup exists. |
| OpenAI SDK | Use chat.completions.create for documented NexoRouter calls. |
Why this matters
If a tool silently switches to Responses API, the request may fail or behave differently from the documented NexoRouter API. This is one of the most common hidden configuration traps for GPT-5 and o-series models.