unexpected status 404 Not Found: Unknown error - Codex
Quick fix
DeepSeek does not support the Responses API. Add /v1 to base_url and remove wire_api = "responses".
Symptom
Section titled “Symptom”unexpected status 404 Not Found: Unknown error, url: https://api.deepseek.com/responsesWhen using DeepSeek models in Codex, setting `wire_api` to `responses` causes requests to the `/responses` endpoint. Since DeepSeek does not support the Responses API, it returns a 404 Not Found error.
Open the Codex config file (usually at `~/.codex/config.toml`).
In `[model_providers.custom]`, update `base_url` to include `/v1` and remove `wire_api = "responses"`.
If errors persist, delete the current DeepSeek preset in cc-switch and re-add it, ensuring standard OpenAI-compatible interface usage instead of Responses API.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 2 real issues
- Does DeepSeek support the Responses API?
- No. DeepSeek only provides standard OpenAI-compatible interfaces; there is no responses endpoint.
- Why does deleting config.toml and reconfiguring still result in a 404 error?
- The regenerated config may still default to `wire_api = "responses"`. Manually modify `base_url` and remove that field, or delete the incorrect preset in cc-switch and reconfigure.
Related problems
Section titled “Related problems”This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.