Skip to Content
Introduction

What is the human.tech Wallet Protocol?

The human.tech Wallet Protocol gives an application or an agent a wallet its user actually owns. We call that protected self-custody.

Self-custody usually means the user carries the whole risk. A seed phrase to keep, a device to keep clean, and no recourse when either fails. Wallet-as-a-Service removes that risk by taking the wallet back: the provider decides what a wallet may do and charges for the privilege.

Protected self-custody is the third position. The user holds the authority. The signing keys are generated inside an attested Trusted Execution Environment and never reach the user’s device, so there is nothing on the device for malware to steal. Every signature passes a policy the user set before it is produced. One account works across applications and across chains, rather than one wallet per app.


waap-sdk2.3.0waap-cli2.2.0

The human.tech Wallet Protocol in use. Sign-on with email, phone, Google, Twitter, MetaMask and WalletConnect. An account with its balance and its buy, sell, send, swap and receive actions over a token list. An authorization panel where a second factor is required to sign a high-risk transaction, set here to email 2FA, with phone and an external wallet available.

Choose Your Path

WaaP for Apps

Integrate WaaP into your dApp with the SDK. Add 1-click onboarding, gasless transactions, and cross-chain support to any web application.

  • EVM and Sui support
  • UI customization via Playground
  • Sponsored transactions
  • Privileges for seamless UX
Get started with the SDK →

WaaP for Agents

Give AI agents and scripts secure wallet access with the CLI. Programmatic signing, policy controls, and 2FA — no browser required.

  • CLI and AI Agent Skills
  • Policy-based spending limits
  • 2FA with email, phone, Telegram, or hardware wallet
  • Privileges for autonomous flows
Get started with the CLI →

Build something

For apps

For agents

All recipes →

Keep reading

How a signature is protectedWhere the key lives, and what has to be true before it signsSquid ModeSigning distributed across an independent validator networkSupported networksEVM, Sui and Solana from one accountPrivilegesActing inside a scope without a prompt each time
Last updated on