get_memories
Retrieve all memories stored in the workspace. Supports pagination to handle large numbers of memories.Use Cases
- Load workspace context at the start of a conversation
- Review all stored memories
- Implement memory browsing interfaces
- Audit stored information
Parameters
Response
Array of memory objects, each containing:
memory_id: UUID of the memorycontent: The memory contentcreated_at: Timestamp when memory was createdupdated_at: Timestamp when memory was last updatedagent_id: Optional agent identifieragent_name: Optional agent nameapi_key_id: ID of the API key that created the memory
Example Request
Example Response
Pagination
To retrieve all memories, use pagination:Behavior
- Returns memories in reverse chronological order (newest first)
- Only returns memories for the project associated with the API key
- Empty result sets return an empty array, not an error
Error Handling
Best Practices
- Use reasonable limits: Start with 50-100 memories per request
- Implement pagination: For workspaces with many memories
- Cache results: Consider caching memories that don’t change frequently
- Filter client-side: If you need to filter by agent or date, do it after retrieval
