Entitlements
Package entitlements is what your org may run: what the plan grants, and which of those products are switched on.
Package entitlements is what your org may run: what the plan grants, and which of those products are switched on.
| Base URL | https://api.hanzo.ai |
| Operations | 1 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
entitlements
Projection reports which console apps the CALLER's org may open, and the plan slug that decides it.
GET /v1/entitlements
Projection reports which console apps the CALLER's org may open, and the plan slug that decides it. It is the READ side of the unified paywall: the org's plan tier resolved from commerce, which is a different authority from the enablement store behind GET /v1/orgs/{org}/entitlements (that one is the org's own on/off intent).
It fails SAFE-TO-LOCKED, never 500: an unvalidated principal is a 403, but a commerce outage reports every app locked at 200 rather than breaking the shell. The ENFORCEMENT path still fails open, so functionality survives the same outage even while the UI conservatively shows locked.
How is this guide?