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 ipstack is live
Plenty of applications reach for IP geolocation exactly once, at the point a user first connects, to guess a country or set a default currency and move on. ipstack has long been a common pick for that single step. Our new compatibility host lets that step keep working the same way, against a different backend.
The host mirrors ipstack's request parameters and response body precisely, aside from copyright, terms and privacy text, which reflects My Geocode rather than the original provider. Wherever your application currently sends a lookup shaped for ipstack, it can send that same lookup to our host, and the fields coming back land in the same places your existing parsing code expects.
Both address families are supported fully here, matching how /v1/ip works everywhere else on the platform. An IPv4 address and an IPv6 address both resolve correctly against this host, with the same response shape either way.
Keys can travel as an X-API-Key header, an Authorization: Bearer header, HTTP Basic auth with the key as the username, or a query parameter, matching whichever pattern your existing ipstack integration already uses. All four are accepted identically across every host and endpoint we run, so authentication code rarely needs to change.
The pricing behind this host is the same as everywhere else. Any address gets 2,500 free lookups a day with no key needed, counted per network so a shared office or building draws from one pool rather than many. A key adds a further 2,500 free requests a day on its own. Past those allowances, prepaid credit is €0.0001 a request, or an Unlimited package covers it for €50 a month, with no separate rate for this compatibility host.
Every response includes our full quota header set as well, something a plain ipstack integration would not otherwise expose: X-Quota-Limit, X-Quota-Used, X-Quota-Free-Remaining, X-Quota-Network-Used and X-Credits-Remaining are all present, call after call.
If your project wants more than the standard response, mg_extras=1 on the request, or an X-MG-Extras header, adds optional fields such as IP threat and network detail on top of the compatible shape. It stays off by default, so nothing changes in the response format unless you specifically ask for it.
The compatibility host is documented at /compatibility/ipstack/, with the full IP lookup reference at /docs/ipv4-lookup/ and /docs/ipv6-lookup/ covering everything underneath it.