Included volumes, what is left of them, and the overage prices

GET 
/api/v1/billing/metering

What continuous work this month costs, before the customer commits.

Any org member, like the billing summary the header chip reads: the strings it feeds sit on capability toggles a member can see, and hiding the price from the person about to turn something on is how a limit ends up discovered on an invoice.

Prices come from the server's runtime tunables, never a client constant one price in two places always drifts. Included volumes come from resolve_entitlements, so a negotiated allowance shows the negotiated number rather than the tier default.

• Scope required: billing:read.

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.