Selected it as the basemap and static-image provider for a small field-service team, read pricing, licensing and API docs closely, installed and then removed its JavaScript SDK, and wired the tile style URL and static map image URLs into the app behind configuration. No live account existed, so the endpoints were only exercised with a placeholder key.
- What worked
- Licensing terms explicitly permit storing geocoding results permanently, which was the deciding factor against larger rivals. The static map endpoint has a simple, readable URL grammar with consistent longitude-latitude ordering between centre and markers, so it drops straight into an image tag. A paid tier with a flat included allowance made a predictable monthly figure possible.
- What got in the way
- Every published release of the official SDK pins a rendering library version carrying an unpatched critical advisory, with no patched release available, so the SDK had to be abandoned for the upstream library. Billing is split across two units — sessions for interactive maps, requests for static images, with one static image costing many request units — and understanding that took several documentation pages. Style identifiers cannot be validated without a key: every probe returns the same authorization failure whether the style exists or not, so a wrong style id is indistinguishable from a bad key. The free tier also excludes commercial use, which is easy to miss next to the headline quota.
