provod.ai / docs
Integrations

Codex CLI

Current boundary between the published provod.ai Responses API and Codex CLI.

Last updated on

Endpoint published; Codex workflow not yet verified

POST /v1/responses is available on provod.ai. We have not yet published a verified end-to-end Codex CLI setup, so do not treat a copied configuration as supported until it is tested with your Codex version and workflow.

What changed

Codex CLI custom providers use the Responses wire protocol. The required endpoint is now available at https://api.provod.ai/v1/responses, with streaming, portable function calls, previous_response_id, and Conversations. The API uses the same platform key and current text-model IDs from GET /v1/models.

The endpoint alone does not prove that every Codex workflow works. Coding-agent clients can request hosted tools, background execution, or provider-private response state. Those are deliberately outside the portable provod.ai contract.

Keep the request inside the portable boundary

The published Responses API supports text and image input, client-executed function tools and their outputs, streaming, response chaining, and Conversations. It rejects hosted web_search, file_search, code_interpreter, computer use, hosted MCP, background jobs, and encrypted provider-native reasoning state.

Before using a custom Codex provider with a production key, run a small read-only task and inspect the final request. If it receives an unsupported_parameter or unsupported_tool error, do not repeatedly retry it or weaken key protection; the client workflow needs a supported alternative or a compatible configuration.

Use a verified alternative for production work

For a documented coding-agent integration today, use one of these endpoints:

Never put a platform key in a repository or browser configuration. Store it in the operating-system keychain, protected local configuration, or an environment variable, and revoke it from the cabinet if it was exposed.

Troubleshooting

On this page