01
“Discover and list mispriced Polymarket events”
Discover
/bloom Trade
Connect your agent to
Isolated keys per agent, spending limits it can't route around, and every transaction shown in plain English before it goes onchain.
Tell your agent:
Read https://bloom.directory/SKILL.md and set up Bloom.Contract address:
HykQwqkTSh2VR8Riof64PD8SxhbmSZ4sYwzqa9SpumpUse cases
Give your agent crypto super powers
02
“Text me when vitalik.eth buys a new ERC20 token”
Alert
03
“Send me a weekly position digest across all chains”
Digest
04
“I want to DCA into ETH over 6 months”
DCA
05
“Maintain an 80/20 split of BTC/ETH in USD value, rebalancing daily”
RebalanceWhy walletFS
Agent-native finance starts with your filesystem.
Keys in AI context
No private keys, no API keys, no secrets, no node URLs. Nothing inside the sandbox can leak what isn't there.
Fewer prompt tokens
Agents use fewer tokens and achieve higher task accuracy than MCP tool calls.
* Internal benchmark across representative wallet tasks.Approval to grant scoped autonomy
Sign a Sealed Approval once; the agent operates inside it and escalates when it hits the boundary.
The agent value chain
From human-operated apps to agent-native finance.
Today
- Human
- Application
- Wallet
- Smart Contract
- Blockchain
With walletFS
- Human
- Agent
- Smart Contract
- Blockchain
walletFS replaces the Application and Wallet layers.
Features
Built for agent-native execution.
Filesystem-native
The entire Ethereum ecosystem, mounted as files and folders. Reads are chain queries; writes are staged transaction intents. No SDK, no tool schemas. Your agent already knows ls and cat.
Sealed Approvals
You define exactly what the agent may do without you, whether a single swap or 30 days of Hyperliquid trades, and sign it once with a passkey. Everything outside the seal escalates to you.
Secured Keys
The agent runs in one folder with a contained blast radius. Keys live in an encrypted keystore outside the mount, so compromising the agent leaves nothing to steal.
Petals
Verifiable, agent-safe extensions. Any agent can build one; every user benefits. Live: Polymarket, Hyperliquid, x402/MPP payments.
Batched & Parallel
Stage many writes, review one sealed plan.
Multi-chain
Designed around Ethereum and EVM-compatible networks.
For teams & platforms
Agent wallet infrastructure for products that need control.
Agent wallet infrastructure
Embed agent-safe transaction execution without putting keys in model context or building a new approval stack for every integration.
Talk to us- Own the experienceGate signing behind your own UX
- Bound every agentEnforce spend limits and allowlists
- Stay accountableKeep audit-ready approval logs
Ecosystem
Works across the EVM ecosystem and the apps agents already use.
Networks
BNB Chain
Gnosis
Linea
HyperEVM
Robinhood Chain
Applications
Polymarket
Enso
MPP
Interactive preview
Watch an agent use walletFS.
Try
Scripted from real walletFS flows. Expand each step to inspect the command.
Try
/bloom Sealed Approval
Approve this action?
Frequent Agent Questions
What is walletFS?
walletFS gives AI agents the Ethereum ecosystem as mounted files and folders. Reads become chain queries, writes become staged transaction intents, and signing authority stays isolated from the agent.
Why do AI agents need a wallet built for them?
Consumer wallets assume a person is present to interpret screens and approve each action. Agents need machine-readable state, bounded authority, and inspectable plans that keep verification in step with execution.
Where do private keys live?
Keys stay in an encrypted keystore outside the agent's environment. The agent can inspect state and prepare actions, but key material never enters its context.
Can an agent move funds without me?
Only within scoped, time-boxed authority you explicitly grant through a Sealed Approval. Anything outside those boundaries stops and escalates to you.
What can a Sealed Approval constrain?
A Sealed Approval can limit duration, spend, recipients, contracts, and permitted actions. Requests outside the signed scope require a new approval.
How is it different from tool-based wallets?
Bloom replaces growing tool schemas and one-off integrations with one filesystem interface agents already understand. Petals add verifiable capabilities without changing that interaction model.
Which agents and chains work with it?
Bloom works with Codex, Claude, Cursor, Hermes, and custom agents that can follow local instructions. It targets Ethereum and EVM-compatible networks including Base, Arbitrum, Optimism, Polygon, Avalanche, and BNB Chain.
Is Bloom available today?
Yes, as open-source alpha software under active development. It is experimental and unaudited, so explore it with funds and environments appropriate for early software.
What does it cost?
The alpha is free to try, with no additional charge from Bloom. Standard network fees still apply when real transactions are signed and broadcast.
How do I get started?
Tell your agent: Read https://bloom.directory/SKILL.md and set up Bloom. Your agent will install walletFS and guide you through the initial setup.
Install walletFS