# Image work with a durable path from prompt to gallery

Source: https://cicora.ai/en/products/images

Create image jobs, use reference inputs where supported, and return to completed outputs in a private gallery.

Start a generation or reference-based edit, follow the job state, and keep completed outputs available in your private gallery.

## Make iterations traceable

- Queue a durable image generation job.

- Use uploaded reference inputs for editing where the selected option supports it.

- Return to completed outputs in the private gallery.

## A visible lifecycle for visual iterations

Choose an available option, add the prompt or reference input, wait for the job result, then revisit the saved output.

## For campaigns, concepts, and repeated visual work

Use Images when a visual task benefits from saved jobs and the ability to return to completed outputs.

## Options depend on the selected image model

Supported generation and editing inputs vary by the selected option. Check the current product interface and catalog before planning a workflow.

## Continue with the connected products

## Related pages

- [/en/pricing](/en/pricing.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.