Skip to main content
Cogito authenticates with bearer tokens — the same shape OpenAI uses, so any OpenAI-compatible SDK works without modification.

Creating keys

  1. Sign in at cogito.decart.ai.
  2. Open Dashboard → API keys.
  3. Click Create, name the key (we recommend naming it after the environment — production-api, local-dev), and copy the secret immediately. The full secret is shown once.

Best practices

  • One key per environment. Local dev, staging, and production should each have their own key.
  • Rotate on schedule. We surface last_used_at on every key — keys that haven’t been used in 30 days are good rotation candidates.
  • Revoke instantly. Compromised keys can be revoked from the dashboard; revocation propagates within seconds.
  • Don’t commit keys. Use environment variables (COGITO_API_KEY) or your platform’s secret manager.

Scopes

Model access is scoped with projects. A project belongs to your organization, selects which models it allows, and owns its own API keys:
  1. Open Dashboard → Projects and create a project (org owners and admins only).
  2. Pick All models or Selected models only on the project page.
  3. Create keys inside the project. Those keys can call only the project’s models — everything else returns the same 404 model_not_found as a model that doesn’t exist, on /v1/chat/completions, /v1/completions, /v1/models, and /v1/metrics alike.
Keys created from Dashboard → API keys (outside any project) keep full access to every model your organization can use. Deleting a project permanently revokes its keys. Other per-key scoping (read-only, monthly budget) ships in a later release.

Errors

A request without a valid key returns:
Always log the request_id — we trace it through every layer of the gateway and inference cluster, so support can find your request immediately.