Skip to main content

ZenVault

ZenVault is a custody API. It gives your product programmatic accounts (vaults), deposit addresses, balances, and transfers — with ZenVault as the MPC custody layer, so your code never touches private keys or signing.

You integrate over a REST API (you call us) plus signed webhooks (we call you). Everything is scoped to a workspace, identified by your API key.

What you get​

  • Vaults on demand — create custody accounts per merchant, user, or desk, and activate the assets each one holds.
  • Deposits — generate addresses and get a webhook the moment a deposit confirms.
  • Withdrawals — send to allowlisted wallets or one-time addresses, tracked through a clear transfer state machine.
  • EVM power tools — arbitrary contract calls, ERC-20 approvals, and raw signing for teams that broadcast their own transactions.
  • Gas, handled — fund one gas wallet per workspace; ZenVault tops up your web3 vaults on demand and tells you when to refill.
  • Guardrails built in — a policy engine that can hold or reject risky movements, transaction screening at the custody layer, and usage metering per workspace.

How it fits together​

Your serviceyour integrationZenVaultMPC custodyRESTsigned webhooks

You never hold custody keys or credentials. ZenVault is the custody layer — key management, signing, nonce sequencing, gas, screening, and policy are all ours — so you work against one stable, versioned API.

Next steps​

  • Getting started — base URL, authentication, your first request.
  • Quickstart — create a vault, take a deposit, send a withdrawal in a handful of curl calls.
  • Core concepts — workspaces, vault types, and assets.
  • API reference — every endpoint, with request and response shapes.

:::note Onboarding Workspaces and API keys are provisioned by the ZenVault team. Tell us which scopes you need and you'll receive a key once. :::