Erase a tenant
Destroys the tenant, its subjects, every objective associated with it and everything reachable from those objectives, and its widget sessions. This is the full erasure hammer, wider than DELETE /widget_sessions, which removes only what widget sessions created. The work runs in the background: this returns the tenant in STATE_ERASING rather than a count of what was removed, since a large tenant’s history cannot be destroyed inside a request. Poll the tenant to follow it — STATE_ERASING while it runs, NotFound once it finishes. Erasure is terminal; a tenant cannot be recovered once it starts.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Workspace ID.
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
Tenant to destroy. Accepts the canonical tenant_… form or the
external_id:<value> form.
Response
OK
Tenant is the customer's organization as a readable record rather than an
echo. It carries no spec: a tenant is never configured, only asserted, so
everything about it lives in the metadata envelope — external_id is the key
the customer asserted it under, name is the most recent name they asserted,
and updated_at is therefore when the tenant was last asserted.
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
The current lifecycle state of the tenant. Output only.
STATE_UNSPECIFIED, STATE_ACTIVE, STATE_ERASING TenantInfo provides read-only server-derived data about a tenant.