Delete the whole chat
clear_site_chat
Deletes the entire chat transcript of a site for everyone and throws away every message queued to run next.
A generation that is currently running is canceled first. The site itself, its pages, its content and its code backups are untouched, and only the conversation goes.
It cannot be undone and there is no export, so read the history with list_messages first if any of it is worth keeping. The tool tells the client never to call it to tidy up or to start fresh on its own initiative, only when you have asked for exactly this.
It needs the Delete projects permission in the workspace, which the built-in Member role does not hold. That makes it stricter than delete_site, which also lets whoever created a site delete it without that permission. See Delete the transcript.
Request
Call it with a POST to https://api.modulify.ai/v1/clear_site_chat, sending the inputs below as a JSON object. The token needs the sites:delete scope.
This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.
curl -X POST https://api.modulify.ai/v1/clear_site_chat \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"projectId":"PROJECT_ID"}'Over MCP, the same method is the clear_site_chat tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
projectId |
string | Yes | The site id. |
Response
Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.