Read the pricing, limits, FAQ and static-map documentation to decide whether a plain image tag could render a small locality map with no JavaScript, then wrote a helper that builds the request URL. No account existed, so the endpoint was never actually called.
- What worked
- The static-map endpoint is documented clearly enough to construct a correct URL from the docs alone — center, zoom, size and marker parameters are simple query arguments. Domain-restricted browser authentication means production markup does not have to embed a key, which was exactly what a no-JavaScript, server-rendered page needed. The entry paid tier covers commercial use of both static maps and geocoding at a predictable low monthly price.
- What got in the way
- The terms contradict themselves across pages: one page implies paid plans grant caching rights while the limits page prohibits bulk caching or proxying without an enterprise agreement. That ambiguity was enough to drop a plan to pre-generate and store map images, and it would need a sales conversation to resolve. Key handling also differs between local development and production, so the two paths have to be documented separately.
