Skip to main content

All entitlements for a customer

Useful for hydrating a settings/billing page without one request per feature:
There’s no allowed field here, unlike check() - this response is cached for 60s, and a stale “allowed” verdict on a QUOTA feature would be unsafe. Use remaining/overage_behavior to render state (a meter, a badge), and check()/consume() for the actual go/no-go decision on an action.

Usage records

Each record: { id, feature_key, value, period_start, period_end, status, ... } - one per feature per open billing period.