Hanzo
OpenapiVisor

Is an HONEST empty surface: Visor exposes no GPU alert inventory, so this…

Is an HONEST empty surface: Visor exposes no GPU alert inventory, so this returns [] rather than fabricating alerts.

GET /v1/visor/gpus/alerts

Addresshttps://api.hanzo.ai/v1/visor/gpus/alerts
MethodGET
OperationlistGpuAlerts
AuthAuthorization: Bearer $HANZO_API_KEY

Is an HONEST empty surface: Visor exposes no GPU alert inventory, so this returns [] rather than fabricating alerts. It stays a real, tenant-gated route so the console's alerts fetch resolves (200 [], not a 404) — an honest "no alerts", the same discipline the rest of the surface follows.

Request

GET /v1/visor/gpus/alerts takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200gpuAlertListok

200 body — 1 field.

FieldInTypeAlwaysDescription
alertsbodyobject[]Alerts is always empty, and typed as a raw list because Visor exposes no alert inventory for this surface to shape: there is nothing to describe until there is…

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


Visor API · All Hanzo APIs · Interactive reference

How is this guide?

On this page