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 school catchment area checker
Every spring, a school district's enrollment office fielded the same question over and over from families who had just moved, were considering moving, or simply were not sure: which school does my address belong to. Answering it by hand meant a staff member looking up a street address against a set of catchment area boundaries maintained as maps and lists, a process that took a few minutes per family and did not scale well during the weeks leading up to enrollment deadlines when the volume of questions spiked hardest.
The district built a self-service checker to handle the common case directly. A family typed in their address, which the tool sent to /v1/forward to get back a location match with coordinates, since the district's catchment boundaries were maintained as geographic areas that needed a coordinate to test against, not a text address that could not be directly compared to a boundary shape. Once an address resolved to a coordinate, checking which catchment area contained that point was a straightforward geometry test run by the district's own system, comparing the point against each boundary polygon on file.
For addresses that resolved with high confidence and landed clearly inside one boundary, the tool gave an immediate answer, naming the assigned school directly. For addresses that resolved with lower confidence or fell very close to a boundary line, common for newer developments or addresses near the edge of two zones, the tool flagged the result as needing confirmation from the enrollment office rather than stating a school name with more certainty than the underlying match actually supported, since a wrong answer on something as consequential as school assignment was a much bigger problem than an occasional "please contact us to confirm" message.
This distinction mattered enough that the district built it in deliberately rather than as an afterthought. A geocoding match reflects how confidently an address resolved, and treating every match as equally certain would have produced confidently wrong answers for exactly the addresses most likely to be genuinely ambiguous, the ones sitting right at a boundary edge where getting it wrong caused the most disruption for a family relying on the answer.
The tool cut enrollment office call volume substantially during the weeks it mattered most, freeing staff to spend time on the harder cases, boundary-edge addresses, families with unusual circumstances, rather than repeating the same basic lookup hundreds of times over. The district also used the same underlying geocoding to occasionally audit its own catchment maps, checking whether addresses near a boundary that families had disputed were, in fact, correctly assigned according to the district's own official boundary data, catching a small number of genuine mapping errors in the process.
Usage was seasonal and concentrated, spiking hard in the weeks before enrollment deadlines and quiet the rest of the year, a pattern the free daily allowance handled well during quiet periods, with prepaid credit covering the enrollment season spike without the district needing to commit to a plan sized for its busiest weeks year round.
Documentation for both endpoints is at /docs/forward-geocoding/ and /docs/postal-code-lookup/.