# Codex CLI

Source: https://cicora.ai/en/docs/codex-cli

**Endpoint published; Codex workflow not yet verified**


`POST /v1/responses` is available on cicora.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.cicora.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 cicora.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:


[OpenCode](/en/docs/opencode)


Use an OpenAI-compatible Chat Completions provider.


[Claude Code](/en/docs/claude-code)


Use the Anthropic Messages-compatible endpoint.


[Responses API](/en/docs/responses)


Build a portable Responses integration directly.



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


**Codex returns 404 for /v1/responses**


Confirm the custom provider base URL is exactly `https://api.cicora.ai/v1`
and that no stale proxy overrides it. The published endpoint is
`/v1/responses`; a duplicated `/v1` usually indicates a base-URL
configuration error.


**Codex receives an unsupported parameter or tool error**


The client asked for a capability outside the portable contract. Record the
public error code, parameter, Codex version, model ID, and time without
including the key. Use a supported coding tool or change the client
workflow; do not retry the same unsupported request.


**A model appears in /v1/models but the task still fails**


Model discovery, the Responses protocol, and agent capabilities are separate
checks. Choose an available text model, validate a minimal Responses request
first, then add the agent workflow one capability at a time.

## FAQ

### What is cicora.ai?

cicora.ai is a multi-model AI workspace and compatible API for chat, text, images, video, coding tools, and teams. Start with the [overview](/en.md), [documentation](/en/docs.md), or [model catalog](/en/models.md).

### How is usage billed?

Confirmed usage is charged in USD from the active workspace's prepaid balance. Use the live catalog for current model prices and the [usage guide](/en/docs/usage-costs.md) for settlement details.

### Which protocols and integrations are available?

Documentation covers OpenAI-compatible Chat Completions and Responses, Anthropic Messages, image interfaces, Claude Code, OpenCode, and Codex CLI. Compatibility does not imply support for every upstream parameter.

### Which sources are authoritative and current?

For model IDs, availability, capabilities, limits, and prices, use the [live catalog](/en/models.md). For API behavior, use the matching [documentation page](/en/docs.md). Never include API keys, private workspace data, or preview URLs in public documents.