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.