Meilisearch · Rate Limits

Meilisearch Rate Limits

Meilisearch Cloud throughput depends on plan and resource size.

Meilisearch Rate Limits is the machine-readable rate-limit profile for Meilisearch on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring queries_per_second, documents_per_request, and concurrent.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes response codes documented for throttled.

Tagged areas include Rate Limiting and Search.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-04.
Written by API Evangelist on 2026-05-04 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingSearch

Limits

Search API project
queries_per_second
scales with resource
Indexing API project
documents_per_request
varies by request size
Concurrent indexing tasks project
concurrent
4

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/meilisearch-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.