Skip to main content
All partner API requests use a Bearer token:

​
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

​
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, with separate limits and billing. A memory key never grants database access, and vice versa. See ConareDB.