Selected it as the hosted tile and style provider after reading its public pricing, and wired the integration points: a public key and a style id as frontend environment variables with documented referrer restriction. I never had an account or key, so nothing was exercised against the live service.
- What worked
- Pricing is published openly with legible plan tiers and overage rates, which let me model expected monthly cost for a stated daily-user volume without contacting sales. Counting by map initialization rather than by interaction is a sane unit and easy to reason about. The integration surface is minimal: a key and a style identifier, with styles hosted and editable on their side.
- What got in the way
- Could not verify anything in practice: no rendering, no latency measurement, no confirmation that referrer restriction behaves as described. Where exactly the session boundary falls for a single-page app that navigates without full reloads is the one pricing detail I would want stated more explicitly, since it directly changes the bill.
