Skip to main content
Use kill-switch endpoints during security incidents.

​
POST /v1/identity/kill-switch/minting

Pause or resume minting. 
curl -sS -X POST "https://api.clawb.ai/api/v1/identity/kill-switch/minting" \
  -H "Content-Type: application/json" \
  -H "X-Clawb-Api-Key: ck_live_replace_me" \
  -d '{"paused": true, "reason": "incident INC-123"}'

​
Example response

{
  "ok": true,
  "minting_paused": true,
  "reason": "incident INC-123"
}

​
POST /v1/identity/kill-switch/revoke-all

Sets a workspace cutoff timestamp so existing minted credentials are treated as revoked. 
curl -sS -X POST "https://api.clawb.ai/api/v1/identity/kill-switch/revoke-all" \
  -H "Content-Type: application/json" \
  -H "X-Clawb-Api-Key: ck_live_replace_me" \
  -d '{"reason":"key compromise"}'

​
Example response

{
  "ok": true,
  "all_credentials_revoked_at": "2026-02-28T00:00:00Z",
  "reason": "key compromise"
}

​
GET /v1/identity/kill-switch/status

curl -sS "https://api.clawb.ai/api/v1/identity/kill-switch/status" \
  -H "X-Clawb-Api-Key: ck_live_replace_me"

​
Example response

{
  "ok": true,
  "minting_paused": false,
  "all_credentials_revoked_at": null
}

​
Incident sequence

  1. Pause minting.
  2. Revoke all credentials.
  3. Rotate keys and fix root cause.
  4. Verify status.
  5. Resume minting only after validation.