Use case

IP Geolocation API for Content Licensing & Geo-Gating

Enforce where content can be shown — licensing regions, blackouts, and region locks — from a single lookup.

Rights are sold by territory — your delivery has to respect them. One IP lookup tells you the country and region a request comes from, and whether it's hiding behind a VPN or a datacentre, so you can serve, blackout, or block before a single frame loads.


Who uses it

The teams that lean on this most, in rough order of how often we see it.

The signals it uses

Every one ships in the standard response — no add-ons, no tiers.

country / countryCode Allow or block by licensing territory
region Sub-national blackouts and regional rights
is_in_eu EU-wide licensing and distribution rules
security (isVpn / isTor) Flag attempts to geo-spoof around a region lock
connection (type) Spot datacentre traffic evading the gate

How different teams put it to work

The same lookup, applied to the rights each platform has to honour.

Common questions

Can people bypass geo-gating with a VPN?

Determined users can, but you can make it much harder. The response flags common VPN, proxy, and Tor exits and identifies datacentre/hosting networks — the traffic most spoofing runs through. Combine the country with those anonymiser and network-type signals to challenge or block the obvious cases.

How accurate is country detection for licensing?

Country-level accuracy is very high and reliable for licensing and region-lock decisions. Region and city can be null for some IPs, so build territory rules at the country level first and treat finer granularity as best-effort.

Does this replace DRM?

No — it complements it. Geo-gating decides who is allowed to request content from where; DRM protects the content itself once delivered. Most platforms use IP geolocation as the first gate and DRM as the second.

Gate content by region in one request

Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. One call per request, under 50ms median response.