Question 1

What is WalletSuite?

Accepted Answer

WalletSuite is wallet infrastructure for Web3 companies and AI agents. We provide an SDK, REST API, and MCP Server that give your product on-chain access across 79+ blockchains: balance queries, transaction construction, token resolution, and price lookups.

Question 2

How many blockchains does WalletSuite support?

Accepted Answer

79+ blockchains today, including Ethereum, Solana, Bitcoin, Polygon, Arbitrum, Optimism, Base, BNB Chain, Avalanche, and Tron. Every chain is accessible through the same API surface, with normalized data formats so you don't need chain-specific integration code.

Question 3

How quickly can I integrate WalletSuite?

Accepted Answer

Most teams go from API key to working integration in under a week. The MCP Server requires zero code: add a few lines of JSON config and your AI agent has wallet access immediately. The SDK and API typically take 2-5 days to integrate depending on your use case. Building the same functionality in-house usually takes 12+ months and 5-7 separate vendor integrations.

Question 4

Do I need blockchain expertise to use WalletSuite?

Accepted Answer

No. The API and SDK handle chain-specific complexity for you: nonce management, fee estimation, gas optimization, UTXO selection, calldata encoding, token resolution, balance aggregation, price lookups, transaction simulation, webhook delivery, contract decoding, and multi-chain routing. Your team works with a standard REST API and typed SDK. The MCP Server goes further by letting AI agents interact with wallets through natural language, with no blockchain code at all.

Question 5

What is the MCP Server?

Accepted Answer

The MCP Server connects AI agents to on-chain wallet operations via the Model Context Protocol, an open standard by Anthropic. It exposes tools for balance queries, token resolution, price lookups, transfer preparation, transaction signing, and broadcasting. AI agents like Claude can call these tools directly during a conversation, with no SDK integration required on your side.

Question 6

How does WalletSuite handle transaction signing?

Accepted Answer

Two modes. By default, the API and MCP Server build unsigned transaction payloads for your own wallet to sign externally. With the Open Wallet Standard (OWS) enabled, the MCP Server manages keys in a local AES-256-GCM encrypted vault, signs transactions, and broadcasts them on-chain. OWS wallets use 12-word BIP39 mnemonics with standard HD derivation, and the mnemonic is never exposed to the AI agent. A four-band permission system (read, prepare, sign, broadcast) controls which operations an agent can perform, and per-wallet policy gates enforce chain restrictions and expiry rules.

Question 7

Can I use only specific components of WalletSuite?

Accepted Answer

Yes. The SDK, API, and MCP Server are independent products. You can use the MCP Server alone for AI agent wallet access, the API for backend integrations, or the SDK for typed client-side interactions. They share the same underlying infrastructure but don't depend on each other.

Question 8

What can I build with WalletSuite?

Accepted Answer

Teams use WalletSuite for AI agent wallet access, crypto payment processing, portfolio tracking, exchange backends, DeFi aggregators, and neobank on-ramps. Any product that needs to read balances, look up prices, resolve tokens, or prepare transactions across multiple chains.

Question 9

How does WalletSuite secure its infrastructure?

Accepted Answer

Security is layered across every level. All inputs are schema-validated before processing. The MCP Server enforces a four-band permission system (read, prepare, sign, broadcast) so AI agents can only access the operations you explicitly enable. When OWS is enabled, keys are encrypted with AES-256-GCM in a local vault, secrets never pass through tool arguments or chat, and every signing and broadcast operation is logged to a tamper-evident audit trail. Hook-level gates can require explicit user confirmation before any sign or broadcast call.

Question 10

What is token resolution?

Accepted Answer

Token resolution maps a human-readable identifier like 'USDC' to the exact contract address on a specific chain. Since the same symbol can exist on dozens of chains at different addresses, the resolver verifies the asset against a curated registry and flags ambiguous matches. This prevents misrouted transfers in both API integrations and AI agent workflows.

Frequently Asked Questions