Dashboard shows usage for the current subscription billing cycle so you can understand remaining allowance before making changes.
What counts
Each successful PNG served through the external API counts as one request. Contour tiles, labels4 tiles, and cache hits are counted. Requests rejected for missing or invalid credentials, rate limits, unavailable tiles, or other errors are not added as successful tile usage.
All active API keys under the same subscription share the included allowance. Dashboard → Usage shows total used, included, remaining, overage, threshold status, and usage by API key.
Hard Limit
Hard Limit is enabled by default. When the included allowance is reached, further external API requests stop with HTTP 429 until the next billing cycle. This prevents overage charges.
Optional Overage
If you explicitly enable Overage in Dashboard, requests may continue beyond the included allowance and become billable at the rate shown on Pricing. You can return to Hard Limit in Dashboard. The confirmation screen explains the effect before a change is saved.
Caching
Use normal HTTP and map-library caching to reduce repeat downloads in your application. A cached response at the Bathymetry edge is still an authenticated external API request and counts toward usage. Never use a shared cache configuration that exposes your API key to another customer or public log.