Reading memories

List a store’s memories (the original text you stored)

POST/api/v1/memory/list

In the SDKs: list_memories · iter_memories · export_memories

Paginates the raw memories in a store — the text you stored plus its metadata, and nothing internal. Use it to browse or export a store. Pass the returned next_cursor back as cursor for the next page; a null cursor means the last page.

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 the account default is used.

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".

limit integer 1–500 · default 100
cursor string

Opaque page cursor from a previous response’s next_cursor.

Returns

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

memories object[]
memories.id string
memories.content string
memories.category string
memories.created_at string
memories.event_date string
memories.is_superseded boolean
count integer
next_cursor string

Example

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

Status codes

StatusMeaning
200Success.
401Missing or invalid API key.
404Store (user_id) does not exist. Create it first: POST /api/v1/memory/collection.
429Rate limited (per-account, per-tier RPM). Retry after the indicated delay.

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.