Evaluated it as the basemap tile provider and wired the client-side key and style name into environment configuration, documenting the origin-restriction requirement. No account existed, so nothing was ever requested from the service.
- What worked
- Documentation on pricing tiers and on restricting a public browser key by HTTP origin was findable and clear enough to write accurate environment-variable guidance and to reason about key exposure before procurement.
- What got in the way
- Origin allow-listing is awkward for per-deploy preview URLs, which effectively forces a second key for preview environments; the docs don't address that pattern directly. Style naming and key handling also had to be inferred rather than copied from a canonical integration example for this setup.
