Fetch one memory by id (the original text you stored)

POST/api/v1/memory/get

In the SDKs: get

Returns a single stored memory by the id that /store or /list returned: the original text plus its metadata, and nothing internal. Tablet 2, the default model, answers with the memory itself; older models wrap it as {user_id, memory: {...}}. The SDKs return the memory either way. An unknown id, or one from another store, is a 404.

Authentication

Every call carries your API key in an X-API-Key header. Keys are created in the console.

X-WOS-Modeloptional

Picks the memory model that answers. Omit it and Tablet 2 answers.

Request body

JSON, required. Out-of-range values are refused with a 400 rather than quietly clamped.

user_id string required

The store to operate on. Stores are explicit: create one first or use the built-in "default". Use the id the store was created with: 1-64 ASCII letters, digits, ., _ or -, starting with a letter or digit. Ids that differ only by case name one store.

memory_id string required

The memory id from /store or /list.

Returns

The 200 body. Fields nested one level are shown as parent.child.

id string

content string

category string

created_at string

event_date string

is_superseded boolean

superseded_by string

Example

curl -X POST https://api.wontopos.com/api/v1/memory/get \
  -H "X-API-Key: $WOS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Status codes

Rate limits per tier and the full status list are in Errors & limits.

In the SDKs

The Python, TypeScript, and Rust SDKs wrap this endpoint so you do not build the request by hand — pip install wontopos, npm i wontopos, or cargo add wontopos, then the method list is on the SDK reference. A coding agent can take the whole API in one file at llms.txt, or over MCP with npx -y wontopos-mcp.

Related

• Search
• Recall
• List memories
• History
• Stats