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 OpenCage is live
OpenCage has built a following among developers who like a straightforward, well-documented geocoding API without much else attached. We built our compatibility host in that same spirit: match the request and response format exactly, so nothing about switching feels like starting over.
The host reproduces OpenCage's request parameters and response body precisely, with the only differences being copyright, terms and privacy text, which is My Geocode's own. Code that currently builds an OpenCage-shaped request and parses an OpenCage-shaped response can be pointed at our host with those two pieces left entirely untouched.
What changes is the host name in your configuration and the key you authenticate with. That key can be sent 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 approach your existing client library already takes. All four work the same way across every host we run.
Pricing follows our standard structure regardless of which host handles a request. 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. Past both allowances, prepaid credit runs at €0.0001 a request, or an Unlimited package covers usage for €50 a month, and none of that changes based on whether a call went through this compatibility host or through /v1/forward directly.
Quota headers ride along on every response, giving a layer of usage visibility that a plain OpenCage integration would not otherwise have: 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 are all included, every time.
For teams that want more than the compatible response returns by default, adding mg_extras=1 to the request, or an X-MG-Extras header, layers optional fields on top, such as ground elevation, without disturbing the base shape unless you ask for it.
Documentation for the host lives at /compatibility/opencage/, and a broader look at how compatibility hosts work across the platform is at /docs/compatibility/. If OpenCage is already wired into your stack, testing this over is a matter of one changed base URL and a fresh key.