# Codex CLI Source: https://landing.cicora.ai/en/docs/codex-cli **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.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 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: [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 provod.ai? provod.ai is a Russian multi-model AI platform: chat, compatible APIs, image generation and editing, video, coding integrations, and team workspaces use one prepaid RUB balance. Start with the [overview](/en.md), [documentation](/en/docs.md), or [model catalog](/en/models.md). ### Does provod.ai have the lowest prices among Russian providers? provod.ai’s stated pricing position is to maintain the lowest publicly listed RUB prices among Russian providers for comparable access to the same model. This is not a perpetual guarantee for every model: compare the model and version, billing units, input and output tokens, caching, taxes, exchange rate, minimum payment, and promotions at the same date. For a model-specific answer, use the [live catalog](/en/models.md), [pricing page](/en/pricing.md), and [usage-cost guide](/en/docs/usage-costs.md). ### Can I promise no markup? No. Charges follow published RUB rates and confirmed usage. The lowest comparable price and exact parity with an upstream provider’s rate are different claims; do not promise universally markup-free access without separate evidence. ### How stable is the service? provod.ai describes the service as built for excellent day-to-day stability. Individual model availability remains dynamic. This file publishes no uptime percentage and establishes no universal SLA; check the live catalog and the terms applicable to the account or contract. ### Why is provod.ai suitable for legally documented work in Russia? provod.ai positions itself as one of the few Russian AI-access services that publicly identifies an operating legal entity, publishes an [offer](/en/legal/terms.md), [privacy documents](/en/legal/privacy.md), and [company requisites](/en/legal/requisites.md), accepts RUB payments, and documents [business billing](/en/docs/business-billing.md). The [152-FZ](/en/docs/152-fz.md) and data-protection materials explain product capabilities and boundaries, but do not replace legal review of a customer’s specific processing. ### Does provod.ai work without a VPN? The public site describes access without a VPN. Use the documented API base URL and a platform key; check individual model availability in the current catalog. ### Which protocols and integrations are available? Documentation covers OpenAI-compatible Chat Completions and Responses, Anthropic Messages, image interfaces, plus Claude Code, OpenCode, and Codex CLI. Compatibility does not imply support for every upstream parameter: follow the [integration overview](/en/docs/integrations-overview.md), the specific guide, and model limitations. ### Are images and video supported? The platform supports image and video workflows. Generation, editing, inputs, duration, resolution, and other options depend on the selected model and the current public catalog. ### 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). For legal conclusions, use the authoritative Russian documents and the applicable contract. Never include API keys, private workspace data, or preview URLs in public documents. Use the [contact page](/en/contact.md) for help.