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 Open-Elevation is live
Open-Elevation has long served as a simple, no-frills way to attach ground height to a set of coordinates. Our compatibility host takes that same request and response shape and puts a fully working elevation service behind it, along with a quota structure that tells you exactly what you have used.
The host reproduces Open-Elevation's request parameters and response body exactly, aside from copyright, terms and privacy text, which is ours rather than the original provider's. Send a set of coordinates the way you already send them to Open-Elevation, and the elevation values come back in the same JSON shape your existing code parses today.
Because our elevation endpoint is fully working, this is not just a shape match. Query the coordinates for a location and the response returns a real elevation figure in meters, the same way /v1/elevation does directly. Batch requests work the same way too, with each coordinate pair counted as one request rather than the call as a whole.
Authentication accepts our usual four methods: an X-API-Key header, an Authorization: Bearer header, HTTP Basic auth with the key as the username, or a query parameter. Since Open-Elevation is often used without any authentication at all, adding a key here also means gaining a dedicated, trackable allowance rather than relying on a shared, unmanaged resource.
Pricing matches every other host on the 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 both, prepaid credit is €0.0001 a request, or an Unlimited package covers usage for €50 a month.
Quota headers accompany every response: X-Quota-Limit, X-Quota-Used, X-Quota-Free-Remaining, X-Quota-Network-Used and X-Credits-Remaining are all present, giving reliable visibility into elevation lookup volume that a shared public instance typically does not offer.
For anything beyond the standard elevation response, mg_extras=1 on the request, or an X-MG-Extras header, adds optional extras on top of the compatible shape, entirely by choice.
The host is documented at /compatibility/open-elevation/, and the underlying elevation endpoint is covered fully at /docs/elevation-lookup/. If elevation lookups are part of a mapping or routing feature today, this is a straightforward way to add a dedicated allowance behind the same request shape.