> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conare.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

> Authenticate partner API requests with cint_ Integration Bearer keys — scopes, one-time secrets, base URLs, and separation from ConareDB cdb_ keys.

All partner API requests use a Bearer token:

```bash theme={null}
Authorization: Bearer cint_...
```

## Integration keys (`cint_...`)

* Created per Integration in the [dashboard](https://conare.ai/dashboard), scoped to `memory:read`, `memory:write`, `memory:delete`.
* The secret is displayed **once**. Conare persists only a SHA-256 digest — a lost key is rotated, never recovered.
* Server-side only. Never embed in browser or mobile builds; requests carry your users' memory.

## Base URLs

| Host                    | Purpose                                             |
| ----------------------- | --------------------------------------------------- |
| `https://api.conare.ai` | Production — dedicated partner-API host (preferred) |
| `https://conare.ai`     | Alias — same API on the main host                   |

## Legacy personal keys (`cmem_...`)

Personal keys from the MCP/CLI product remain accepted during migration but are deprecated for partner integrations. Team-scoped `cmem_` keys are rejected on the partner path. New integrations should use `cint_` keys exclusively.

## ConareDB keys are separate

Database access uses its own `cdb_` keys, issued from the [ConareDB console](https://db.conare.ai), with separate limits and billing. A memory key never grants database access, and vice versa. See [ConareDB](/db/overview).