Stayingapi Rate Limits
StayingAPI publishes a per-plan request-rate limit in requests per minute, enforced per-key for REST and on a separate per-user bucket for the MCP server. It is a token bucket: exhaustion returns 429 rate_limit_exceeded with Retry-After. The rate limit is the second of two independent throttles — the first is the credit balance, which meters work rather than request frequency.
Stayingapi Rate Limits is the machine-readable rate-limit profile for StayingAPI on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring requests_per_minute.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting, Travel, and Accommodation Data.
limitremainingresetretryAfter
Limits
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.