Lichess · Rate Limits

Lichess Rate Limits

Lichess applies multiple per-endpoint rate-limiting strategies to keep the public API responsive for everyone. All limits are enforced server-side; the official guidance is to make only one request at a time and to back off on HTTP 429. There is no formal published quota table. Limits are documented inline in the OpenAPI per-endpoint description, with example values surfaced in this file.

Lichess Rate Limits is the machine-readable rate-limit profile for Lichess on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 16 rate-limit definitions.

The profile also includes response codes documented for throttled and quotaExceeded.

Tagged areas include Chess, Rate Limiting, and Fair Use.

16 Limits Throttle: 429 Quota: 429
ChessRate LimitingFair Use

Limits

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/lichess-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.