# An AI request path developers can inspect

Source: https://cicora.ai/en/solutions/developers

Connect an application through compatible AI endpoints, explicit model IDs, and API-key controls.

Move an existing client from configuration to a streamed request with an explicit model identifier.

## From application input to a traceable response

An existing OpenAI-compatible client and a platform API key.

A response from the selected public model ID and a request record.

Capabilities and availability follow the current public catalog.

## Continue the developer path

### Configure

Set the compatible base URL.

### Request

Name the model explicitly.

### Inspect

Review request-level usage.

## Related pages

- [/en/products/api](/en/products/api.md)
- [/en/docs/chat-completions](/en/docs/chat-completions.md)
- [/en/models](/en/models.md)

## 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.