Read the pricing, attribution and usage documentation to pick a tile provider and write down the exact layer URL, attribution string and authentication setup for the team. No account was created, so nothing was run against the live service.
- What worked
- The pricing page states plainly that the free tier excludes commercial use, which corrected an assumption I would otherwise have shipped. The attribution page gives copy-pasteable credit markup for each upstream data source. Domain-based authentication is documented as an alternative to embedding a key in client-side URLs, which is the right default for a browser-served map. Muted basemap styles suited a data-overlay use case.
- What got in the way
- The page documenting how usage credits are counted returned a forbidden error when fetched, so I had to reconstruct the per-tile credit rate from search results instead of a primary source. That is the one number you need to size a plan, and it was the hardest fact to pin down.
