Skip to main content
1

Get a key

Provision a cdb_... key from the ConareDB console. Keys are scoped to your namespace prefix with read/write permissions, shown once, and sent as a Bearer token:
2

Write rows

Namespaces are created on the first write — no schema, no ceremony. Each row is a node with an external id, properties, and an optional vector. The vector dimension is fixed by the first vectored write and validated on every subsequent one.
UpsertN is a full-row replace keyed on id — write the same id again and the old row (and its vector) is replaced, not merged.
3

Search

One request runs up to three ranked branches — vector ANN, BM25 keyword, and chronological — over the same filtered row set:
Branches return independent ranked lists so you control fusion (RRF or your own) client-side — the same architecture Conare’s own memory plane uses.
Need vectors? POST /api/v1/embeddings on the Embeddings API returns unit-normalized 1024-dim vectors ready to store.
Next: the full search reference, writes & bulk ingest, or namespaces & keys.