Chess.com · Rate Limits
Chess Com Rate Limits
Rate-limit posture for the Chess.com Published Data API. The API does not publish a numeric limit but enforces throttling on parallel requests.
Chess Com Rate Limits is the machine-readable rate-limit profile for Chess.com on the APIs.io network, conforming to the API Commons Rate Limits specification.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, notFound, and gone.
Tagged areas include Chess, Rate Limiting, and Public API.
0 Limits
Throttle: 429
ChessRate LimitingPublic API
Policies
Serial requests unlimited
Serial (non-parallel) client traffic is unlimited in practice.
Parallel requests throttled
Concurrent requests against the same path or against many paths in parallel will receive 429 Too Many Requests responses. There is no published per-IP or per-key quota.
Cache refresh window
Most endpoints refresh at most every 12-24 hours. Clients SHOULD honor ETag and Last-Modified to avoid revalidation traffic.
User-Agent requirement
Clients SHOULD include a recognizable User-Agent header containing a contact email or URL. Generic or empty User-Agents may be blocked.
Stale-player tolerance
About 3% of players still using legacy V2 website may have slightly stale data.
Sources
- https://www.chess.com/news/view/published-data-api
- https://support.chess.com/en/articles/9650547-published-data-api
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.