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 Geoapify is live
Geoapify pairs geocoding with a wider set of location tools, which means integrations built against it sometimes touch more of a codebase than a single API call would suggest. Our compatibility host focuses narrowly on the geocoding request and response shape, matched exactly, so that piece can move without disturbing everything around it.
The host reproduces Geoapify's request parameters and response body precisely, aside from copyright, terms and privacy text, which is ours rather than the original provider's. A request currently built for Geoapify's geocoding endpoints can be sent to our host as is, and the JSON returned parses the same way existing code already expects.
Narrowing the scope this way is deliberate. Geoapify's own platform covers routing, isochrones and places search alongside geocoding, and trying to match all of that inside one compatibility host would tie its release schedule to features well outside geocoding itself. Restricting the host to the geocoding endpoints keeps it simple to verify against the original service and easy to keep in step as My Geocode adds capabilities of its own.
Switching over means changing a host name and a key, nothing more. That key authenticates the same flexible way it does across every host we operate: as an X-API-Key header, an Authorization: Bearer header, HTTP Basic auth with the key as the username, or a query parameter. Whichever your current client sends, it is accepted here too.
The pricing underneath is unchanged from the rest of the platform. Any address gets 2,500 free requests a day with no key at all, counted per network. A key adds its own 2,500 free requests a day on top of that. Beyond both allowances, prepaid credit costs €0.0001 a request, or an Unlimited package covers everything for €50 a month, with the same rate applying whether a call went to this host or to /v1/forward directly.
Quota headers accompany every response here as well: 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 all show up, giving visibility a straight Geoapify integration does not build in on its own.
Moving a geocoding integration to a new provider is also a reasonable moment to tighten account security generally. The dashboard's two-factor authentication setting sits next to API keys and billing, so turning it on for an account that now holds a new key takes one extra step rather than a separate project of its own.
For anything beyond the standard compatible response, adding mg_extras=1 to a request, or an X-MG-Extras header, layers optional fields on top without changing the base shape unless explicitly requested.
Full documentation for the host is at /compatibility/geoapify/, and the broader compatibility reference covering all seventeen hosts is at /docs/compatibility/. If Geoapify already sits behind part of your stack, this is a low-effort way to compare it against ours.