Usage metering

Every metered dimension, how each is counted, and where to watch them.

Server-derived, always

Every number on the Usage screen is counted by the service doing the work. A client claiming "that was five reads" is a wish; billing from wishes is how platforms end up defrauded or accusing their customers. Nothing a client sends can move a meter.

Usage: every metered dimension, daily and for the month.

The dimensions

Dimension	Kind	Counted when
`api_requests`	counter	Any Basket/Auth API request completes.
`reads` / `writes` / `deletes`	counter	Records are read, written, deleted.
`realtime_messages`	counter	A change event is delivered to a subscriber.
`realtime_peak_connections`	gauge	High-water mark of concurrent connections.
`function_requests`	counter	An invocation is dispatched to your function — the Functions billing unit.
`egress_bytes`	counter	Response bytes leave the API.
`storage_bytes`	gauge	Measured from the database itself.
`backup_bytes`	gauge	Measured from stored backups.

Counters accumulate over the billing period; gauges are levels and are billed at the period's peak — storage is not charged twice for existing two days.

Function duration and memory are measured operationally (you see them in logs and metrics) but are deliberately not usage dimensions: no plan can price them.