put_v1_ingress_services_id

PutService creates or replaces one backend pool and hot-applies it. POST mints an id when the body omits one; PUT takes the id from the URL, which wins over any id in the body.

PutService creates or replaces one backend pool and hot-applies it. POST mints an id when the body omits one; PUT takes the id from the URL, which wins over any id in the body. A pool needs at least one backend and every backend URL must be http(s)://host[:port].


Tool	`put_v1_ingress_services_id`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	3
Operation	`PUT /v1/ingress/services/{id}`
Product	ingress

Arguments

Field	Type	Required	Default	Values	Description
`backends`	`Backend[]`	—	—	—	Backends are the upstream servers to balance across: 1..32 of them.
`id`	`string`	—	—	—	ID identifies the pool within the org: [A-Za-z0-9-_.], at most 128 chars. A create that omits it gets a generated one. Routes reference it by this id.
`passHostHeader`	`boolean`	—	—	—	PassHostHeader forwards the client's original Host header upstream instead of rewriting it to the backend's.

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

Object types

Backend is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.

Backend

Field	Type	Required	Default	Values	Description
`url`	`string`	—	—	—	URL is the upstream server, http(s)://host[:port].
`weight`	`integer`	—	—	—	Weight is this member's share of the round-robin; must be >= 0.

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": "put_v1_ingress_services_id",
         "arguments": {
           "backends": [
             {
               "url": "<url>",
               "weight": 0
             }
           ],
           "id": "<id>",
           "passHostHeader": false
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. backends[].weight and passHostHeader 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

Operation	Route	Product	Summary
`put_v1_ingress_services_id`	`PUT /v1/ingress/services/{id}`	ingress	Creates or replaces one backend pool and hot-applies it.

The same capability over plain HTTP is in the ingress 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).