Create wallet

Provisions a new signing identity under one of the caller org's accounts and answers the stored wallet including its on-chain address.

POST /v1/wallet

Wallet → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/wallet`
Method	`POST`
Operation	`post_wallet`
Auth	`Authorization: Bearer $HANZO_API_KEY`

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.

Request

6 fields, body application/json (required).

Field	In	Type	Required	Description
`accountId`	body	string	—	AccountID is the account this wallet belongs to.
`agent`	body	string	—	Agent optionally narrows the wallet to one agent within the org.
`chain`	body	string	—	Chain is the EVM chain this wallet is for, as "eip155:<n>" or a bare decimal chain id.
`custody`	body	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).
`name`	body	string	—	Name is the wallet's display label.
`tier`	body	string	—	Tier is the MPC wallet tier: hot, warm, cold, gas, bridge, contract_admin, validator, quarantine or disaster_recovery.

Response

Status	Body	Meaning
`200`	wallet.Wallet	ok
`default`	problem-details	refused

200 body — 12 fields.

Field	In	Type	Always	Description
`accountId`	body	string	—
`address`	body	string	—	Address is the on-chain address.
`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 (int64)	—	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 m-of-n threshold key on the deployed ring, which differ by governance and not by signing mechanics), or "safe" (a Safe contract owned by an MPC key).
`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

CLI

SDK

HTTP

MCP

hanzo wallet create

.ts

.py

.go

.rs

.java

import { Configuration, WalletApi } from 'hanzoai';

const api = new WalletApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postWallet({ accountId: "<accountId>", agent: "<agent>" });

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(account_id="<accountId>", agent="<agent>")

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.WalletAPI.PostWallet(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::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(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.WalletApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new WalletApi(client).postWallet();

curl -X POST https://api.hanzo.ai/v1/wallet \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "accountId": "<accountId>",
       "agent": "<agent>"
     }'

MCP reaches wallet through the wallet tool, which names its 7 operations with its own verbs — this one among them, under a name only MCP 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"
         }
       }
     }'

Wallet API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCreate transactions NextGet chains