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 Geocode.Farm is live
Geocode.Farm has quietly powered geocoding in a number of smaller applications and internal tools for a long time, often wired in during an early build and left alone ever since. Our compatibility host is meant for exactly this kind of integration, one that has been running fine and deserves an easy path forward rather than a rewrite.
The host reproduces Geocode.Farm's request parameters and response body exactly, aside from copyright, terms and privacy text, which is My Geocode's own. Requests currently shaped for Geocode.Farm's endpoints can be pointed at our host as is, with the response returned in the same structure existing code already expects.
Switching requires changing a host name and a key, and nothing in the request or response parsing logic around it. That key can authenticate 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 your current integration already sends.
Older integrations like this were often written directly against raw HTTP calls, before an SDK for the provider existed or was worth adopting. My Geocode publishes its own SDKs, listed at /sdks/, for anyone who would rather move off raw HTTP entirely while they are already touching this part of the code, though nothing about the compatibility host requires it.
Pricing follows the same rules as 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. Beyond those, prepaid credit is €0.0001 a request, or an Unlimited package covers usage for €50 a month, with the same rate applying regardless of which host handled the call.
Every response carries our full quota header set: 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, giving usage visibility that a smaller, older integration may never have had before.
For projects that want more than the compatible response returns, adding mg_extras=1 to the request, or an X-MG-Extras header, layers optional extra fields on top, entirely opt in and off by default.
This brings our published compatibility hosts to seventeen in total, spanning geocoding, IP geolocation and elevation. Reaching that number was less about covering every possible provider and more about covering the providers real integrations actually use, which is why the list spans those three categories rather than clustering entirely around one of them.
The host itself is documented at /compatibility/geocode-farm/, and the full list is at /compatibility/. If Geocode.Farm is part of an older integration in your stack, this is a low-effort way to see what a modern quota structure looks like behind the same request shape.