Aliases
Some clients do not prepend /v1. The backend registers compatibility aliases for those clients.
Registered Aliases
| Method | Alias path | Standard path |
|---|---|---|
POST | /responses, /responses/* | /v1/responses, /v1/responses/* |
GET | /responses | OpenAI Responses WebSocket compatibility entry |
POST | /chat/completions | /v1/chat/completions |
POST | /images/generations, /images/edits | /v1/images/generations, /v1/images/edits |
POST | /images/tasks | /v1/images/tasks |
GET | /images/tasks/{task_id} | /v1/images/tasks/{task_id} |
GET | /images/tasks/events | /v1/images/tasks/events |
POST | /images/tasks/{task_id}/cancel | /v1/images/tasks/{task_id}/cancel |
Codex-Compatible Entry
| Method | Path | Notes |
|---|---|---|
POST | /backend-api/codex/responses | Codex-compatible Responses entry. |
POST | /backend-api/codex/responses/* | Codex-compatible Responses subpaths. |
GET | /backend-api/codex/responses | Codex-compatible WebSocket entry. |
Unregistered Aliases
The current backend does not register these paths without /v1:
text
/models
/usageUse /v1/models and /v1/usage for model and usage queries.