Frequently Asked Questions

80+ 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.

Yes. The API is fully modular — use only the endpoints you need. Want just balances? Call the balance endpoint. Need only swaps or price feeds? Use those individually. The SDK, API, and MCP Server are independent products that share the same infrastructure but don't depend on each other.

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

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.

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.

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.

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.

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.

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.