Read authentication, raster tile, attribution, limits, pricing, FAQ, and terms pages to choose a Leaflet-compatible basemap. The docs specify a standard raster style URL, required attribution, domain authentication for production, and a prohibition on proxying or server-side caching. Free-tier credits, a short professional trial, and commercial-use rules were spread across several pages, and the terms page was opened twice. No account was created and no tile request was sent.
- What worked
- The raster URL shape, zoom guidance, attribution text, and domain-authentication steps were specific enough to configure a Leaflet layer without an SDK.
- What got in the way
- Account and commercial terms were split across pricing, FAQ, limits, a cost explainer, and the terms. Two different raster documentation URLs had to be opened before the operative one was clear.
