List registered people
GET/api/v1/memory/speakers
In the SDKs: list_speakers
Authentication
Every call carries your API key in an X-API-Key header. Keys are created in the console.
Request body
None. This call takes no JSON body.
Returns
The 200 body. Fields nested one level are shown as parent.child.
user_idstringspeakersobject[]speakers.speakerstringspeakers.memoriesintegerspeakers.created_atstringcountintegerlimitintegerRegistration cap for this store (50 to start).
Example
curl -X GET https://api.wontopos.com/api/v1/memory/speakers \ -H "X-API-Key: $WOS_API_KEY"
Status codes
| Status | Meaning |
|---|---|
| 200 | Success. |
| 401 | Missing or invalid API key. |
| 404 | Store (user_id) does not exist. Create it first: POST /api/v1/memory/collection. |
| 429 | Rate 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.