Ipregistry Rate Limits
IPregistry does not enforce hard rate limits by default. The primary constraint on API usage is the credit balance on the account — each IP lookup costs one credit, batch requests cost (quantity + 1) credits, and user-agent or ASN lookups each cost one credit. Optional hourly invocation limits can be configured per API key through the dashboard to protect against runaway usage or abuse. When throttling is enabled, IPregistry implements a leaky-bucket-style algorithm that resets limits gradually over each hour rather than hard-resetting at the boundary, providing smoother traffic shaping and burst absorption.
Ipregistry Rate Limits is the machine-readable rate-limit profile for IPregistry on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions.
Limit state is signalled in the X-Rate-Limit-Limit, X-Rate-Limit-Remaining, X-Rate-Limit-Reset, and Retry-After response headers.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
Tagged areas include IP Geolocation, Threat Intelligence, IP Address, ASN, and Carrier.
X-Rate-Limit-LimitX-Rate-Limit-RemainingX-Rate-Limit-ResetRetry-After
generated.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.