Web3 Companion · Open Source, MIT Licensed

Your Secure Agentic Wallet

Web3 Companion is a secure agentic wallet that lets your AI agent check balances, execute transactions, and move assets across chains—all without seeing your private keys or changing your security rules.

Onchain Workflows

What your agent can do on-chain

From checking positions to executing transactions, Web3 Companion lets your agent complete four core on-chain operations within the boundaries you set.

01

Check assets and positions

View wallet balances and holdings across Ethereum, Base, Polygon, and BSC.

02

Send tokens

Send native tokens or ERC-20 tokens to a specified address.

03

Same-chain swaps

Get quotes and execute same-chain swaps through supported DEX aggregators.

04

Cross-chain transfers

Get routes and move assets between networks through supported bridge protocols.

From prompt to on-chain execution

Swap 50 USDC → ETH · Within policy · Auto-signedTransfer to a risky address · Flagged high risk · Not signed

Address risk labels and transaction risk signals in the demo are powered by x402 Compliance API and MetaSleuth.

Security Boundaries

Autonomous within the boundaries you set

Your agent can be fooled—prompt injection and supply-chain compromise cannot be ruled out. But it never holds the keys: private keys exist only in the isolated Secure Signature Module. On top of that, every transaction passes three independent boundaries.

1

Security Review · Is this transaction safe?

  • Simulates what the transaction would actually do and runs 14 static checks
  • Decodes calldata and flags unlimited approvals, burn addresses, and address risk labels
  • Raises advisory risk signals; it does not block a transaction by itself
2

Signing Policy · Is this transaction allowed?

  • Per-transaction caps, daily budgets, and recipient allowlists are enforced by code
  • The agent cannot modify its own limits
  • Transactions that violate hard policy are rejected even if security review passed
3

Passkey Approval · Is it really you?

  • Policy changes, wallet exports, and transactions above the auto-sign threshold all require a Passkey
  • Hardware-bound biometric credentials the agent cannot forge
  • A purely software-level attack cannot substitute for the user’s physical presence
Agent submits intent
Simulation & security checks
Risk signals raised
Signing-policy validation
Hard-policy violation, rejected
Passkey confirmationonly when human approval is needed
Not confirmed, not signed
Secure Signature Module signs
Transaction goes on-chain
Get Started

Get started in three steps

1

Deploy in your environment

Start Web3 Companion with Docker and complete the initial setup in your browser.

2

Define your agent’s operating boundaries

Set per-transaction limits, daily budgets, recipient rules, and auto-signing conditions for each wallet.

3

Execute autonomously within those boundaries

Transactions within policy are signed automatically; those that require human approval request your Passkey.

FAQ

Frequently asked questions

Ready to try it?

Deploy Web3 Companion, review the code, set boundaries your agent cannot change.

Web3 Companion is an open-source research preview and has not yet undergone a complete production-grade security audit. Assess the risks before deploying it with real funds.