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.
Autocomplete suggestions added across compatible hosts
Address autocomplete is a different kind of request from a straight geocoding lookup: it needs to respond to partial, changing input rather than a single finished address, usually as someone types into a form. We have extended our compatibility hosts to support this pattern as well, matching the autocomplete request shape of the providers that offer it.
This sits alongside our native /v1/autocomplete endpoint, documented at /docs/address-autocomplete/, which handles the same kind of partial-address request directly. Wherever a compatibility host's original provider also offers autocomplete, that same request shape is now supported on our equivalent host, aside from copyright, terms and privacy text, which is ours.
Authentication and pricing for autocomplete requests follow exactly the same rules as every other request type on the platform. A key authenticates as an X-API-Key header, an Authorization: Bearer header, HTTP Basic auth, or a query parameter, and usage counts against the same free daily allowance, whether that allowance comes from the calling network or from the key itself. Beyond the free allowance, autocomplete requests draw on prepaid credit at €0.0001 a request or are covered by an Unlimited package, exactly like any other endpoint.
Autocomplete traffic tends to run at a different pace than a typical geocoding lookup, often firing on every keystroke as someone types an address into a form rather than once per finished submission. That makes quota visibility especially useful here: the same quota headers attached to every response, X-Quota-Limit, X-Quota-Used, X-Quota-Free-Remaining and the rest, let an integration watch consumption in real time and adjust behavior, such as debouncing requests more aggressively, if usage is running higher than expected.
For teams that already use a compatibility host for geocoding and separately handle autocomplete through another provider or a second integration, this update means autocomplete can now potentially move onto the same host and the same key, consolidating both request types under one account rather than splitting them across two.
Which compatibility hosts support autocomplete depends on whether their original provider does, and the details for each are documented on that host's own page, reachable from the full list at /compatibility/. Testing autocomplete against a compatible host costs nothing to try, given the free allowance available to any new key.