WaaP for Agents

Your AI agent can trade, earn yield, place bets, and move funds on-chain — without ever holding a private key.

WaaP for Agents splits the signing key between your device and a secure network using two-party computation. Neither side can sign alone. Your agent proposes transactions, and you approve the big ones from Telegram. Routine operations happen automatically within limits you set.

The result: your agent earns while you sleep, and no single point of failure can drain your funds.

What can agents do?

Agents built with WaaP are already running on mainnet. Here are the most common use cases:

Each recipe is a complete, working agent you can run today.

Get started

Give your agent a WaaP wallet in three steps:

# 1. Install
npm install -g @human.tech/waap-cli@latest
 
# 2. Create an agent wallet
waap-cli signup --email youragent@example.com --password 'YourSecurePass!'
 
# 3. Sign a transaction from your agent code
waap-cli send-tx --to 0xRecipient --value 0.01 --chain evm:1

Your agent calls waap-cli for every transaction. The CLI handles two-party signing, policy checks, and approval flows. Your agent’s code stays simple — it never touches a key.

Works with any language, any framework, any chain WaaP supports (EVM + Sui, Solana coming). See the full CLI command reference for all available operations.

import { execSync } from 'child_process';
 
function signAndSend(to, value, chain) {
  const result = execSync(
    `waap-cli send-tx --to ${to} --value ${value} --chain ${chain} --json`,
    { encoding: 'utf-8' }
  );
  return JSON.parse(result);
}
 
// Your agent logic calls this whenever it needs to transact
const tx = signAndSend('0xRecipient', '0.01', 'evm:1');

import subprocess, json
 
def sign_and_send(to, value, chain):
    result = subprocess.run(
        ["waap-cli", "send-tx", "--to", to, "--value", value, "--chain", chain, "--json"],
        capture_output=True, text=True
    )
    return json.loads(result.stdout)
 
# Your agent logic calls this whenever it needs to transact
tx = sign_and_send("0xRecipient", "0.01", "evm:1")

waap-cli send-tx --to 0xRecipient --value 0.01 --chain evm:1 --json
# Returns JSON: {"txHash": "0x...", "chain": "evm:1", ...}

How it keeps your agent safe

Every transaction flows through four layers before it reaches the chain:

Your agent proposes a transaction
        |
Policy engine checks spend limits and risk
        |
High risk? -> You approve on Telegram (t.me/waap_xyz_bot)
Low risk?  -> Signed automatically via Privileges
        |
Two-party signing: your device + secure network
Neither side holds the full key
        |
Transaction goes on-chain

Compare this to a raw private key in an .env file: one compromised dependency, one leaked secret, and everything is gone. WaaP eliminates that single point of failure.

Supported chains

One WaaP account gives your agent addresses on every supported chain. No separate setup per chain. See EVM networks and Sui networks for details.

AI agent skills

If your agent runs inside Claude, Cursor, or Copilot, it can discover WaaP automatically:

# Install the CLI — skills are bundled
npm install -g @human.tech/waap-cli@latest
 
# Or install skills standalone
npx skills add holonym-foundation/the-waap-skills

The SKILL.md inside the package teaches the AI agent how to use WaaP — it can create wallets, sign transactions, and check balances without you writing integration code.

Where to go next

I want to try an agent now:

• Cetus Yield Agent — Earn yield on Sui (5 progressive phases)
• Polymarket Agent — Trade prediction markets
• Browse all Recipes

I want to understand the security:

• Approvals & Notifications — Telegram bot setup and approval flows
• Policy Controls — Spend limits and risk thresholds
• Privileges — Scoped autonomy for routine operations
• Architecture — Two-party computation deep dive

I’m comparing wallet options:

• WaaP vs Coinbase Agentic Wallets
• WaaP vs Privy Server Wallets

I need the reference:

• CLI Commands — Full command reference
• Running Agents 24/7 — Production deployment patterns