Frequently Asked Questions

Governed wallet operations infrastructure for stablecoin platforms, payment teams, treasury operators, and agentic workflows: one policy, approval, and evidence layer across WalletSuite MPC, on-premise HSM, and external signers.

Fireblocks is a full custody platform. WalletSuite is a flexible-signing operations layer: one policy, approval, and evidence model across WalletSuite MPC, on-premise HSM, and the external signers you already use.

Enterprise design partners run WalletSuite policy evaluation beside their existing rules before turning on enforcement. Every transaction is scored by both systems, compared, and recorded as evidence for migration and audit review.

Each customer, fund, or business unit gets its own wallets, policies, approvers, limits, and audit logs. Built for payment platforms, stablecoin platforms, RWA platforms, and multi-client treasury products.

Scripts prove a team can write rules. WalletSuite productizes them: multi-signer, multi-tenant, with approvals and evidence built in. Start in shadow mode and turn on enforcement once the decisions match.

Read, prepare, approve, sign, and broadcast are separate capabilities. Agents and jobs get only what they need, and risky transactions can require human approval before anything signs.

80+ today, including Ethereum, Solana, Bitcoin, Polygon, Arbitrum, Optimism, Base, BNB Chain, Avalanche, and Tron. One API surface and normalized data across all of them.

Yes. Take only what you need: balance queries, swaps, price feeds, transaction construction, or full governed signing. Every surface (MCP Server, SDK, REST API) shares the same primitives, so you can add more later.

AI agent wallets, payment processing, portfolio tracking, exchange backends, DeFi aggregators, and neobank on-ramps. Anything that reads balances, resolves tokens, or moves assets across chains.

The MCP Server runs in under 15 minutes: install, API key, agent token, first signed transaction. The SDK and REST API typically take up to two days end to end. Building the same in-house usually takes 12+ months and 5 to 7 separate vendor integrations.

No. The API and SDK absorb the chain-specific complexity: nonce management, fee estimation, gas optimization, UTXO selection, calldata encoding, token resolution, transaction simulation, webhook delivery, and multi-chain routing. Your team works with a standard REST API, and AI agents use the MCP Server with no blockchain code at all.

Yes. Reads work on any address, prepare returns the transaction for you to sign, and broadcast accepts any signed transaction. Your keys never touch WalletSuite.

You decide. Sign with WalletSuite MPC, an external signer, or keys in your own infrastructure. The Wallet API works the same either way.

The agent-facing surface of WalletSuite. It connects AI agents to wallet operations through the Model Context Protocol, an open standard by Anthropic, with zero infrastructure to operate: hosted MPC signing by default, on-premise HSM in regulated environments. Works with LangChain, CrewAI, Claude Agent SDK, or any MCP runtime.

It maps a symbol like USDC to the exact contract on a specific chain, verified against a curated registry. Ambiguous matches are flagged, which prevents misrouted transfers.

A scoped credential for an autonomous agent: one wallet, a capability cap, and a policy set with spend limits and expiry. The agent never sees keys, and revoking the token revokes the agent.

Your policy, approval, and audit logic is never locked to one signing backend. Choose WalletSuite MPC, on-premise HSM, or signed-payload workflows for external signers, and switch without rebuilding governance.

Every wallet operation becomes a structured receipt: transaction facts, policy version, matched rules, decision reason, approval trail, signer path, and hash-chain links for tamper-evident audit.

KYT and Travel Rule pre-checks run before broadcast and attach to the transaction's evidence record. They are available for enterprise design partner validation; production availability depends on provider, jurisdiction, and deployment scope.

Non-custodial by architecture. The default is 2-of-2 MPC: your share and ours must both sign, and neither party can move funds alone. Regulated institutions can use on-premise HSM, with keys in FIPS-validated hardware that never leave their environment. Either path emits unsigned payloads for any external signer you prefer.

Defense in depth: schema-validated inputs, band-scoped permissions, and policy evaluated before any signature. With 2-of-2 MPC WalletSuite cannot sign alone, secrets never pass through tool arguments or chat, and every operation lands in a SHA-256 hash-chained, tamper-evident audit trail.

Hosted MPC is the default: nothing to operate. Choose on-premise HSM when your regulator (CBUAE, DFSA, ADGM, VARA, or similar) requires hardware-backed keys in your environment, or you already run an HSM and want WalletSuite's policy, approvals, and evidence above it.