---
title: "ai.memory.write · OpenVibe.Services"
canonical: "https://openvibe.services/docs/capabilities/ai.memory.write"
updated: null
---

# ai.memory.write · OpenVibe.Services

HTML: [ai.memory.write · OpenVibe.Services](https://openvibe.services/docs/capabilities/ai.memory.write)

# `ai.memory.write`

Generated at 2026-11-13 06:25:48 UTC from [`openvibe-contracts v0.419.0`](https://github.com/OpenVibers/OpenVibe.Contracts/tree/v0.419.0) and [`openvibe-sdk v0.161.0`](https://github.com/OpenVibers/OpenVibe.SDK/tree/v0.161.0).

Not grantable to apps (active, first-party).

Store and change a person's memory in OpenVibe.AI (Memory M2): POST /api/v1/memory/items:batch imports up to 200 items, PATCH /items/{id} changes text, kind, scope or status, DELETE /items/{id} and DELETE /items?source= remove rows. The person's own token or a service acting on\_behalf\_of them. Redaction runs again on the server (openvibe-sdk/redact), an item that is only a secret is refused, AI-produced items are suggestions until the person accepts them, and a delete removes the row (profiles that used it are rebuilt).

- Owner: ai (token audience `openvibe.ai`)
- Version: 1.0
- Status: active
- Visibility: first-party
- Resource constraints: owner
- Quota class: ai-memory
- Permissions: ai:memory:write
- Input: [ai.memory-write-request@1](/docs/contracts/ai.memory-write-request)
- Output: ai.memory-result@1
- Events: —
- Implemented by: - `POST /api/v1/memory/items:batch`
- `PATCH /api/v1/memory/items/:id`
- `DELETE /api/v1/memory/items/:id`
- `DELETE /api/v1/memory/items`

[These routes in the API explorer](/docs/api/ai#cap-ai.memory.write)