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.
Batch limits: matching what the big providers already allow
A batch integration built against a large, established provider was usually built around whatever batch size that provider already supported, since there was rarely a reason to test smaller. When that same integration gets pointed at a new provider, one of the first questions is whether the batch size it already sends will actually be accepted, or whether it needs to be split down into smaller pieces first.
We built our batch handling with exactly that concern in mind. Rather than picking an arbitrary limit and asking every integration to adjust around it, we sized batch support to match what the large providers our compatibility hosts stand in for already allow. An integration sending a batch shaped for Geocodio, or for Google Maps Platform, should not need to resize that batch just because the destination changed.
Pricing for batch requests stays exactly the same regardless of size: every item inside a batch counts as one request, not the call as a whole. A batch of a hundred addresses counts as a hundred requests against whatever allowance applies, whether that is the free daily allowance, prepaid credit at €0.0001 a request, or coverage under an Unlimited package. There is no separate, different rate that kicks in at a particular batch size, and no incentive to break work into smaller calls purely to manage cost.
This applies the same way across native endpoints and compatibility hosts alike. A batch sent to /v1/forward directly and a batch sent to a compatibility host shaped for a large provider are both handled by the same underlying batch logic, sized the same way, priced the same way, and reflected the same way in the quota headers attached to the response.
For teams migrating an existing batch integration over, this means the migration itself should be uneventful on the batch-sizing front specifically. The migration guides at /docs/compatibility/ cover the details worth checking for each provider, but batch size limits should not be one of the things that requires extra engineering work during a switch.
If you run batch jobs today against a provider you are considering leaving, testing the same batch size against the equivalent My Geocode compatibility host is a quick way to confirm this in practice, and it costs nothing to try given the free allowance covers meaningful testing before any commitment is needed.