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.
Migration guides: a new home for switching providers
Knowing a compatibility host exists is one thing. Knowing exactly how to move an existing integration onto it, without breaking anything along the way, is another. We built a dedicated set of migration guides to close that gap, gathered together at /docs/compatibility/.
The guides walk through the practical steps of switching: what changes in a request, what stays the same, which authentication method to use, and what to watch for in the response, provider by provider, endpoint by endpoint. Since each of our seventeen compatibility hosts reproduces its original provider's request and response shape exactly, aside from copyright, terms and privacy text, the guides focus mostly on the parts that genuinely differ: the host name to point at, the key to generate, and the quota headers that now ride along with every response.
We wrote these with a specific reader in mind: someone who already has working code against another provider and wants confidence, not just a promise, that pointing it at us will keep working. That means being explicit about pricing during the transition too. Every endpoint and every compatibility host costs the same, with 2,500 free requests a day from any address and a further 2,500 free requests a day per key, so testing a migration costs nothing before you commit to it.
Each guide also covers the small details that tend to trip up a migration if left unaddressed: how batch requests are counted, since a bulk call counts each item individually rather than the call as a whole, and what the extra quota headers on each response mean if you have not seen them before. None of that requires guesswork once the relevant guide is open next to your code.
For a team weighing whether to move, the recommended path is straightforward: read the guide for whichever provider you currently use, generate a key, and test a handful of real requests against the compatible host before touching any production code. Because the free allowance covers that testing entirely, there is no cost to comparing the two side by side before deciding.
The full list of compatibility hosts covered by these guides sits at /compatibility/, and general authentication and rate limit documentation that applies across all of them is at /docs/authentication/ and /docs/rate-limits/. We plan to keep expanding this guide collection as compatibility coverage grows.