DELETE · projects:write

Delete project

Delete a project, its keywords, settings, and shared access. Retains stored mentions and their snapshots privately for support recovery; they disappear from the dashboard and API. Before calling, tell the user which project will be deleted and these consequences, ask for explicit confirmation, and wait for their answer. Only then supply confirmDeletion: true and the exact current project name as confirmationName. Never infer confirmation from knowing the name. Requires owner access. Frees keyword slots; preserves consumed monthly/trial mention usage and all billing/provider allowances. Emits project.deleted to workspace webhooks. There is no self-service undo.

DestructiveExternal side effects

REST

DELETE/api/v1/projects/:projectId

curl "https://www.stalkr.ai/api/v1/projects/:projectId" \
  --request DELETE \
  --header "Authorization: Bearer $STALKR_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: unique-operation-key"

MCP

Tool name: delete_project

The MCP tool accepts the same input schema and returns the same structured { data, meta } result as REST.

Input

confirmationNamerequired

string

Exact current project name confirmed by the user. Keyword slots are freed; mention history and consumed mention usage are preserved.

confirmDeletionrequired

boolean

Required explicit confirmation. Set true only after the user confirms deleting this specific project after being told the consequences. Never infer consent from knowing the project name.

projectIdrequired

string

idempotencyKey

string

Unique key used to safely retry this write operation

Safe retries

Pass idempotencyKey to the MCP tool or Idempotency-Key to REST when retrying this write.

Authorization

Required scope: projects:write.

Scope authorization is followed by resource authorization. Project operations check current membership and the minimum role required by the underlying workflow.

Related resources

REST conventions · MCP setup · Errors and limits