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 Mapbox Geocoding is live
A lot of the code written against Mapbox Geocoding lives inside front-end applications, mobile apps, and internal tools where the geocoding call itself is a small, easy-to-miss detail buried in a larger system. Changing a provider there usually means finding every place that detail lives before anything else can happen. Our compatibility host is meant to shrink that job down to almost nothing.
It reproduces Mapbox's request format and response structure exactly, aside from copyright, terms and privacy text, which is My Geocode's own. Wherever your code currently sends a request shaped for Mapbox, it can send that same request to our host instead, and the response coming back will parse the same way your existing code already expects.
Authentication follows our usual pattern rather than forcing a rewrite of that part either. 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, whichever matches how your client currently authenticates. All four work on every host and every endpoint we run.
Pricing does not change based on which host handled the request. Any address gets 2,500 free requests a day with no key required, counted per network rather than per individual caller. A key adds a further 2,500 free requests a day of its own. Beyond both allowances, prepaid credit is €0.0001 a request, or an Unlimited package covers it all for €50 a month. The compatibility host costs exactly the same as our native /v1/forward and /v1/reverse endpoints.
Quota headers are attached to every response regardless of format, giving visibility that a straight Mapbox integration does not provide on its own: X-Quota-Limit, X-Quota-Used, X-Quota-Free-Remaining, X-Credits-Remaining, X-Key-IPs-Used, X-Key-IPs-Limit and X-Quota-Reset all show up on this host the same way they do everywhere else.
For anything beyond the compatible response shape, mg_extras=1 on the request, or an X-MG-Extras header, adds optional extra fields on top without altering the base structure. It is off by default, so the response matches Mapbox's shape until you explicitly ask for more.
The host lives at /compatibility/mapbox/, with general guidance on moving an integration over at /docs/compatibility/. If you maintain a Mapbox-shaped integration today, testing this costs one key and one changed base URL.