put_v1_ingress_routes_id

PutRoute creates or replaces one routing rule and hot-applies the new table — there is no config file and no restart.

PutRoute creates or replaces one routing rule and hot-applies the new table — there is no config file and no restart. 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 route's host is a GLOBALLY unique DNS claim: a host another org's route already holds is refused 409, so no tenant can hijack another's hostname.


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

Arguments

Field	Type	Required	Default	Values	Description
`host`	`string`	—	—	—	Host is the exact hostname this route matches, lowercased with any trailing dot stripped. It is a GLOBALLY unique claim — one route across the whole edge may hold a host, so no tenant can hijack another's.
`id`	`string`	—	—	—	ID identifies the route within the org: [A-Za-z0-9-_.], at most 128 chars. A create that omits it gets a generated one.
`middlewares`	`string[]`	—	—	—	Middlewares are the ids of the edge transforms to apply, in this order, before the request reaches the service. At most 16.
`pathPrefix`	`string`	—	—	—	PathPrefix narrows the match to requests under this path; it must start with "/". Empty matches every path on the host.
`priority`	`integer`	—	—	—	Priority orders routes that share a host: higher wins, and equal priorities fall back to the longer PathPrefix.
`service`	`string`	—	—	—	Service is the id of the backend pool this route dispatches to. A route naming a service that does not exist is skipped at compile, not served.
`tls`	`boolean`	—	—	—	TLS asks the edge to terminate TLS for Host with an ACME-managed certificate.

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.

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_routes_id",
         "arguments": {
           "host": "<host>",
           "id": "<id>",
           "middlewares": [
             "<middlewares>"
           ],
           "pathPrefix": "<pathPrefix>",
           "priority": 0,
           "service": "<service>",
           "tls": false
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. priority and tls 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_routes_id`	`PUT /v1/ingress/routes/{id}`	ingress	Creates or replaces one routing rule and hot-applies the new table — there is no config…

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).

put_v1_ingress_routes_id

Arguments

Call it

The operation behind it

On this page