Rolls one wallet's signing material through its own custody backend and answers…
Rolls one wallet's signing material through its own custody backend and answers the wallet with whatever address that produced.
POST /v1/wallet/{id}/keys
| Address | https://api.hanzo.ai/v1/wallet/{id}/keys |
| Method | POST |
| Operation | post_wallet_by_id_keys |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Rolls one wallet's signing material through its own custody backend and answers the wallet with whatever address that produced. For KMS custody a fresh secp256k1 key is generated and sealed, which CHANGES the address — funds and approvals at the old address do not move. For a Safe the address is counterfactual and the owner shares are ring-managed, so rotation is a no-op and the address is unchanged. A backend that is not configured fails closed with 503 rather than leaving the wallet half-rotated.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | yes |
Response
| Status | Body | Meaning |
|---|---|---|
200 | Wallet | ok |
200 body — 12 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
accountId | body | string | — | |
address | body | string | — | Address is the on-chain address. For kms/mpc/treasury it is the EOA a signature from this wallet recovers to; for safe it is the CREATE2 address of the Safe… |
agent | body | string | — | |
chain | body | string | — | Chain is the EVM chain the wallet is bound to, CAIP-2 "eip155:<n>" or a bare decimal chain id. |
createdAt | body | integer | — | CreatedAt is when the wallet was provisioned, Unix seconds. |
custody | body | string | — | Custody is the backend holding the signing material, fixed at creation: "kms" (a secp256k1 key sealed under KMS and opened in-process), "mpc" or "treasury" (an… |
financeAccount | body | string | — | FinanceAccount is the finance ledger account bound to this wallet — the lookup that turns a ledger account back into an on-chain signer. |
id | body | string | — | ID is the wallet id, minted by the server as "wal_" + 24 hex. |
name | body | string | — | Name is the display label given at creation. |
org | body | string | — | |
project | body | string | — | |
tier | body | string | — | Tier is the wallet tier the ring keys its TierPolicy on: hot, warm, cold, gas, bridge, contract_admin, validator, quarantine or disaster_recovery. |
Failure carries the platform error shape — see Errors.
Examples
hanzo wallets keys <id>import { Configuration, WalletApi } from 'hanzoai';
const api = new WalletApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postWalletByIdKeys({ id: 'id' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import WalletApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = WalletApi(client).post_wallet_by_id_keys(id='id')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.WalletAPI.PostWalletByIdKeys(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, wallet_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = wallet_api::post_wallet_by_id_keys(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.WalletApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new WalletApi(client).postWalletByIdKeys();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X POST https://api.hanzo.ai/v1/wallet/<id>/keys \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches wallet through the wallets tool, which names its 7 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_wallets"
}
}
}'How is this guide?