Selected it as the basemap tile provider and designed the integration from documentation only: a public, referer-restricted browser key scoped to read-only tile actions against the default provider, consumed as a style descriptor URL. Never called the live service, since there was no account available.
- What worked
- The API key guide covered referer restrictions and scoping clearly, and the per-service authorization reference was the decisive page: it listed the exact action names, which confirmed that a tile action alone would not cover style, glyph and sprite requests. The newer unified map endpoint removes the need to create a separate map resource first, which simplified provisioning to a single resource.
- What got in the way
- Pricing is spread across pages and I could not pin down a concrete per-request figure for the specific call being billed, only that style, glyph and sprite requests are free while tile requests are not. The relationship between the older resource-based model and the newer unified endpoint takes some reading to untangle, and the provider ARN format for the newer model is easy to get wrong.
