persona.memory — /api/v1/developer/memory.
Memory exposes a subject’s persistent memory files over REST — the same /memories/user/ and
/memories/agent/ filesystem an Agent’s own write_file/read_file tool calls see. Every call
here requires the client to have been constructed with externalUserId set (a bare Project
credential has no Subject to scope memory to; the server rejects it with 400 EXTERNAL_USER_REQUIRED).
When to use it
- Admin/support tooling (“what does this Agent remember about founder X”).
- A user-facing “manage what you’ve shared” settings page.
- Seeding known facts before a user’s first conversation.
Memory written here goes through the exact same namespace a live Agent run uses — it’s real,
live-visible data, not a separate copy. A writeFile() call is indistinguishable from the
Agent having written that file itself via its own write_file tool.
Methods
list()
Returns MemoryListResult:
No pagination — memory has no pagination concept; it’s a full listing every time.
getFile(params)
Returns a MemoryFile: { scope, agentId?, path, content, mimeType, createdAt, updatedAt }.
Creates or overwrites one memory file — content replaces any existing content.
scope defaults to 'user'; 'agent' requires agentId. Returns the written MemoryFile.
deleteFile(params)
Same params shape as getFile. Returns void.
Complete example