Collect
Mail, chat, tickets, and records enter one plane.
01 / CONTEXT INFRASTRUCTURE
One API over 199 sources, product events, and tenant data.
What should the travel agent recommend?
Recommend smaller coastal cities in
late September . Stay on the
Team plan.
199 sources · one context plane
02 / THE CONTEXT LOOP
Mail, chat, tickets, and records enter one plane.
Identity, source, and version keep current truth.
Hybrid search. Ranked, bounded result.
Grounded context for this user and task.
03 / MEASURED
measured
25 wins, 5 ties, 0 losses · 30 real sessions · blind judge

04 / RETRIEVAL
05 / THE LIFECYCLE
import { Conare } from "@conare/sdk"
const conare = new Conare({ apiKey })
await conare.memories.upsertSource({
endUserId: "user_123",
source: "customer-profile",
externalId: "profile_123",
version: 7,
content: "Prefers smaller coastal cities."
})
const context = await conare.recall({
endUserId: "user_123",
query: "What should we recommend next?"
})Credentials determine the tenant. End-user and workspace fences narrow every read before retrieval.
Versioned writes correct and delete durable source records without stale retries restoring old state.
Choose raw hybrid search or citation-grounded recall. Scope the result to the source your model needs.
Remove one memory, one container, or an end user through explicit lifecycle endpoints.
06 / THE PLATFORM
managed memory
Save, search, recall, suggest.
retrieval database
Isolated retrieval. Tenant, user, source in scope.
model layer
Vectors in the same space the engine searches.
source layer
199 catalog sources. Consent and delete by tenant.