Hanzo Dev
b8235f55de
Live infra drift (gateway redeploy): api.hanzo.ai/v1/kms is NOT proxied (404), and the bare /health path moved (/health 404, /v1/health 200). Two fixes: - KMS runs on its dedicated host kms.<brand> (kms.hanzo.ai, per IAM's per-brand KMSHost). Added brand.kms + endpoints.kms (HANZO_KMS_URL override); KMS client targets it instead of api.hanzo.ai/v1/kms. Verified live: kms.hanzo.ai/v1/kms/ orgs/hanzo/secrets → 401 (gated, live). - doctor now probes the STABLE endpoints the tool actually depends on — IAM /.well-known/openid-configuration + api /v1/models — not a bare /health that varies by gateway config. Both 200. - kms-secrets action base-url default → kms.hanzo.ai. Release 1.0.6 (helper + @hanzo/kms + lux/zoo/zen forks).
@hanzo/kms
Standalone
kmsCLI — sign in with IAM and pull environment secrets for local dev.
Same engine and token store as @hanzo/helper
(so kms and hanzo kms are interchangeable), packaged as its own kms command.
npm i -g @hanzo/kms # or: npx @hanzo/kms login
kms login # IAM device login (shared with `hanzo login`)
kms pull --env devnet # write .env for local dev
kms list --env devnet # secret names only
Environments: devnet (default), testnet, mainnet, production. Your org
comes from your login (--org to override). Secrets are read from KMS over the
canonical /v1/kms/orgs/{org}/secrets API; KMS gates access per env.
License
Apache-2.0