put_v1_pubsub_kv_bucket_key
Put sets one key to one value and returns the revision the write created.
Put sets one key to one value and returns the revision the write created. Writes are versioned: each put is a new revision and the bucket retains up to its History of them per key.
| Tool | put_v1_pubsub_kv_bucket_key |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | PUT /v1/pubsub/kv/{bucket}/{key} |
| Product | pubsub |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
bucket | string | — | — | — | Bucket is the bucket, from the path. |
key | string | — | — | — | Key is the key, from the path. |
value | string | — | — | — | Value is the value, carried verbatim as UTF-8 text (typically JSON). |
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_pubsub_kv_bucket_key",
"arguments": {
"bucket": "<bucket>",
"key": "<key>",
"value": "<value>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source 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_pubsub_kv_bucket_key | PUT /v1/pubsub/kv/{bucket}/{key} | pubsub | Put sets one key to one value and returns the revision the write created. |
The same capability over plain HTTP is in the pubsub 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?