Ipstack Rate Limits
IPstack meters by MONTHLY REQUEST QUOTA, not by requests-per-second, and it publishes no runtime rate-limit signal at all. An agent gets no header telling it how much quota is left, no Retry-After when it runs out, and no distinct HTTP status — the same HTTP 200 that carries a successful lookup carries the failure.
Ipstack Rate Limits is the machine-readable rate-limit profile for IPstack on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions.
Limit state is signalled in the observed, x_ratelimit, ratelimit_draft, and retry_after response headers.
Tagged areas include Geocoding, IP Geolocation, Location, Threat Intelligence, and Networking.
observedx_ratelimitratelimit_draftretry_after
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.