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 LocationIQ is live
LocationIQ has earned a place in a lot of stacks that started small and grew, often because it was easy to adopt early on. Our compatibility host is aimed at exactly that kind of integration: one that works fine today, was never meant to be permanent, and has simply never been worth rewriting.
The host reproduces LocationIQ's request parameters and response body exactly, aside from copyright, terms and privacy text, which is My Geocode's own. Requests shaped for LocationIQ's endpoints can be sent to our host unchanged, and the response returned parses the same way existing code already expects it to.
That exactness is not a coincidence of effort spent per provider. Every compatibility host sits on top of the same billing, quota and account system that runs the rest of My Geocode, so building a new one is mostly a mapping exercise, matching field names and parameter shapes to what a given provider's clients already send, rather than standing up a separate backend. That is why pricing, authentication and quota tracking behave identically across all seventeen hosts instead of drifting apart from one another over time.
Authentication follows the same pattern used across every host on the platform. Send your key as an X-API-Key header, an Authorization: Bearer header, HTTP Basic auth with the key as the username, or a query parameter, matching whatever your current LocationIQ integration already does. All four are accepted here without exception, so switching rarely means touching your HTTP client at all.
Pricing does not shift based on which host or endpoint handles a call. Any address gets 2,500 free requests a day with no key required, counted per network so the allowance maps sensibly to a shared connection rather than to every device behind it. A key adds a further 2,500 free requests a day of its own, tracked separately from the keyless allowance on the same network. Past those, prepaid credit is €0.0001 a request, or an Unlimited package covers it all for €50 a month.
Every response carries our full quota header set, regardless of which compatibility host handled it: X-Quota-Limit, X-Quota-Used, X-Quota-Free-Remaining, X-Quota-Network-Used and X-Credits-Remaining are attached to this host's responses exactly as they are to our native endpoints, so anything built around those headers keeps working unchanged.
If a project needs more than the compatible response provides, mg_extras=1 on the request, or an X-MG-Extras header, adds optional extra fields on top, entirely opt in. On a geocoding call, that can include ground elevation for the returned coordinates, pulled from the same source that answers /v1/elevation directly. Skip it, and the response format matches LocationIQ's shape precisely, with no surprises for existing parsing logic.
Accounts that make the switch and find it holds up under real traffic often end up recommending it to whoever else on their team is still paying for the original provider. The referral program in the dashboard, at /dashboard/referrals, is built for exactly that kind of word of mouth.
The host is documented at /compatibility/locationiq/, with general guidance on switching providers at /docs/compatibility/. A single test call against a fresh key is usually enough to confirm it fits into an existing integration cleanly.