Authentication - Conare

All partner API requests use a Bearer token:

Authorization: Bearer cint_...

Integration keys (`cint_...`)

Created per Integration in the 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
`https://embeddings.conare.ai`	Embeddings API for platform keys

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.

One platform key for ConareDB and embeddings

Use one server-side sk-conare-... platform key for both ConareDB and https://embeddings.conare.ai/api/v1/embeddings. Send it as Authorization: Bearer sk-conare-.... Existing cdb_... database credentials remain accepted during migration. Use scoped cint_... Integration keys for per-end-user memory APIs.