Memory API
Ingest, retrieve and reason over your organisation's knowledge.
The Memory API is where knowledge goes in and answers come out.
Account-level operations — workspaces, credentials, billing — live in the Platform API.
curl https://api.uni-flow.ai/api/v1/memory/search \
-H "x-api-key: $CHORDIAN_API_KEY" \
-H "content-type: application/json" \
-d '{"query": "What is blocking the Acme deal?"}'Choosing an endpoint
| You want to | Call |
|---|---|
| Ask a question, get a cited answer | POST/api/v1/memory/search |
| Stream that answer | POST/api/v1/memory/search/stream |
| Add text, markdown, HTML or JSON | POST/api/v1/memory/ingest |
| Add a file | POST/api/v1/memory/uploads |
| Traverse relationships | GET/api/v1/memory/graph/explore/{id} |
| Correct a wrong answer | POST/api/v1/memory/learn |
Start here
1
Getting started
Ingest something and search it.
2
Memory model
Scoping, hostnames and credentials.
3
Ingestion guide
Routing, files, deduplication and the perimeter.
4
Retrieval guide
Filters, streaming and citations.
Reference
Search
Query, stream and list indexed sources.
Ingestion
Content, files and re-indexing.
Knowledge graph
Entities, timelines and traversal.
Knowledge quality
Contradictions, health and syntheses.
Spaces
Scoped retrieval and conversation capture.
Learning
Corrections, deprecations and lessons.
Two hosts
| Host | Credential | Reaches |
|---|---|---|
api.uni-flow.ai | ck_live_… | Every memory in the tenant |
{slug}-{serial}.api.uni-flow.ai | mk_… | Exactly one memory |
Prefer the per-memory host and key for agents and third-party integrations — a leaked credential then exposes one memory rather than everything.
Machine-readable
curl https://docs.uni-flow.ai/openapi/memory.yamlWas this page helpful?Report an issue