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 franchise territory planner
Selling a new franchise territory that overlaps too closely with an existing one is the kind of mistake that generates lawsuits, not just awkward conversations, and a franchisor expanding into a new region needed to be certain, with actual data rather than a rough sense from a paper map, exactly where its existing locations sat relative to any new territory it was about to offer.
The franchisor's location records existed as text addresses in its franchise management system, useful for mailing invoices and useless for measuring distance or drawing a boundary. Turning that list into something a territory planning process could actually use started with geocoding the entire existing network in a single batch through /v1/forward, since a bulk request counts each address as one billed item, giving every location a fixed coordinate rather than a name and street that could not be directly compared to a proposed new boundary.
With coordinates for the full existing network, drawing a new territory became a measurable exercise: a proposed boundary for a new franchisee could be checked directly against the coordinates of every nearby existing location, confirming a minimum distance was respected or that a proposed boundary did not accidentally include a competing existing territory within it, a check the franchisor's legal and development team could run before ever presenting a territory map to a prospective franchisee, catching a conflict on paper rather than after a contract was signed.
The franchisor also used the geocoded network for straightforward expansion analysis, looking at which regions had no existing locations within a reasonable distance of any population center worth serving, a gap analysis that had previously relied on development staff's general familiarity with the map rather than an actual measured distance from real coordinates. That analysis surfaced a couple of genuinely underserved regions the development team had not prioritized before, simply because nobody had looked at the existing network's coverage gaps with real distance data rather than an impression of the map.
This was largely a one-time project rather than an ongoing integration, similar in shape to a sales territory mapping exercise: the existing network got geocoded once, in a batch that fit comfortably inside the free daily allowance for a franchise system of moderate size, and new locations were geocoded individually as they came online after that, a small and predictable ongoing volume that never approached needing prepaid credit for a franchisor adding a modest number of new locations per year.
The value of the project showed up specifically in the confidence it gave the legal and development team before finalizing a new territory, since a proposed boundary that had been checked against real distances to real existing locations was a much stronger position to stand behind than one drawn by hand and reviewed by eye, particularly if a territory dispute with an existing franchisee ever needed to be resolved and the company wanted to point to a documented, measured process rather than a subjective judgment call.
Documentation for the endpoint, including batch request formatting, is at /docs/forward-geocoding/.