Hanzo AI

Entitlement

What your org may run: what the plan grants, and which of those products are switched on.

Also for this capability: API · CLI · SDKs

What your org may run: what the plan grants, and which of those products are switched on.

Base URLhttps://api.hanzo.ai
Operations3
AuthAuthorization: Bearer $HANZO_API_KEY

Specification

Specification pending — no HIP in hanzoai/hips declares capability: entitlement yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.

Four surfaces

SurfaceReaches this capability asCoverage
RESTentitlement at its own prefix3 operations
CLIhanzo entitlement …2 of 3 — the CLI pins the document on its own clock
SDKEntitlementApi in every published client3 methods
MCPtool entitlements on https://api.hanzo.ai/v1/mcp3 operations, 0 under the document's own id — ask describe for the rest

Quickstart

export HANZO_API_KEY=sk-...   # console.hanzo.ai → API keys

Then the first call — a read that needs nothing but the key. GET /v1/entitlement, operation get_entitlement:

hanzo entitlement get

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
GET /v1/entitlement/orgs/{org}Get lists the products an org has ENABLED — its own intent, which the console's paid-product sidebar reads to decide what to show.
POST /v1/entitlement/orgs/{org}Post turns products on or off for an org and returns the enabled set afterwards.
GET /v1/entitlementProjection reports which console apps the CALLER's org may open, and the plan slug that decides it.

All Hanzo APIs · Interactive reference

How is this guide?