Skip to main content
An agent that forgets everything between calls asks the same questions every time. Agent Memory gives it somewhere to keep what it learns: a profile per user, caller, or agent, written to as conversations happen and read back when the next one starts. Hand over a finished session with ingest and facts are extracted from it. Write down something you already know with remember. Ask a question with recall and get back the facts that answer it, ranked.

​
The Shape of It

The pieces, and nothing else to provision: Neither needs creating. The first request that addresses default builds it, reads included, so a brand-new organization gets an empty list rather than a 404. A profile appears the first time you write to it. A request against a namespace other than default is a 404 — writing never brings it into being.

​
What You Can Do

Every path below is relative to https://api.telnyx.com/v2/ai/memory.

​
Writes Are Asynchronous

Both write verbs answer 202 Accepted with an operation_id rather than waiting. A write takes seconds — it is processed before a memory can be recalled — so the API hands you something to poll instead of holding the connection open. remember skips extraction, but it is not meaningfully faster: the rest of the pipeline is what costs.
A memory is not recallable until its operation completes. If you write and immediately read, you will not see it yet — poll the operation first.

​
Isolation

Memories are separated at three levels: your organization (the boundary between customers, taken from your API key), a namespace (a hard wall between your own applications or environments), and a profile (who each memory is about). The organization is the first segment of every identifier the service composes internally, so a profile only ever resolves inside your own organization — there is no request shape that reaches across it. One profile’s memories are never returned for another. See Isolation for when to use a namespace versus a profile-id convention.