Hanzo
OpenapiVisor

Launch a metered machine for your org, or price one first with dryRun

Provisions a machine owned by the caller's org and answers 201 with the machine.

POST /v1/visor/machines

Addresshttps://api.hanzo.ai/v1/visor/machines
MethodPOST
Operationpost_visor_machines
AuthAuthorization: Bearer $HANZO_API_KEY

Provisions a machine owned by the caller's org and answers 201 with the machine. Send dryRun: true to get a PRICE QUOTE instead: 200 with the upstream quote passed through verbatim, nothing launched and nothing spent. Two response shapes on one address is the rule to know, and it is why this is not a typed op.

Metering is not this plane's: the launch fronts the compute provider's resell endpoint, which owns the balance gate and the per-hour meter, and cloud only forwards the tenant. Ownership is the validated principal's org and is never read from the body, so a launch always lands in the caller's OWN tenant and the machine it creates is only ever visible to that tenant. Fails closed: a validated principal is required (403 without one) and size (or its instanceType alias) is required (400).

Request

The document declares no body for POST /v1/visor/machines. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_visor_machines, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — 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