The Memory API gives your agent a long-term, semantically searchable store. Write any piece of text as a memory — it’s automatically embedded into a high-dimensional vector — then retrieve the most relevant memories later using natural-language queries. This means your agent can recall past conversations, decisions, and knowledge without needing to fit everything into a context window. Memories persist indefinitely until you delete them.Documentation Index
Fetch the complete documentation index at: https://docs.nonhumans.ai/llms.txt
Use this file to discover all available pages before exploring further.
POST /v1/memory
Store a new memory. The content is automatically embedded using Nonhumans’ managed embedding model — you don’t need to generate or store vectors yourself.The text content of the memory. This is what gets embedded and searched. Maximum 8,000 tokens.
Optional key-value pairs attached to the memory. Use metadata to tag, categorize, or filter memories without affecting the semantic content. Keys and values must be strings.
Unique identifier for the stored memory. Use this to delete or reference the memory directly.
Timestamp when the memory was stored and embedded.
POST /v1/memory/search
Search your agent’s memory store using a natural-language query. The API returns the most semantically similar memories ranked by cosine similarity score.Natural-language search query. Does not need to be an exact phrase — semantic similarity is used.
Maximum number of memories to return. Default
10, max 50.Key-value pairs used to pre-filter memories before the semantic search. Only memories whose metadata contains all specified key-value pairs are considered. This is a strict equality filter.
Ranked array of matching memory objects.
DELETE /v1/memory/
Permanently delete a specific memory by ID. This action is irreversible.The unique ID of the memory to delete.
204 No Content on success with no response body.
POST /v1/memory/files
Upload a file to your agent’s personal drive. Files are stored durably and can be retrieved via their URL. Large documents (PDFs, spreadsheets, text files) are also automatically chunked and indexed into vector memory for semantic search.The file to upload. Sent as
multipart/form-data. Maximum file size is 500 MB. Supported formats for automatic indexing: PDF, DOCX, TXT, MD, CSV, XLSX.Unique identifier for the uploaded file.
Original filename as uploaded.
File size in bytes.
Direct URL to download or share the file. URLs are authenticated — the file is only accessible with a valid agent session.
Whether the file’s contents have been extracted and indexed into the vector memory store. When
true, you can search the file’s contents using POST /v1/memory/search.GET /v1/memory/files
List all files stored in your agent’s drive. Results are returned in reverse chronological order and support cursor-based pagination.Number of files to return. Default
20, max 100.Pagination cursor from a previous response’s
next_cursor. Omit to start from the most recent file.Array of file objects stored in the agent’s drive.
Cursor to pass as the
cursor query parameter to retrieve the next page. null when you have reached the last page.Total number of files stored in the agent’s drive, regardless of pagination.