OPEN-SOURCE PYTHON INFRASTRUCTURE · v1.18.5

Build agents that can actually execute.¶

Web3 Agent Kit provides autonomous agents with wallets, chains, protocol tools, transaction-safety primitives, and integrations for on-chain workflows. Write execution depends on the module and application configuration; not every write path is yet unified.

Get started View source

INSTALL pip install web3-agent-kit

agent.pyREADY

from web3_agent_kit import Agent, Wallet, Chain
from web3_agent_kit.defi import Uniswap

agent = Agent(
    wallet=Wallet.from_env("PRIVATE_KEY"),
    chains=[Chain.BASE],
    tools=[Uniswap()],
)

result = agent.run("check my balances")
print(result)

intent → policy → simulation → execution

25modules

1,957tests passing

9supported chains

75%coverage

MITlicense

01 / THE FRAMEWORK

Everything around the transaction.¶

The hard part of an on-chain agent is not calling a contract. It is making the full path observable, composable, and safe to operate. The kit keeps those concerns in one surface.

01

Agent runtime¶

Goal-driven execution with pluggable LLM providers, tool routing, structured results, and a Python API that stays readable.

Read the agent API →

02

Execution policy¶

Spend limits, operator confirmation, kill switches, and transaction simulation sit between an agent decision and a broadcast.

Review the security model →

03

Protocol primitives¶

DeFi, bridges, wallets, gas, portfolio, NFT, trading, oracle, and account-abstraction modules share the same chain-aware foundation.

Explore features →

04

Multi-chain by default¶

Use one interface across Ethereum, Base, Arbitrum, Polygon, Optimism, BSC, Avalanche, Robinhood Chain, and Solana. Chain connectivity does not imply every DeFi adapter is available on that chain.

EthereumBaseArbitrumPolygonOptimismBSCAvalancheRobinhood ChainSolana

02 / EXECUTION MODEL

Intended write lifecycle¶

A write should follow this lifecycle where the module and application have the required controls configured. Not every write-capable module currently uses one shared pipeline.

01IntentNatural language or typed request

02PolicySpend limits and allowlists

03SimulationPre-flight when supported

04AuthorizationApplication-verified approval for gated writes

05ExecuteOnly through a configured signing path

i

Beta software. The wallet gate fails closed, but write-path coverage is not yet uniform. Gated signing requires an application-supplied authorization provider; the current authorization digest does not bind gas limit or fee fields. Review the [safety pipeline](safety-and-transaction-pipeline.md), [maturity policy](project-maturity.md), and [risk disclosure](../RISKS.md) before using real funds.

03 / START HERE

Small surface. Serious foundations.¶

FIRST RUN

Build your first agent¶

Install the package, configure a wallet, and run a read-only balance check.

Open Getting Started →

TERMINAL

Use the `wak` CLI¶

Inspect chains, check dependencies, run examples, and operate without writing Python.

Open CLI reference →

REFERENCE

Browse the API¶

Go deeper into wallets, chains, LLMs, DeFi, bridges, security, and execution modules.

Open API reference →