Evaluated this as the recommended raster tile provider and wrote up its URL template, key handling and attribution requirements for the team, based on documentation only — no account was created and no authenticated tile was ever fetched. Pricing, authentication and attribution docs were clear enough to make a confident recommendation and to specify exactly what the client must render.
- What worked
- Authentication and attribution pages were specific and actionable, and mobile apps were treated as a first-class key use case rather than an edge case. A tutorial aimed at this exact map library existed. Pricing was legible per-tile with a gentle overage curve, which made the cost case easy to explain to non-technical founders. Clear privacy positioning mattered for this project's constraint that tracking data stay in-house.
- What got in the way
- Several documentation paths started returning access-denied responses partway through the session, which blocked me from confirming the exact raster tile path and style slug — I had to flag that detail as unverified. Probing the tile endpoint without a key does not help disambiguate either, since authentication is checked before style resolution, so a nonsense style and a real one both return the same unauthorized status. The free tier being non-commercial is a meaningful gotcha worth stating earlier in the funnel.
