Verifying an address matches its stated postal code before checkout
A mismatched postal code and city on an order form looks like a small typo until it turns into a delivery sent to the wrong part of the country entirely.
Building a farm equipment dealer locator
Rural coverage breaks a lot of assumptions that store locators built for cities carry with them by default. A farm equipment manufacturer with a network of independent dealers spread across large agricultural regions found that a locator tuned for city-scale distances, showing dealers within a ten or twenty mile radius, returned an empty result for a meaningful share of its customers, who might reasonably expect to drive an hour or more to reach the nearest dealer for a major purchase.
Building a locator suited to that reality started the same way any distance-based locator does, with coordinates. Every dealer address in the manufacturer's network was geocoded once, in a single batch through /v1/forward, since a bulk request counts each address as one billed item regardless of how many dealers were in the list. That gave every dealer a fixed coordinate to measure distance from, rather than relying on the loose regional descriptions, "serves the tri-county area," that dealer listings had used before.
The distance defaults were the real change. Instead of a fixed search radius tuned for a city, the locator scaled its default radius up substantially for rural search areas, and let a customer widen it further with a single control rather than hitting a wall of "no dealers found" that suggested, wrongly, that the manufacturer simply had no presence nearby. A customer who allowed location detection got a starting point from /v1/ip, resolved from their IP address into approximate coordinates, and a customer who preferred to type in a town name or postal code had that entry geocoded the same way as the dealer list.
The manufacturer also used the geocoded dealer network for something beyond the customer-facing locator: internal coverage analysis, looking at where genuine gaps existed between dealers relative to where its equipment was actually being used, based on service and warranty registration addresses. That analysis, run once the whole dealer network had coordinates attached, informed where the company prioritized recruiting new dealers, a decision that had previously relied on regional sales reps' informal sense of where coverage felt thin.
None of this required treating rural and urban customers differently in the code itself. The same geocoding and distance calculation ran for every search. What changed was tuning, the default search radius and how the "no results" state was worded and handled, decisions that came from understanding the actual geography being served rather than from the underlying location technology, which worked identically regardless of how dense or sparse the area was.
Geocoding volume was almost entirely front-loaded into the initial dealer network batch, with a slow trickle after that as new dealers signed on, a workload that fit easily inside the free daily allowance included with the manufacturer's key. Customer-facing locator searches added a modest ongoing volume on top, also comfortably within the free tier for a company of this size, since dealer locator searches happen at a much lower frequency than, say, an everyday retail store finder would see.
Distance-based tools built with city assumptions baked in quietly fail rural users, and the fix is rarely a different technology, usually just different defaults applied to the same underlying calculation. Documentation for the endpoint is at /docs/forward-geocoding/.