post_v1_wallets
Provisions a new signing identity under one of the caller org's accounts and answers the stored wallet including its on-chain address.
Provisions a new signing identity under one of the caller org's accounts and answers the stored wallet including its on-chain address. The custody backend generates the key material — a KMS-sealed secp256k1 key, an MPC threshold key on the ring, or a Safe smart wallet owned by one — and the HANDLE to it is kept server-side and never returned. A custody kind the deployment has not wired fails CLOSED with 503: a signature is never fabricated. The wallet is scoped to the org, the caller's ambient project, and optionally an agent and the named account; those narrowings are what its key ref is derived from, so each must be a url-safe segment.
| Tool | post_v1_wallets |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 6 |
| Operation | POST /v1/wallets |
| Product | wallets |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
accountId | string | — | — | AccountID is the account this wallet belongs to. Required, and it must be an account of the caller's own org — an unknown one is a 404. |
agent | string | — | — | Agent optionally narrows the wallet to one agent within the org. It becomes a segment of the key ref, so it must be a url-safe segment with no slash. |
chain | string | — | — | Chain is the EVM chain this wallet is for, as "eip155:<n>" or a bare decimal chain id. Optional; a Safe defaults to the Hanzo L1 (36963). |
custody | string | — | — | Custody selects the signing backend: "kms" (in-process, always available), "mpc" or "treasury" (the deployed MPC ring), or "safe" (a Safe smart wallet owned by an MPC key). Empty uses the deployment's default. A backend that is not configured fails CLOSED with 503 rather than fabricating a signature. |
name | string | — | — | Name is the wallet's display label. Optional. |
tier | string | — | — | Tier is the MPC wallet tier: hot, warm, cold, gas, bridge, contract_admin, validator, quarantine or disaster_recovery. Empty defaults to hot. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
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_wallets",
"arguments": {
"accountId": "<accountId>",
"agent": "<agent>",
"chain": "<chain>",
"custody": "<custody>",
"name": "<name>",
"tier": "<tier>"
}
}
}'Values are placeholders derived from each field's declared type. 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 |
|---|---|---|---|
cloud_post_v1_wallets | POST /v1/wallets | wallets | Provisions a new signing identity under one of the caller org's accounts and answers the s |
The same capability over plain HTTP is in the wallets API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?