Unregister a person

DELETE/api/v1/memory/speakers

In the SDKs: remove_speaker

Their memories stay, and the name can no longer tag a new memory or filter a search. On tablet-2 the tag stays on memories already stored with it.

Authentication

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

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.

speaker string required

Returns

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

user_id string

speaker string

status "removed"

Example

curl -X DELETE https://api.wontopos.com/api/v1/memory/speakers \
  -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

• Register a speaker
• List speakers
• By speaker