post_v1_agents_targets

RegisterTarget registers a machine as an agent target, or re-links one that is already registered. Re-linking is idempotent and keyed on org+host+owner, so a machine that reconnects refreshes its own row rather than piling up duplicates; it answers 200, while a first registration answers 201.

Arguments

tools/list declares a type for each field and nothing further. A — means neither the door nor that operation constrains the field.

Object types

GPU, Metrics and Spec are objects this tool's fields are made of. Each is declared inside the tool's own schema, and each is enumerated in full below.

GPU

Metrics

Spec

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "post_v1_agents_targets",
         "arguments": {
           "capacity": "<capacity>",
           "host": "<host>",
           "kind": "<kind>",
           "label": "<label>",
           "metrics": {
             "at": 0,
             "gpuUtil": 0,
             "load1": 0,
             "load15": 0,
             "load5": 0,
             "memFree": 0,
             "memUsed": 0
           },
           "spec": {
             "arch": "<arch>",
             "cpus": 0,
             "gpus": [
               "<gpus>"
             ],
             "memory": 0,
             "os": "<os>"
           },
           "status": "<status>"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. metrics.at, metrics.gpuUtil, metrics.load1, metrics.load15, metrics.load5, metrics.memFree, metrics.memUsed, spec.cpus and spec.memory hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are this page's, not the API's. Neither the door nor the operation declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.

All 755 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).