Connect Mem0 with Fabriq Developer
Your user pastes their Mem0 credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Mem0 in practice
Mem0’s v3 Platform API removed the parameters most v2 integrations were built around — output_format, api_version, async_mode and enable_graph among them — and quietly changed defaults underneath: search now applies a 0.1 similarity threshold and rerank flipped from true to false. Writes are always async in v3, so a read issued straight after a write can legitimately return nothing.
Worth knowing
- Adds and searches moved to dedicated endpoints, POST /v3/memories/add/ and POST /v3/memories/search/, split out of the combined v1 and v2 endpoints.
- The list endpoint’s response changed from a bare results array to a paginated envelope with count, next, previous and results, so a client that indexed into the old shape breaks silently.
- async_mode is no longer configurable — v3 is always async — and enable_graph is automatic, so code that set either is now passing a rejected parameter.
- Authentication is Authorization: Token <your-api-key>, and organization and project scoping for multi-tenant isolation is a Platform-only feature, absent from the self-hosted build.
Checked against Platform v2 to v3 migration (2026-09-29), Mem0 API reference (2026-09-29), Mem0 platform quickstart (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Mem0 behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.