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.
Adding local business hours to a franchise website
A franchise with locations across several time zones had a website problem nobody had thought to fix: the central "hours" section on every location page showed the same schedule, written once by someone at headquarters and copied to every store, regardless of which time zone that particular store actually operated in. A location on the west side of the franchise's territory closing at what its own clock read as 9 PM looked, on the website, like it closed three hours earlier than it actually did, because the hours had been written against headquarters time and never adjusted per location.
Fixing it required attaching a real time zone to each location rather than treating "hours" as one shared piece of content. For every franchise location's address, the company resolved coordinates through /v1/forward and passed those coordinates to /v1/timezone, which returns the IANA time zone name for that exact point. Storing the name rather than a fixed offset meant the hours display stayed correct automatically through daylight saving changes, without anyone at headquarters needing to remember to update anything twice a year.
With each location's own time zone on file, the website could finally do the thing it should have been doing from the start: show a visitor whether a specific location was open right now, calculated correctly against that location's own clock, not the visitor's clock and not headquarters' clock. A visitor browsing from across the country looking at a location page for a store on the opposite coast saw an accurate "open now" or "closed, opens at 8 AM" reflecting that store's actual local time, which is the only version of that information that is actually useful to someone about to drive there.
The company layered the visitor's own location on top of this for the location finder specifically. /v1/ip resolved a visiting customer's approximate coordinates, which fed into the same distance ranking used by other locator tools, so a customer searching for the nearest open location got results that accounted for both distance and whether that particular location was actually open at the moment of searching, rather than a distance-sorted list that included several currently closed stores mixed in with open ones.
This was a small, mostly invisible fix in the sense that a website visitor would never think to credit "correct time zone handling" for anything, they would simply notice, or more likely not notice, that the hours shown matched reality. That is generally the sign of a fix worth making: nobody praises it, but everybody who would have been confused by the old version simply is not confused anymore.
Geocoding ran once per location as part of a one-time setup, a small batch given how many locations most franchises operate, well within the free daily allowance. Time zone lookups for the visitor-facing "open now" feature added a light ongoing volume tied to location finder traffic, also comfortably inside the free tier for a franchise of moderate size, with prepaid credit available if a national marketing campaign drove an unusual spike in location searches.
Documentation for both endpoints is at /docs/forward-geocoding/ and /docs/timezone-lookup/.