What we shipped this month: geocoding, IP, time zone and more
A roundup of recent work across the API: new compatibility hosts, faster time zone and elevation lookups, dashboard features, and clearer quota visibility.
Drop-in compatibility with ip-api.com is live
ip-api.com is often the first IP geolocation service a developer reaches for, mostly because it is quick to try and easy to wire into a script. That same simplicity is exactly what our compatibility host is built to preserve, while sitting behind a different set of quota and pricing rules.
The host reproduces ip-api.com's request handling and response body exactly, apart from copyright, terms and privacy text, which is ours. A request that used to hit ip-api.com's endpoint can hit ours instead, and the JSON coming back parses the same way, with the same field names in the same places.
Because /v1/ip resolves both address families fully, this compatibility host handles IPv4 and IPv6 lookups the same way. A lookup for an IPv4 address and a lookup for an IPv6 address both come back correctly shaped, without any extra flag needed to tell the host which kind of address it is looking at.
Keys authenticate the same way here as everywhere else across My Geocode: as an X-API-Key header, an Authorization: Bearer header, HTTP Basic auth with the key as the username, or a query parameter. Whichever style your current integration already uses is accepted without modification.
Pricing on this host matches every other host and endpoint we run. Any address gets 2,500 free IP lookups a day with no key at all, counted per network. A key adds its own separate 2,500 free requests a day. Beyond that, prepaid credit costs €0.0001 a request, or an Unlimited package covers everything for €50 a month, with no premium attached to using a compatibility host instead of /v1/ip directly.
Quota headers ride along on every response here as well, something a plain ip-api.com integration does not typically surface on its own: X-Quota-Limit, X-Quota-Used, X-Quota-Free-Remaining, X-Quota-Network-Used, X-Credits-Remaining, X-Key-IPs-Used, X-Key-IPs-Limit and X-Quota-Reset are all included.
For projects that want more than a standard lookup, adding mg_extras=1 to the request, or sending an X-MG-Extras header, adds optional fields like IP threat and network detail on top of the compatible response, without changing its base shape unless you ask for it.
Full details are at /compatibility/ip-api/. If a script somewhere in your stack already talks to ip-api.com, redirecting it here is a quick way to see the difference a quota-aware, EUR-priced host makes.