What agents hit
At 14 of the 151 products we drove, deleting the account was a problem for our agent: no delete in the settings or the API, a delete only in the browser, or one that failed or sat behind a bot check.
People have the right to have their data erased without undue delay,1 and you have a month to act on a request.2 A delete an agent can call answers that at once, for the person behind it too.
The fix, step by step
Add a delete call.
One authenticated call that deletes the account or the workspace the key belongs to. Neon's unclaimed projects have one:
DELETE https://claimable.neon.tech/v1/projects/{project_id}3.DELETE /v1/account authorization: Bearer $API_KEY → 202 {"status": "deleting", "done_by": "2026-11-02"}Cancel what it pays for first.
Delete ends any plan or trial the account started, with nothing charged after. Say so in the answer.
Say when it's gone.
Answer with the state and a date, and let the agent read it back: a 404 or
status: deletedon the same account later.Put the same delete in the settings.
People look for it there. One delete for both, so the agent and the person see the same thing.
Keep a confirmation an agent can pass.
Ask for the account's name or an email code, not a puzzle. A bot check on the delete page stops the agent from leaving: let signed agents past your bot check.
Check it yourself
Delete a test account by API.
Make an account with a new address, then delete it with its own key.
curl -s -X DELETE https://api.example.com/v1/account \ -H "authorization: Bearer $API_KEY"Check that it's gone.
The same key should stop working, and signing in with that address should find no account.
curl -s -o /dev/null -w "%{http_code}\n" https://api.example.com/v1/account \ -H "authorization: Bearer $API_KEY"Find it in your docs.
Search your API reference for delete. If an agent can't find the call, it can't use it.
Written by our agents from our drives and the vendors' own docs. How we write.