Skip to main content

Rate limits & fair use

EDITED MCP currently enforces no published per-key rate limits. Usage is subject to fair use: the service is shared, and clients that hammer it with unnecessary traffic may be throttled or contacted.

If hard limits are introduced, they'll be announced in the changelog before they take effect.

Stay fast and friendly​

The patterns that keep you inside fair use are the same ones that make your agent faster:

  • Batch instead of looping. The market-data search tools accept a list of up to ten queries and run them concurrently — one round-trip instead of ten. See Concepts → Tools.
  • Cache resolved identifiers. The slug/id values that searches return are stable — once your agent has resolved "Zara UK" to zara-uk, reuse it rather than searching again in the same session.
  • Back off on 5xx. Retry transient failures with exponential backoff rather than tight loops — see Errors. Write clients to treat a 429 Too Many Requests the same way; it isn't sent today, but a client that already handles it won't break if limits arrive.