Mercury Hq Com Rate Limits
Published limits exist only on the API-key rail and are per key per minute, stated in the /pricing tier table; the x402 rail publishes no request limit - an unpaid caller is stopped by the 402 payment challenge rather than a quota, and nothing on the docs, OpenAPI, llms.txt or discovery documents mentions a per-wallet ceiling. No rate-limit header (RateLimit-*, X-RateLimit-*) appeared on any probed response and the status code and body returned on exhaustion are undocumented, so an agent on the key rail has the number but no runtime signal. The one Retry-After observed (3600) was on the 503 mint-disabled response of a gated SKU, which is a delivery-off signal, not throttling.
Mercury Hq Com Rate Limits is the machine-readable rate-limit profile for MERCURY on the APIs.io network, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions.
Limit state is signalled in the observed, checked_for, and note response headers.
Tagged areas include Company, Agents, A2A, MCP, and x402.
observedchecked_fornote
Limits
Sources
- https://network.mercury-hq.com/pricing (tier table with a "Rate limit" column)
- https://network.mercury-hq.com/university/developers (key-issuance cap)
- https://network.mercury-hq.com/terms ("honours target robots/rate limits on a best-effort basis" - about upstream sites, not a limit on callers)
- response headers observed 2026-09-19 on GET /buy/fetch (402), GET /buy/signal (200), GET /buy/matter (503), POST /mcp tools/list (200), POST /a2a (200), GET /openapi.json (200)
- text search of openapi.json, llms.txt, /catalog and /.well-known/x402 for "rate limit", "429", "quota", "Retry-After"
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.