The picture we hold for an image memory
POST/api/v1/memory/image
In the SDKs: get_image
The only call on this plane that answers with something other than JSON: the stored image itself, with its own Content-Type. Not necessarily your upload — anything over 1568px on its long edge was stored downscaled, and re-encoded to WebP unless it was a JPEG, so a PNG comes back as image/webp. When the format changed, x-wos-image-converted-from names what you sent; take the file extension from Content-Type rather than from your upload. A memory that exists but carries no image is a 404, same as an unknown id.
Authentication
Every call carries your API key in an X-API-Key header. Keys are created in the console.
X-WOS-ModeloptionalPicks 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_idstring requiredThe store to operate on. Stores are explicit: create one first or use the built-in "default".
memory_idstring requiredThe memory whose image you want.
Example
curl -X POST https://api.wontopos.com/api/v1/memory/image \
-H "X-API-Key: $WOS_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'Status codes
| Status | Meaning |
|---|---|
| 200 | The image bytes as we hold them — downscaled to 1568px on the long edge, and re-encoded to WebP unless it was a JPEG. Content-Type is sniffed from the bytes; x-wos-image-converted-from appears when the format changed. |
| 401 | Missing or invalid API key. |
| 404 | No such memory, or the memory exists and carries no image. |
| 429 | Rate limited (per-account, per-tier RPM). Retry after the indicated delay. |
| 501 | The selected model’s engine does not implement this endpoint (Tablet 2 and newer do). The message names the model. |
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.