Coming from Mem0

Anyone coming from Mem0 knows add, search, get_all, update, delete, history, the filters, feedback, webhooks and the project’s instructions. Each has a name here, and almost every one does something similar by a different path: Niadra keeps a company’s memory of its customers, resolved across channels, extracted once per session and read under policy and verification level. This page gives the name and the route, and where the difference changes your code. What does not exist here is said, with the reason.

Writing

In Mem0	In Niadra	What changes
`add(messages, user_id=...)`, one call per exchange, with the model running on each	`customer()` and `agent()` on a `conversation()`, or `track()`; over HTTP, `POST /v1/batch`	Extraction runs once, when the session closes (by inactivity or `conversation.ended`), in one call. The write is acknowledged before extraction, and `POST /v1/ingest/status` says when the conversation became memory
`add(..., infer=False)` (store without extracting)	A system event (`system_event`) with `canonical_type`, an object and fields, with no AI model	Structured data changes an object’s state; a free-text fact with no evidence is not accepted
`timestamp`, `observation_datetime`	`occurred_at` on every event	Memory is ordered by `occurred_at`, and an episode is dated by the conversation’s last turn
Free `metadata` on a memory	`fields` on the system event; the business object with its state	There is no loose metadata on a memory item: an item is born from several events
`custom_instructions`, `includes`, `excludes`	The `extraction-guidance` configuration document: instructions, `include`, `exclude`, per space and per source	Changed by an approved diff, like the schema; enters the prompt after the rules it cannot change
Custom categories	The schema’s predicates, categories and episode categories, per space and per source
`immutable`	Does not exist	A data subject’s correction always wins: it is the right to rectification
`expiration_date`	`valid_until` on the event and on the agent’s note	After the date, the fact leaves the context and the search; `show_expired` still finds it
Direct import	`POST /v1/ingest/files`, a CSV for identity or a JSONL of batch items; `import.completed` and `import.failed` announce the end
Images and PDFs	PDF text and image OCR inside the cell, only for the types the space lists

Reading

In Mem0	In Niadra	What changes
`search(query, user_id=...)` before every answer, `top_k`, `threshold`	`context()`: the pack ready for the prompt, pinned per conversation; `search()` only when the context does not answer, with `max_tokens` and `limit`	The context is not a search: it is compiled when the memory changes and delivered in under 100 ms, without a model. No `threshold`: the cut is by token budget and by value
v2 filters (`AND`, `OR`, `NOT`, `eq`, `in`, `gte`, `contains`…)	`filters.where` on the search and the timeline, with the same grammar	Checked after the policy: it only narrows what the reader could already see, and never changes the ranking
`agent_id` as a filter	`source_id` and `vendor` in `where`	The source is the agent, with its own vendor and key
`rerank=True`	Does not exist	No model on the read path: latency and receipts stay predictable
`get_all(user_id=...)`	`timeline()`, one line per conversation or action; for governance, `GET /v1/profiles/{profile_id}/memory`
`get(memory_id)`	`open()`: the whole conversation or the object, with what was asked, promised and settled
`history(memory_id)`	`versions` on the opened item; `GET /v1/profiles/{profile_id}/facts/{fact_id}/history` for every value a fact held
Graph memory	Objects, links, accounts and partners: a typed graph, with no co-occurrence links
Temporal reasoning (`reference_date`)	`when` on the search, in Portuguese, English and Spanish, without a model; and the anchors on the system’s events	`timestamp`, `reference_date` and `decay` belong to Mem0’s paid platform; the open source SDK refuses them
Usage decay	Does not exist	Event recency and the context-use measurement decide what gets in

Correcting and erasing

In Mem0	In Niadra	What changes
`update(memory_id, data)`	`POST /v1/feedback` with `correct_fact`, by the agent; `POST /v1/corrections`, by the security role	It becomes an event, with lineage and a receipt
`batch_update`, `batch_delete`	`POST /v1/feedback/batch` (up to 500) and `POST /v1/corrections/batch` (up to 100)	One bad item never fails the rest
`delete(memory_id)`	`retract_fact` on the feedback	The fact leaves every pack
`delete_all(user_id=...)`, `delete_users()`	`POST /v1/forget`, by profile, handle or conversation, with a receipt and a deadline	Never within the model’s reach: erasure stays with people and admin keys
`feedback(memory_id, "POSITIVE" ...)`	The rating does not exist	Use is measured without anyone clicking: what the agent used, repeated or contradicted, in `GET /v1/context-use`
`reset()`	Deleting the space, in the control plane, with a receipt

Notifications and clients

In Mem0	In Niadra	What changes
Webhooks `memory_add`, `memory_update`, `memory_delete`	`fact.added` and `fact.retracted`, with `replaces`, `replaced_by` and `by`; never the value	Only the endpoint whose source may read the fact receives it. Signed in the Standard Webhooks format, retried for 24 hours
`ingest_job_completed`, `_failed`	`import.completed` and `import.failed`, only to the source that imported
Event list, `get_event_status`	Receipts, webhook deliveries and `POST /v1/ingest/status`
MCP `add_memory`, `search_memories`, `get_memories`, `update_memory`	The eight tools of the space’s MCP server, with the customer bound by the `subject_token`; `correct_customer_memory` corrects or retracts	No `delete_memory`, `list_entities` or `list_events`: an agent never lists customers or erases
`ping`, `users`	`GET /v1/sources/me` says what the key authenticates as; customers are never listed by an agent key
Admin client (`get_all`, `users`, `batch_update`, `export`)	`niadra.admin` in both SDKs, for keys with the `admin` scope
`user_id`, `agent_id`, `run_id`	The customer’s handle (phone, e-mail, `wa_id`, app id, system id), the source and the conversation or task	Identity is resolved across channels: the same customer on WhatsApp, on the phone and in the CRM is one profile

What stays out, and why

Model-written patterns (“Dream”), a model summary on the read path and model-filled schemas on export: every field would lose its evidence, and a model on the read path breaks latency and the receipt.
One model call per exchange: 37 times the model cost measured in the benchmark, with no accuracy gain.
An OpenAI-compatible proxy: the adapters plug into your framework without standing between you and the model call.

Agents

Integrations

Coming from Mem0

Writing

Reading

Correcting and erasing

Notifications and clients

What stays out, and why

Next steps

Quickstart

Integrations

​Writing

​Reading

​Correcting and erasing

​Notifications and clients

​What stays out, and why

​Next steps

Quickstart

Integrations

Writing

Reading

Correcting and erasing

Notifications and clients

What stays out, and why

Next steps