post_v1_balancers
CreateLoadBalancer creates a load balancer in the caller's org namespace and answers 201 with it.
CreateLoadBalancer creates a load balancer in the caller's org namespace and answers 201 with it. The physical DigitalOcean name is derived server-side from the validated org; a name that already exists there is a 409. Omitting forwarding rules yields a usable HTTP 80→80 load balancer rather than a 422.
| Tool | post_v1_balancers |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 5 |
| Operation | POST /v1/balancers |
| Product | balancers |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
forwarding_rules | fwdRule[] | — | — | — | ForwardingRules are the listen→backend port mappings. Empty defaults to plain HTTP 80→80, the same default DigitalOcean's own console applies. |
name | string | — | — | — | Name is the FRIENDLY name, a DNS-safe slug of at most 40 characters. The physical DigitalOcean name is derived from it and the caller's org. |
region | string | — | — | — | Region is the DigitalOcean region slug (nyc3, sfo3, …). Required. |
size | string | — | — | — | Size is the DigitalOcean size slug. Empty takes DO's default. |
type | string | — | — | — | Type is the DigitalOcean load-balancer type. Empty takes DO's default (REGIONAL). |
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
fwdRule is an object this tool's fields are made of, declared inside the tool's own schema and enumerated in full below.
fwdRule
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
entry_port | integer | — | — | — | EntryPort is the port the load balancer listens on. |
entry_protocol | string | — | — | — | EntryProtocol is the protocol the load balancer listens with (http, https, tcp). |
target_port | integer | — | — | — | TargetPort is the backend port traffic is forwarded to. |
target_protocol | string | — | — | — | TargetProtocol is the protocol used to reach the backend droplets. |
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_balancers",
"arguments": {
"forwarding_rules": [
{
"entry_port": 0,
"entry_protocol": "<entry_protocol>",
"target_port": 0,
"target_protocol": "<target_protocol>"
}
],
"name": "<name>",
"region": "<region>",
"size": "<size>",
"type": "<type>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. forwarding_rules[].entry_port and forwarding_rules[].target_port 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 |
|---|---|---|---|
post_v1_balancers | POST /v1/balancers | balancers | Creates a load balancer in the caller's org namespace and answers 201 with it. |
The same capability over plain HTTP is in the balancers 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).
How is this guide?