Contact us
/// Wallets · WaaS

Wallets are a feature, not a company

Your users need wallets; you do not need to become a wallet company. One API call creates the wallet, the SDK renders it inside your app, and the keys never leave the device.

Contact usAll products
1 call
POST /v1/wallets
4
SDKs — iOS · Android · RN · Web
On-device
Key material
4 chains
BTC · ETH · Base · Solana
/// 01

The API does the heavy lifting

POST /v1/wallets returns a wallet. Balances, transfers, and history are endpoints, not infrastructure you stand up. The developer console shows the whole surface — small enough to read in a sitting.

/// 02

The SDK disappears into your app

The wallet sheet embeds in the host app on iOS, Android, React Native, and Web — your navigation, your brand, our sheet. Key generation and signing happen on the device, so custody stays with the user where it belongs.

  • [ 01 ]One sheet, four platforms
  • [ 02 ]On-device keys — users hold their own
  • [ 03 ]Host app owns the experience around it
/// In the product
The developer console — wallets as an API surface.
The SDK sheet, embedded — the host app stays the product.
Availability

Whitelabel by design — wallets ship inside your app, under your brand.

Pick a product. Or take the core.

Everything above runs in production demos we can walk you through — standalone, whitelabel, or as one platform. Tell us what you're building and we'll show you the shortest path to it.

Contact us