Your AI agent trades, hunts deals, and earns on-chain — while you sleep.

From npm install to your first transaction in under ten minutes.

Get started

Pick your first agent.

Pre-configured recipes you can clone and run. Or skip ahead and build your own with the CLI.

Polymarket agent

Ready

Watches Polymarket for mispriced markets, places bets, pings you for the big ones.

Morpho yield agent

Coming soon

Rebalances your stables to the highest-APY pool across lending protocols, within the limits you set.

Pendle auto-roll agent

Coming soon

Auto-rolls your maturing Pendle yield positions, pings you for approval on bigger moves.

Snapshot voter

Ready

Votes across the DAOs you care about using your preferences. Asks you about the big ones.

Agent wallet in four commands.

Install the CLI, create an account, enable 2FA, set your daily spend — and voilà. You're ready to send your first transaction.

npm install -g @human.tech/waap-cli
waap-cli signup -e <email> -p <password>
waap-cli 2fa enable --telegram
waap-cli policy set --daily-spend-limit 10

Signup confirms on Telegram. Daily limit starts at $10 — increase it when you're ready.

Read the full docs

Why your agent's wallet should be built different.

2PC key split. No single party holds it.

The private key is split between your device and a secure enclave, never reconstructed. Compromise one share, funds don't move.

Alternatives reconstruct the full key inside a single enclave. One breach of that enclave and every customer is exposed.

You set the budget. The agent stays within.

Daily spend limits, whitelisted contracts, auto-approve for routine ops. Enforced at the signing layer.

Most alternatives enforce policy in application code — a compromised agent can bypass it. We enforce it where the signature is produced.

One-tap approve, from anywhere.

2FA via Telegram, email, SMS, or hardware wallet. Anything above your limits pings you first — approve or deny in one tap.

Most alternatives run agents fully autonomous. You find out about bad trades from your balance, not a notification.

Scoped autonomy without modal prompts.

Permission Tokens let the agent act freely inside a box — capped spend, fixed expiry, whitelisted addresses. No latency penalty.

Alternatives either block the agent with a user prompt on every transaction or let it sign anything. We split the difference cryptographically.

Every EVM chain. No lock-in.

Every EVM chain via CLI today. Sui and Stellar via SDK. Solana in progress.

AgentKit is Base-optimized (gasless is Base-only). Your agent transacts wherever the opportunity is — not where your wallet provider optimized for.

Revenue share, no per-signature billing.

No integration fees. No per-signature costs. Wallet infra becomes a revenue source, not a cost center.

Privy charges per signature above their free tier. Your scale becomes their billing. We don't do that.

How WaaP compares.

Direct architectural comparison with the three providers developers usually evaluate alongside us.

 WaaPCoinbase AgentKitPrivyTurnkey
Custody model2PC — key split between user device and secure enclave, never reconstructedNon-custodial wallets in Coinbase TEE (single-provider trust)Full key reconstructed in a single enclaveKeys in AWS Nitro Enclaves
Who can act by defaultNo one above your policy limits — approval requiredAgent (autonomously, no approval step)Apps act on the wallet by defaultWhatever the developer builds
Human-in-the-loopTelegram/email one-tap approval, built inNone for individual transactionsQuorum approvals via cryptographic key signaturesDeveloper builds it themselves
Pricing modelRevenue share — no per-signature billingNot publicly documentedPer-signature above free tier (50K sigs / $1M volume)Not publicly documented
Chain supportAll EVM; Sui + Stellar via SDK; Solana in progressOptimized for Base (gasless Base-only)Multi-chainCurve-agnostic (any chain)
Integration timeCLI install to first tx in under 10 minutesDrop-in for AgentKit apps on BaseSDK integration per dAppSignificant DIY — low-level signing infra

What we're shipping next: x402 support for machine-to-machine payments. Per-contract limits, time-of-day, and velocity controls in the policy engine. Today, the engine handles daily spend limits, contract whitelists, and auto-approve rules.

What goes wrong with the alternatives.

Three custody models in common use. Three failure modes. What the architecture decides.

If the agent holds the full key

One prompt injection or compromised dependency is enough to move funds.

The agent doesn't need to be malicious — just exploited once.

With WaaP

The agent never holds the full key. 2PC splits it between your device and a secure enclave. Nothing to read out of memory.

If the wallet provider holds every key

Single-provider custody means a single point of failure for every customer on the platform.

One breach of their infra — or one rogue employee — and the blast radius is the entire user base.

With WaaP

Neither party holds the whole key. The provider can't move funds without your share, and you can't sign without theirs.

If there's no human approval step

Any transaction the agent decides to make executes automatically.

First time the model hallucinates or inputs get poisoned, funds move before you notice. By the time you check, they're across a mixer.

With WaaP

Anything above your policy limits pings Telegram for one-tap approval before it goes through. You stay in the loop where it matters.

Questions humans ask.