Entitlement

Displays Maptiles is gated by two feature keys:

• oohdisplays.displays.inventory_tiles - the bundled entitlement that covers Displays inventory geometry (viewsheds, exposure paths, and gates).

• oohdisplays.displays.face_point_tiles - the entitlement that covers the display face points layer.

• 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 Displays layer (all six: faces, viewsheds, both path layers, both gate layers) with no per-layer scoping.

Cost model

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 displays_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 Displays Maptiles group in the console catalog; grant usage reporting (usage_30d) is a placeholder today and lands in a follow-up.

Related reading

• Discovering Displays tilesets - what the catalog tells you before you spend anything
• Minting a Displays tile grant - the free control-plane operations