Disable Grok Bot with the Admin API

Turn Grok Bot off for the team with POST https://api.cursor.com/grok-bot/disable. Official reference: Admin API → Disable Grok Bot.

Authenticate with a team Admin API key (Basic auth, key as username, empty password). Writes need admin:*. Rate limit: 20 requests per minute per team per endpoint.

Call

curl -X POST https://api.cursor.com/grok-bot/disable \
  -u YOUR_API_KEY:

Success returns 204 No Content.

Members lose access. Their computers are not deleted — disk and prior work remain; members cannot run Bot until you enable again.

Plan gate

Disable returns 403 on Teams plans. Enterprise is the plan that can disable through this write path. Reads such as GET /grok-bot/access still work on every plan.

After disable

GET /grok-bot/capabilities reports enabled: false. Re-enable with POST /grok-bot/enable when access should return.

Pitfalls

• Assuming disable wipes computers — it only blocks access
• Calling disable on a Teams plan and treating 403 as a bad key
• Sending enabled: false on PATCH /grok-bot/capabilities — use this route; enabled is read-only there