LimitWatch

xAI (Grok) · rate-limit · between 2026-06-15 and 2026-07-06 Backfilled

xAI (Grok): Request limits switched from requests per minute to requests per second, derived as RPM / 60.

Old RPM and TPM caps per model
New RPS (= RPM / 60) and TPM caps per model

Why it matters: If you use xAI API (request rate limits), this changes how much you can send before requests are limited. The source does not state a separate effective date.

Alerts waitlist (not launched)

Email alerts ($9/mo) when a company changes pricing or limits. Not live yet; waitlist only.

Choose companies (optional) 0 selected

Joining sends nothing now; we keep your email only to tell you when alerts launch. Remove it any time: support@testedmcp.com. Stored by Netlify Forms. Privacy

ProductxAI API (request rate limits)
Categoryrate-limit
Announced / detectedbetween 2026-06-15 and 2026-07-06 Backfilled
BackfilledYes: added retroactively, detected between 2026-06-15 and 2026-07-06
Quote verified againsthttps://web.archive.org/web/20260706202503/https://docs.x.ai/developers/rate-limits
Archive captureshttps://web.archive.org/web/20260615234539/https://docs.x.ai/developers/rate-limits
https://web.archive.org/web/20260706202503/https://docs.x.ai/developers/rate-limits
Effectivenot stated in source
BeforeRPM and TPM caps per model
AfterRPS (= RPM / 60) and TPM caps per model
Official sourcehttps://docs.x.ai/developers/rate-limits
Source quote
Your per-second limit is derived from your per-minute request budget (RPM / 60)
ArchiveNo post-change Wayback capture found
Snapshot hashsha256:14d6624b6c52abdb737570ee827536a54376441c03e4ae1978215ad406020dc0
Statusverified

All xAI (Grok) changes · Dispute or correct this entry

Previous changes from xAI (Grok)

How xAI (Grok) limits and pricing work · All changes, July 2026