Skip to main content
Each API key can make 15 requests per second. Searches also count against a daily cap.

Request rate

Every MCP message and every REST call counts toward the 15 requests per second limit. This includes tool calls, health checks, and search — not only searches. When you exceed 15 per second, the response is HTTP 429 with:
  • A Retry-After header (seconds)
  • Error code rate_limited
  • retry_after_seconds in the body
The same shape is returned on both MCP and REST.

Daily search cap

search_catalog counts against a per-key daily allowance. The cap resets at UTC midnight. When the cap is hit, the response includes:
Only successful search_catalog calls consume the allowance. These do not count:
  • Failed searches with invalid_key, unauthorized, invalid_arguments, rate_limited, or daily_limit_reached
  • All non-search tools: get_product, create_cart, update_cart, create_checkout, complete_checkout, and every other tool

What doesn’t count

Cart, checkout, sign-in, and order operations never consume the search cap. Only search_catalog does.

Increasing limits

Need a higher request rate or search cap? Reply to your welcome email.