docs(cookbooks): repair dead references and label OSS vs Platform support (#6909)

2026-08-14 16:50:46 +05:30
parent c50a2bfb8f
commit a0329f047b
31 changed files with 148 additions and 38 deletions
@@ -3,6 +3,9 @@ title: Build a Companion with Mem0
 description: "Spin up a fitness coach that remembers goals, adapts tone, and keeps sessions personal."
 ---

+<Info icon="layer-group">
+**Works with:** Mem0 OSS (`Memory`) and Mem0 Platform (`MemoryClient`)
+</Info>

 Essentially, creating a companion out of LLMs is as simple as a loop. But these loops work great for one type of character without personalization and fall short as soon as you restart the chat.

@@ -3,6 +3,9 @@ title: Control Memory Ingestion
 description: "Filter speculation, enforce formats, and gate low-confidence data before it persists."
 ---

+<Info icon="cloud">
+**Works with:** Mem0 Platform (`MemoryClient`)
+</Info>

 AI assistants plugged with memory systems face a problem - they often store everything. Not every conversation needs to be remembered, and not every detail should go to the memory store. Without proper controls, memory systems accumulate unreliable data.

@@ -3,6 +3,10 @@ title: Partition Memories by Entity
 description: Keep memories separate by tagging each write and query with user, agent, app, and session identifiers.
 ---

+<Info icon="cloud">
+**Works with:** Mem0 Platform (`MemoryClient`)
+</Info>
+
 Nora runs a travel service. When she stored all memories in one bucket, a recruiter's nut allergy accidentally appeared in a traveler's dinner reservation. Let's fix this by properly separating memories for different users, agents, and applications.

 <Info icon="clock">
@@ -3,6 +3,9 @@ title: Export Stored Memories
 description: "Retrieve, review, and migrate user memories with structured exports."
 ---

+<Info icon="cloud">
+**Works with:** Mem0 Platform (`MemoryClient`)
+</Info>

 Mem0 is a dynamic memory store that gives you full control over your data. Along with storing memories, it gives you the ability to retrieve, export, and migrate your data whenever you need.

@@ -169,20 +172,20 @@ export_job = client.create_memory_export(
 )

 print(f"Export ID: {export_job['id']}")
-print(f"Status: {export_job['status']}")
+print(f"Message: {export_job['message']}")

 ```

 **Output:**

 ```
-Export ID: exp_abc123
-Status: processing
+Export ID: 550e8400-e29b-41d4-a716-446655440000
+Message: Memory export request received. The export will be ready in a few seconds.

 ```

 <Info>
-**Export initiated:** Status is "processing". Large exports may take a few seconds. Poll with `get_memory_export()` until status changes to "completed" before downloading data.
+**Export initiated:** The export runs asynchronously and is usually ready within a few seconds. Retry `get_memory_export()` with the returned ID until it stops returning a "no export found" error.
 </Info>

 ### Step 3: Download the export
@@ -193,7 +196,7 @@ export_data = client.get_memory_export(
    memory_export_id=export_job['id']
 )

-print(export_data['data'])
+print(export_data)

 ```

@@ -216,7 +219,7 @@ export_by_filters = client.get_memory_export(
    filters={"user_id": "dev"}
 )

-print(export_by_filters['data'])
+print(export_by_filters)

 ```

@@ -240,7 +243,7 @@ export_with_instructions = client.create_memory_export(
 ```

 <Tip>
-Always check export status before downloading. Call `get_memory_export()` in a loop with a short delay until `status == "completed"`. Attempting to download while still processing returns incomplete data.
+If the export is still processing, `get_memory_export()` returns a 404 with `{"error": "No memory export request found"}`. Retry after a short delay until the call succeeds instead of polling a status field.
 </Tip>

 ---
@@ -3,6 +3,9 @@ title: Tag and Organize Memories
 description: "Let Mem0 auto-categorize support data so teams retrieve the right facts fast."
 ---

+<Info icon="cloud">
+**Works with:** Mem0 Platform (`MemoryClient`)
+</Info>

 When you have large volumes of memory data, sorting it during post-processing becomes difficult. What if your memory store understood the importance of creating tags and buckets without a lot of effort?