Simple, Transparent Pricing

Start free and scale as you grow. All plans include full API access.

Monthly Annual Save ~17%

Free

$0 /month
  • 5,000 requests/month
  • 2 requests/second
  • All endpoints included
  • Community support
Get Started

Basic

$29 /month
  • 500,000 requests/month
  • 10 requests/second
  • All endpoints included
  • Email support
Subscribe
Popular

Pro

$99 /month
  • 2,000,000 requests/month
  • 30 requests/second
  • All endpoints included
  • Priority support
Subscribe

Business

$299 /month
  • 10,000,000 requests/month
  • 50 requests/second
  • All endpoints included
  • Dedicated support
Subscribe

Enterprise

Need higher limits, custom SLAs, or dedicated infrastructure?

Contact Us

Feature Comparison

Feature Free Basic Pro Business
Monthly Requests 5K 500K 2M 10M
Rate Limit 2/s 10/s 30/s 50/s
Countries, Regions, Cities
Postal Codes
Timezones
IP Geolocation
Cross-type Search
Field Selection
Area filter (?within=)
Bounding-box filter (?bbox=)
Point → admin resolve
Boundary GeoJSON Countries only Countries + regions Countries + regions Countries + regions
Support Community Email Priority Dedicated

How quota is charged

  • A boundary fetch costs 5 quota units. An area filter (?within=) costs 2 quota units. A bounding-box filter (?bbox=) and a point → admin resolve cost 1 quota unit each.
  • Free's 5,000 monthly units therefore buy 1,000 boundary fetches, not 5,000.
  • Because 5 exceeds Free's 2/s rate limit, the charged cost is clamped down to the tier's own per-second limit, so a Free key gets one boundary fetch per second. The clamp is what makes the endpoint reachable at all: without it a request costing 5 against a limit of 2 is refused on an idle key, and every Free boundary fetch would be rate-limited before it ran.
  • The highest multiplier wins and costs never sum: a boundary fetch carrying ?bbox= costs 5, not 6, and ?within= with ?bbox= costs 2, not 3 — a bounding box narrows the candidate set before the polygon test, so adding one makes the query dramatically cheaper to serve.

Region-level boundary geometry has required a paid plan since 2026-08-30. A Free key calling GET /v1/boundaries/{geoname_id} for a region receives 403 tier_upgrade_required with an upgrade link in the body; country geometry stays free on every tier. The full note is in the changelog and the boundary guide.