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 Geocodio is live
Geocodio built a reputation on straightforward batch geocoding, and a fair number of integrations built against it lean on that batch behavior heavily. Our compatibility host matches both the single-lookup and batch request shapes exactly, so that reliance does not become a blocker to switching.
The host reproduces Geocodio's request parameters and response body precisely, aside from copyright, terms and privacy text, which is My Geocode's own. Requests currently shaped for Geocodio's endpoints, single or batch, can be sent to our host as is, with responses parsing the same way existing code already expects.
Batch requests are counted the same way here as everywhere on the platform: each address inside a batch call counts as one request, not the call as a whole. That keeps quota tracking accurate regardless of whether a call carries one address or many.
A batch of five hundred addresses submitted in one call is metered as five hundred requests against quota, and against prepaid credit if the free allowances are already used up, the same as five hundred separate calls would be. That granularity is what lets X-Quota-Used and X-Credits-Remaining stay accurate the moment a large batch finishes, rather than settling a few minutes later once some background job catches up.
Authentication uses our standard four options: 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 Geocodio integration already uses.
Pricing is the same across the whole platform. Any address gets 2,500 free requests a day with no key needed, counted per network. A key adds its own 2,500 free requests a day. Beyond those, prepaid credit runs at €0.0001 a request, or an Unlimited package covers everything for €50 a month, with the same rate applying to single lookups and batch items alike.
Coupon codes in the dashboard are a common way to test a batch-heavy migration like this without committing real budget first, applying a credit balance to an account before deciding whether to fund it properly through prepaid credit or an Unlimited package.
Quota headers accompany every response, batch or single: X-Quota-Limit, X-Quota-Used, X-Quota-Free-Remaining, X-Quota-Network-Used and X-Credits-Remaining reflect exactly how many items a batch consumed, giving a precision that is easy to plan around.
If a project wants more than the standard compatible response, mg_extras=1 on the request, or an X-MG-Extras header, layers optional extra fields on top, without touching the base shape unless explicitly requested.
The host is documented at /compatibility/geocodio/, and general guidance on switching an existing integration over is at /docs/compatibility/. Testing a batch call against the new host is a fast way to confirm quota counting behaves exactly as expected before relying on it for real volume.