project_delete
Request deletion of a project. Two-step flow.
Step 1 — project_delete takes just the project_id. The platform returns a 6-digit confirmation code that expires after 10 minutes. No project state changes before the code is confirmed.
Step 2 — Human authorization is required before calling project_delete_confirm with the same project_id and code. Confirmation immediately takes the project and its hostnames offline, blocks new project effects, retains its database, files, functions, environment variables, and domain bindings for 30 days, and schedules permanent erasure after that retention period. Recovery during the retention period requires support.
Example:
{ "project_id": "my-saas" }The response is a SUCCESS carrying the code and a machine-readable status, e.g. { "ok": true, "status": "needs_confirmation", "confirmation_code": "482917", "code": "482917", "next_call": { "tool": "project_delete_confirm", ... } } — minting the code is this step's whole job, so it is never an error. The response carries confirmation_code (code is the same value, kept for existing callers). The response carries no error_code and no canonical_error, so branching on those stays a reliable failure test.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>"
},
"name": "project_delete"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Project ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them). |