IPGeolocation.io · Rate Limits

Ipgeolocation Rate Limits

IPGeolocation.io takes an unusually permissive stance on rate limits: paid plans have no documented per-second, per-minute, per-hour, per-day, or per-month request caps — the only ceiling is the plan's monthly credit quota (with overage pricing) defined in plans/ipgeolocation-plans-pricing.yml. The Free plan has a hard cap of 1,000 credits/day with no overage. All limits are scoped to the API key (account). Bulk endpoints accept up to 50,000 entries per request. The documentation does not advertise specific X-RateLimit-* headers; clients should rely on standard HTTP status codes for throttling and fall back to exponential backoff on 429 / 5xx responses.

Ipgeolocation Rate Limits is the machine-readable rate-limit profile for IPGeolocation.io on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests_per_day, requests_per_second, requests_per_month, and entries_per_request.

An exhausted limit returns HTTP 429.

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.

The profile also includes 7 backoff/retry policies defined and response codes documented for quotaExceeded, throttled, unauthorized, forbidden, and serverError.

Tagged areas include Rate Limiting, IP Geolocation, IP Intelligence, and Quota.

4 Limits Exhausted: HTTP 429 Quota: 429
Method: generated, dated 2026-05-29.
Written by API Evangelist on 2026-05-29 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingIP GeolocationIP IntelligenceQuota

Limits

Free plan daily cap key
requests_per_day · day
1000
Hard limit on the Free plan — no overage. Exceeding returns 429.
Paid plan request rate key
requests_per_second
no documented per-second limit on paid plans
IPGeolocation explicitly states there are no hourly, daily, or monthly rate limits on any paid plan, and no per-minute cap on any plan. The only effective ceiling is the monthly quota (with overage).
Paid plan monthly quota key
requests_per_month
plan-defined (150K → 5M+); see plans/ipgeolocation-plans-pricing.yml
Monthly credit quotas vary by plan: Starter 150K, Plus 500K, Pro 1M, Business 2M, Premium 5M, Enterprise custom. Overage is charged per block (e.g. $5 per 25K on Starter) rather than blocked.
Bulk endpoint payload size key
entries_per_request
50000
Bulk endpoints (POST /v3/ipgeo-bulk, POST /v3/security-bulk, POST /v3/user-agent-bulk) accept up to 50,000 entries per request. Bulk endpoints require a paid plan.

Policies

Hard cap on Free plan
The Free plan's 1,000 credits/day is a hard limit — once exhausted, additional requests are rejected with 429 until the next day. Free plan users cannot pay overage to continue.
Overage on paid plans
Once a paid plan exceeds its monthly quota, IPGeolocation continues to serve requests and charges an overage surcharge per block on top of the monthly subscription. Requests are not throttled at quota exhaustion.
Shared quota across all 7 APIs
A single API key's quota is shared across all seven products (IP Geolocation, IP Security, ASN, Abuse, Timezone, Astronomy, User Agent). Every request to any endpoint deducts one credit.
Retry on 429 / 5xx
Clients should treat 429 as a soft throttling signal on paid plans (rare, since no published RPS cap) and retry with exponential backoff starting at 1 second, doubling up to 30 seconds, with a maximum of 5 retries.
Bulk over single
For high-volume enrichment, prefer the bulk endpoints — one request of up to 50,000 entries is one HTTP call but still 50,000 credits. The benefit is throughput, not cost.
HTTPS required
All endpoints are served over HTTPS only — including the Free plan.
Request Origin (CORS) authentication
For browser/client-side use, IPGeolocation supports Request Origin (CORS) authentication tied to a registered domain on the dashboard. This avoids embedding the API key in client code.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/ipgeolocation-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.