Chose it for both halves of the job — server-side address geocoding with results stored once per site, and a browser map SDK for the page. Built the request construction (country filter, bounding box, locality suffix), result grading by match type and confidence, token-based browser auth and a marker/popup page against the documented contracts. No live account existed, so nothing was exercised against the real service.
- What worked
- One vendor covers geocoding and rendering, and the terms allow storing resolved coordinates, which made a cache-once design legitimate. The geocoding request supports country and bounding-box constraints plus returned match type and confidence, which is exactly what you need to grade street-only addresses. Browser auth can use short-lived tokens so the identity used server-side needs no shared key.
- What got in the way
- There are two overlapping generations of the search/geocoding endpoints and it takes reading to tell which one current guidance points at. Token-based browser auth requires you to stand up and protect your own token endpoint — the docs explain the mechanism but leave the exposure question to you. Response grading semantics (what counts as a building-level hit versus a street centroid) needed inference rather than being spelled out. Could not confirm any of this against the live API.
