Where did you hear about us?
1 of 6
Working memory

A new query inside the same work

POST/api/v1/memory/work/search

In the SDKs: work_search

One work step: another query, its memories numbered on from the ones already given.

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.

work_id string required

The work open_work returned.

query string required

The new query.

rooms any

Which rooms to look in: "all", one name, or a list of up to nine; false looks in no room. A room is one part of a day in the last three days: m0 is this morning, a0 this afternoon, n0 tonight.

room string

One room. It cannot go with a call that looks in no room.

tz_offset_minutes integer

UTC offset in minutes for this call; the store's time zone when absent.

Example

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

Status codes

StatusMeaning
200Success.
400A field is missing or out of range; the message names it.
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.
501Only Scroll 2 serves this endpoint. Send X-WOS-Model: scroll-2; the message names the model sent.

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.