cicora.ai
English
API specificationOrganizations

Teams and API keys

Separate keys, owners, budgets, and usage traces across applications and workspaces.

Integration reference: choose parameters and available capabilities from your account API settings and the model catalogue for your environment.

Ownership model

Issue a key for one integration and assign an owner, environment, and revocation contact. This turns a key incident into a targeted operation rather than a team-wide stop.

Verify a new key through the model catalogue before connecting it to a queue, webhook, or user interface.

Verify an issued key without inference
bash
curl --request GET https://cicora.ai/api/v1/models \
  --header "Authorization: Bearer $CICORA_API_KEY" \
  --header 'Accept: application/json'

Spend control

  • Use a key limit as a guardrail, not as a way to estimate cost.
  • Associate an internal project with a key and request id.
  • Remove unused keys regularly after owner confirmation.

Investigate variance

Compare usage by model, workflow, key, and time. Aggregate spend without context cannot quickly identify the cause.

Keep only necessary identifiers and provide spend access by role, not by the convenience of a link.

Continue with