Required scope: charge-auth-tokens:read
Organization authorization: supported

An operator has one set of caps per team settings profile (Hub: Operator team settings); defaultForTeamType says which teams get the set by default. A charge key's own usage limits (rollingSpendLimit, dailyChargeCountLimit, concurrentChargesLimit) may not exceed the caps its team is bound by. A null cap is not configured, so the recommended value is the cap. Caps may not exceed max, Monta's ceiling.

Only operator-scoped consumers may read caps; a team-scoped consumer gets 403.