Wallets

Prepare, inspect, govern, and reconcile workspace- and network-bound MPC custody wallets, approved destinations, policies, ceremonies, transfers, and asset portfolios without exposing key or credential material.

BUSINESS CASES

Where this module fits

wallet onboarding
portfolio and balance review
network-aware token discovery and enablement
custody lifecycle governance

PRIMARY CONSUMERS

Who integrates it

treasury operators
custody integrations
wallet agents

PREREQUISITES

What must exist first

wallet scopes for the requested action
an active workspace and supported network
a registered public request-signing key and fresh purpose-bound step-up for sensitive mutations
approved custody, participant-domain, threshold, recovery, screening, and evidence policies

RECOMMENDED WORKFLOW

Compose the module safely.

01
select the authenticated workspace, network, purpose, and approved custody policy
02
read the authoritative token-import-network catalog before inspecting or enabling a contract asset
03
prepare and complete distinct enrollment, attestation, activation, destination-approval, estimate, intent, signing, submission, and reconciliation stages
04
read current wallet, policy, approved-address, balance, ceremony, transfer, and evidence state before every governed action
05
reconcile ambiguous responses from authoritative state before retrying an equivalent idempotent request

AGENT INTEGRATION

Machine-use boundaries

Never send entropy, mnemonic words, seeds, private keys, MPC shares, signing nonces, passwords, password hashes, encrypted password blobs, banking credentials, or reusable custody secrets.
Use opaque owner-safe wallet, destination, funding, and policy references; the bearer supplies workspace and owner boundaries.
Treat a contract asset as the pair (network_id, contract_address). Require the user or integration to select a network returned by /api/v2/wallets/token-import-networks; never guess, silently default, or rewrite the network or address.
Catalog visibility and custom-token enablement are portfolio metadata only. They do not create or activate a chain wallet and grant no enrollment, signing, withdrawal, broadcast, trading, or value authority.
Preparation, enrollment, attestation, activation, approval, estimate, intent, customer authorization, reservation, threshold signing, submission, confirmation, settlement, reversal, and recovery are distinct states; none implies another.
Preserve quantities, balances, amounts, and fees as exact decimal strings and bind mutations to last-read versions and commitments.
Treat legacy /api/v2/wallet/* mutations as bodyless 501 migration markers and verify every canonical replacement in live OpenAPI before calling it.

Register only production-listed routes as executable tools, and re-fetch the deployed OpenAPI before generating or sending a request. Source-ready routes awaiting deployment are preparation references; planned contracts are non-executable.

MODULE CONTRACTS

Every mapped endpoint

Each operation states whether its request shape is authoritative in OpenAPI, reviewed as a planning profile, or intentionally left as an outline pending an owner schema.