Read the caller's entitlements and usage
What this caller’s plan allows, plus where they currently stand against the daily calculator budget. A client cannot correctly gate features without this: it is the answer to “may this user run a consumer calculation / open Matrix”, and the source of the “X of Y runs used today” affordance.
Refresh the usage block after each calculator run rather than counting locally — the cap is enforced server-side and a local count will drift across devices.
Guard the usage lookup — do not assume usage.calc_runs is present.
seats is the caller’s organisation against its user limit (entitlements["org.max_users"]): active users plus invites not yet accepted. Use it to show “N of M users” and to disable inviting at the limit; the server refuses an add past it with 409 seat_limit_reached either way. Re-read it after adding or removing a user. It is null for a caller with no organisation.
Authentication
JWT access token obtained from POST /api/v1/auth/login, or a finput_sk_... API token
Response
The caller's effective plan entitlements. Read a missing key as its safe default (false, or 0) rather than assuming the key set is frozen — plans add keys over time.
calc_runs is not guaranteed present — guard the lookup.
The caller's organisation against its user limit. null for a caller with no organisation.