Enable Grok Bot with the Admin API

Turn Grok Bot on for the team with POST https://api.cursor.com/grok-bot/enable. Official reference: Admin API → Enable 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. A 429 includes Retry-After: 60.

Call

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

Success returns 204 No Content.

On an eligible Enterprise team, the first enable starts the trial.

After enable

Confirm the team is live with GET /grok-bot/capabilities — enabled should be true. That field is read-only on the capabilities route; enable and disable are the only ways to flip it.

Dashboard Enable/Disable on the Grok Bot page is the UI twin of these routes. Use the API when you already automate Admin API provisioning.

Pitfalls

• Calling enable with a read:* key — writes need admin:* and return 401 otherwise
• Expecting a JSON body on success — the documented success is empty 204
• Using PATCH /grok-bot/capabilities with enabled — that field is rejected; use this route instead