> ## Documentation Index
> Fetch the complete documentation index at: https://docs.walletsuite.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> A typed TypeScript SDK for multi-chain wallet operations, signing, and on-chain data.

Everything runs through one class — `WalletSuiteSDK` — so wallet creation, key derivation, transaction lifecycle, and on-chain reads share the same auth, types, and error surface. The SDK is non-custodial: you bring your own signing path — local keys, KMS, HSM, or custodian — and when you compose with an external signer the SDK never sees the private key.

<Note>
  Documented against `@walletsuite/wallet-sdk` v1.3.1.
</Note>

***

## Built for

Engineering teams who need typed, multi-chain wallet primitives in production — trading systems, treasury ops, fintech and payment backends, or Web3 features embedded into an existing stack. If you already own a signing layer (KMS, HSM, custodian), the SDK composes with it through [Bring your own signer](/sdk/end-to-end-token-transfer-flow#bring-your-own-signer).

***

## What you can build

* Multi-chain wallet creation with BIP-39 mnemonics and BIP-44 derivation
* Full transaction lifecycle — prepare, sign, broadcast — step-by-step or bundled in `sdk.transfer()`
* Native and token balance queries with fiat valuation
* Price, fee-quote, transaction status, and history queries across supported chains
* Asset metadata, name-service resolution (ENS, UNS), NFT ownership, and token allowance checks
* Staking and swap metadata queries on supported chains
* Webhook event subscriptions, signed and delivered in real time across supported chains
* Bring-your-own-signer integration — keep keys in your existing KMS, HSM, or custodian

***

## Non-Custodial

The SDK is one of three WalletSuite surfaces (alongside MCP and REST API), and is signer-agnostic. The SDK itself never stores user funds or private keys. Signing runs through whatever signer you bring — a local key for tests, or your existing KMS, HSM, or custodian in production. Key management remains under the integrator's full control.

<Info>
  Integrators are responsible for ensuring secure key handling and compliant usage within their own systems.
</Info>

***

## Multi-Chain Wallet Operations

* Consistent API across supported chain families
* WASM-based cryptographic implementation compatible with modern runtimes
* Wallet-agnostic — works with any key management or wallet architecture

***

## What's Included

<Columns>
  <Column>
    **Environment mapping**

    <Check>
      pass `prod` and the SDK resolves the correct endpoints
    </Check>

    **Typed API client**

    <Check>
      Typed responses for balances, assets, prices, blocks, fees, transaction status and history
    </Check>
  </Column>

  <Column>
    **TypeScript & JavaScript**

    <Check>
      full typings, ESM + CJS dual export, Node 18+
    </Check>
  </Column>
</Columns>