Get releases

Reads one release's metadata: its product, version, platform and the cosign material a client verifies the binary against.

GET /v1/licensing/releases/{release}

Addresshttps://api.hanzo.ai/v1/licensing/releases/{release}
MethodGET
Operationget_licensing_releases_by_release
AuthAuthorization: Bearer $HANZO_API_KEY

Reads one release's metadata: its product, version, platform and the cosign material a client verifies the binary against.

An unknown id is 404. Like the list, this is metadata only — the bytes are behind the license-gated download.

Request

1 field.

FieldInTypeRequiredDescription
releasepathstringyes

Response

StatusBodyMeaning
200licensing.Releaseok
defaultproblem-detailsrefused

200 body — 12 fields.

FieldInTypeAlwaysDescription
app_idbodystring—AppID scopes the release to an app build ("hanzo" | "lux" | "zoo").
artifact_refbodystring—ArtifactRef is where the binary lives (object-store key / OCI ref / path).
cosign_certbodystring—CosignCert is the cosign/Fulcio cert (keyless) or public key ref used to verify CosignSignature.
cosign_signaturebodystring—CosignSignature is the base64 cosign signature over the artifact digest.
created_atbodyinteger (int64)—
idbodystring—ID is the release identifier, e.g. "engine-rocm-0.4.2-linux-amd64".
min_featuresbodystring[]—MinFeatures, when set, are features the license must include to download.
platformbodystring—Platform is "<os>/<arch>", e.g. "linux/amd64".
productbodystring—Product is the licensed product this artifact belongs to (commerce SKU): "engine" for every one of those builds.
sha256bodystring—SHA256 is the hex digest of the artifact (integrity + cosign subject).
versionbodystring—Version is the semantic version of the binary.
yankedbodyboolean—Yanked marks a pulled release (download refused; tokens may be revoked release-scoped too).

Failure carries the platform error shape — see Errors.

Examples

hanzo licensing releases get <release>
import { Configuration, LicensingApi } from 'hanzoai';

const api = new LicensingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getLicensingReleasesByRelease({ release: 'release' });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import LicensingApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = LicensingApi(client).get_licensing_releases_by_release(release='release')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.LicensingAPI.GetLicensingReleasesByRelease(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, licensing_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = licensing_api::get_licensing_releases_by_release(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.LicensingApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new LicensingApi(client).getLicensingReleasesByRelease();
curl https://api.hanzo.ai/v1/licensing/releases/<release> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches licensing through the licensing tool, which names its 9 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_licensing_download"
         }
       }
     }'

Licensing API · All Hanzo APIs · Interactive reference

Was this page useful?