From d7626a8231662cfa2336ee04bda8d11133f247b7 Mon Sep 17 00:00:00 2001 From: kartik-mem0 Date: Fri, 14 Aug 2026 17:35:26 +0530 Subject: [PATCH] docs: add the Platform-only batch, feedback, and summary rows These three capabilities exist on MemoryClient but have no OSS equivalent, and the comparison table did not mention them. Verified absent from Memory/AsyncMemory. Direct Import is deliberately not added: infer=False works on OSS too, so it is not a difference. --- docs/platform/platform-vs-oss.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/platform/platform-vs-oss.mdx b/docs/platform/platform-vs-oss.mdx index 067e66710..4ea74c19a 100644 --- a/docs/platform/platform-vs-oss.mdx +++ b/docs/platform/platform-vs-oss.mdx @@ -79,6 +79,9 @@ The core memory loop is identical on both: `add`, `search`, `get`, `get_all`, `u | **Custom categories** | Set per project or per `add` call ([details](/platform/features/custom-categories)) | Not supported. `Memory.add()` has no `custom_categories` parameter, and OSS project updates are rejected outright | | **Webhooks** | Project-scoped HTTP callbacks on memory and ingest events ([details](/platform/features/webhooks)) | Not available | | **Memory Export** | Schema-driven structured export jobs over filtered memories ([details](/platform/features/memory-export)) | Not available | + | **Batch operations** | `batch_update` and `batch_delete` apply up to 1000 memories per call | Not available. Loop over the single-memory `update`/`delete` calls | + | **Feedback** | `feedback(memory_id, ...)` records `POSITIVE`, `NEGATIVE`, or `VERY_NEGATIVE` signals against a retrieved memory ([details](/platform/features/feedback-mechanism)) | Not available | + | **Summaries** | `get_summary(filters)` returns a generated summary over the matching memories | Not available | | **Filterable fields** | Top-level filter keys come from a fixed allowlist: `user_id`, `agent_id`, `app_id`, `run_id`, `created_at`, `updated_at`, `timestamp`, `expiration_date`, `text`, `categories`, `metadata`, `keywords_search`, `memory_ids`, `keywords`, plus the `AND`/`OR`/`NOT` operators. Any other key is rejected with a `400` ([details](/platform/features/v2-memory-filters)) | Any metadata key is filterable directly, with no allowlist | | **Comparison operators** | Depends on the field: `metadata` accepts `eq`, `ne`, `contains`; `categories` accepts `contains`, `in`; the date fields accept the range operators | The full set on any key: `eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`, `contains`, `icontains` |