Summary
Standardize how publishers track meter_remaining decrements across API and browser contexts for metered access grant types.
Context
The meter_remaining claim is defined in Section 8.3.3 as a decrementing counter per content retrieval. However, there's no spec for how readers should report decrements, how to handle concurrent access, or how meter state syncs across API and browser contexts.
Responsibilities
- Define the decrement API for metered access
- Handle edge cases: concurrent access, offline reading, sync across multiple readers
- Ensure meter state doesn't violate user privacy
- Coordinate with the refresh token rotation flow to prevent count mismatches
Related
Spec sections: 8.3 Optional Claims — meter_remaining, 12.3 Refresh Token Rotation, Future Work
Summary
Standardize how publishers track
meter_remainingdecrements across API and browser contexts for metered access grant types.Context
The
meter_remainingclaim is defined in Section 8.3.3 as a decrementing counter per content retrieval. However, there's no spec for how readers should report decrements, how to handle concurrent access, or how meter state syncs across API and browser contexts.Responsibilities
Related
Spec sections: 8.3 Optional Claims — meter_remaining, 12.3 Refresh Token Rotation, Future Work