Hanzo
CLILicensing

Licensing

11 `hanzo` commands for Licensing, each calling one operation on api.hanzo.ai.

Package licensing is what an org has bought and may run: signed licenses to issue, verify and revoke, and the releases they unlock.

11 commands · API reference →

CommandCallsWhat it does
hanzo licensing download get <release>GET /v1/licensing/download/{release}Download resolves a release to its artifact, gated on a valid license.
hanzo licensing fingerprintPOST /v1/licensing/fingerprintFingerprint turns raw device signals into the opaque value that binds a license to one machine.
hanzo licensing healthzGET /v1/licensing/healthzHealth reports which signer this deployment mints with, and in which env.
hanzo licensing issue --product <product>POST /v1/licensing/issueIssue mints a signed license token for a product the caller's org already pays for.
hanzo licensing jwksGET /v1/licensing/jwksPubkey publishes the Ed25519 PUBLIC verification key, at both /pubkey and /jwks.
hanzo licensing pubkeyGET /v1/licensing/pubkeyPubkey publishes the Ed25519 PUBLIC verification key, at both /pubkey and /jwks.
hanzo licensing releases get <release>GET /v1/licensing/releases/{release}Reads one release's metadata: its product, version, platform and the cosign material a client verifies the binary…
hanzo licensing releases listGET /v1/licensing/releasesLists the signed binary releases this deployment can serve.
hanzo licensing releases createPOST /v1/licensing/releasesPublishes a signed binary release, answering 201 Created.
hanzo licensing revoke --scope <scope> --value <value>POST /v1/licensing/revokeRevoke turns off tokens that have already been issued.
hanzo licensing verify --token <token>POST /v1/licensing/verifyVerify checks a license token online: signature, schema, expiry, app_id and the revocation list.

How is this guide?