# AI models as ordinary working infrastructure

Source: https://cicora.ai/en/about

## What we build

cicora.ai brings chat, OpenAI- and Anthropic-compatible APIs, image and video generation, and team workspaces into one product.

## Product evidence

| Use case | What is included | Result |
| --- | --- | --- |
| Chat | Text, code, documents, search, and images in one workspace. | Work in the browser |
| API | Compatible endpoints for applications, agents, and IDEs. | One integration |
| Teams | Members, keys, spend, and organization balance. | Shared workspace |
| Media | Image and video models in the cabinet and compatible API methods. | Generate and edit |

## Operating principles

- **Compatibility over another protocol.** Change the base URL, set the key, and select a model.
- **Costs should be understandable.** Requests expose usage, rates, and USD charges.
- **Availability belongs in the service.** The platform handles compatible routing without moving that work to the client.
- **One balance across workflows.** Chat, API, image, and video usage draw from the active workspace balance.

## Direct contact

Email [info@cicora.ai](mailto:info@cicora.ai).

## Related pages

- [/en/docs](/en/docs.md)
- [/en/products/api](/en/products/api.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.