Licensing and cost for Viewcast maptiles

The entitlement that unlocks Viewcast vector tiles, how it is granted, and what tile delivery costs.

Entitlement

Viewcast Maptiles is gated by the feature key viewcast.profiles.inventory_tiles, the same bundled entitlement that covers Viewcast inventory geometry (viewsheds, exposure paths, and gates).

  • Grant required. Unlicensed organizations get 403 FEATURE_NOT_LICENSED when minting a grant. Contact sales for access.
  • Metered billing rail required. The organization must be metered; credit-pack-only orgs get 403 TILE_GRANTS_REQUIRE_METERED.
  • One entitlement, all layers. A single entitlement covers every published Viewcast layer (all five: viewsheds, both path layers, both gate layers) with no per-layer scoping.

Cost model

OperationCredits
Discovery (GET /v2/viewcast/tiles/tilesets)0 (public, free)
Grant CRUD and TileJSON (control plane)0
Tile bytes (GET .../viewcast/tiles/{layer}/{z}/{x}/{y}.mvt)1 credit per 1000 tiles served

At the metered credit price of $0.05 per credit, tile delivery works out to $0.05 per 1000 tiles. Tile fetches accrue against your billing account under op id viewcast_tiles_fetch with a meter divisor of 1000. Empty tiles (a z/x/y coordinate with no features) return HTTP 204; responses may be gzip-encoded and clients must honor Content-Encoding.

A quick cost sanity model: a map session that pulls 60 tiles per view, serving 50,000 map views a month, fetches about 3,000,000 tiles, or 3,000 credits, or about $150.

Console visibility

Your organization admin can see the entitlement state and mint/revoke grants from the developer dashboard in the console. Grants minted through the API also appear there under the Viewcast Maptiles group in the console catalog; grant usage reporting (usage_30d) is a placeholder today and lands in a follow-up.

Related reading


Did this page help you?