# Security information

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

## Product boundaries

Use platform API keys only in trusted server-side environments. Create a separate key for each project and revoke a key when exposure is suspected.

Never place a platform key in frontend source, a public browser bundle, a repository, screenshots, or support messages. For security-related questions, 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.