What does the map call?

Origin requests count each API handler invocation, including failures and scheduled archive calls. Browser and CDN cache hits never reach that handler. Provider lookups count calls to the server fetch layer; Next.js may answer from its cache or revalidate in the background, so these are not exact upstream or billable counts. Uncached fetches request the network directly. Memory reuse counts AccuWeather requests resolved before fetch.

A single origin request can trigger several provider lookups; do not add these categories together. Failures mean HTTP errors or fetch exceptions, not invalid weather geometry. Empty tile HTTP 404s can be expected. Average time measures lookup/handler completion, not full browser load time.

Coverage: server weather feeds, imagery tiles, search, point forecasts, regional context, and API handlers. Direct browser Mapbox requests, legacy server-rendered brief pages, static files, database queries, client-side exposure calculations, provider-account traffic outside this app, and dashboard reads are excluded. Provider-side cache hits and billing must be reconciled with provider reports.

Hourly aggregates begin at deployment; no historical backfill. Writes are best-effort after responses and can be lost during storage/platform failures. No visitor identifiers, search queries, coordinates, credentials, or raw provider URLs are stored. Preview and production totals stay separate.