# Hall: vault for AI agent wallets on Robinhood Chain > Vault for AI agent wallets on Robinhood Chain: spend caps, an allowlist of calls, a time-lock for big moves and a kill switch you hold. Over MCP, any agent can check a move against its vault's rules before it signs. Vaults cost only gas. > In detail: wallet vaults for AI agents on Robinhood Chain. A person (the owner) deposits ETH or tokens into their own vault and > writes a policy for one agent key. The agent can only move value through the vault, and every call it makes is > ruled on: the lock (an owner-only kill switch), the guest list (allowed contracts and functions; unlimited approvals > never pass), the counter (per-transaction, per-hour and per-day caps per asset) and the waiting room (moves over a > threshold wait for a time-lock, and the owner can cancel them). The owner can always withdraw. Status: the contracts are new and NOT audited. Deposits are capped per vault until an audit. Do not put in more than you can lose. HallFactory: 0x057c3acf129E17225e7a3374063a92FB2787c713 (chain 4663). Hall never holds a key and never sends a transaction. The API reads the chain and returns unsigned transactions. ## For an agent with a vault 1. Before any move, ask: `check_policy` (MCP) or `GET https://hallofagents.xyz/api/check?vault=0x…&target=0x…&value=0.04&data=0x…`. You get pass / hold / refuse, the door that stopped it and the amount counted, plus a simulation of your execute. 2. Build the transaction: `build_execute_tx` or `GET https://hallofagents.xyz/api/build?vault=…&target=…&value=…&data=…`. Sign and send it with your agent key. `execute` takes no ETH itself; the vault pays value from its balance. 3. If it was held, wait: `pending_timelocks` shows when it is ready. Then build `action=release&move=N` and send it. 4. A refusal reverts with `Refused(reason, asset, amount)`. Don't retry the same call: it will be refused again. ## MCP Endpoint: https://hallofagents.xyz/api/mcp (Streamable HTTP, JSON replies, protocol 2025-06-18, no sessions). Claude Code: `claude mcp add --transport http hall https://hallofagents.xyz/api/mcp` Tools: vault_status, check_policy, build_execute_tx, pending_timelocks, vault_activity. ## API (GET unless noted; JSON; CORS *) - /api/factory deployed factory, deposit caps, vault count, the rules and reason codes - /api/vault?vault=0x… | owner=0x… status, balances, caps with today's spend, guest list, held moves, inspection - /api/check?target=&value=&data=[&vault=] the ruling (sample policy without vault) - /api/build?vault=&target=&value=&data= unsigned execute tx for the agent (action=release|cancel&move=N too) - /api/pending?vault= held moves with release/cancel txs - /api/activity?vault=&n= the vault's events, newest first - /api/inspect?vault= sanity checks on a vault's policy - POST /api/draft { vault, changes: [...] } or { create: {...} } -> inspection + unsigned owner tx - /api/sample the sample policy and example rulings - /api/known labels for known Robinhood Chain contracts and selectors - /api/token the token's supply and burned amount, read from the chain Values: `value` is ETH as a decimal ("0.04"), or `value_wei`. `data` is 0x hex calldata. ## The rules (HallVault) Order: lock -> guest list -> counter -> waiting room. The first refusal ends it. - Guest list: target address + 4-byte selector. 0x00000000 = a plain ETH send to that address. The vault itself and the factory can never be called. approve(…, max), increaseAllowance(…, max) and setApprovalForAll(…, true) are refused. - Counter: ETH = the call's value. Tokens = the amount in transfer, approve, increaseAllowance, or transferFrom from the vault, on the token being called. An asset with no limits has caps of zero. Windows: clock hour and UTC day. - Waiting room: a move over the asset's holdAbove is queued for gateDelay (1 minute to 30 days). It is ruled on again at release (except the threshold) and must still fit the caps. It expires 7 days after it becomes releasable. - Lock: owner-only freeze/unfreeze. Frozen = every agent move and release refused. Withdrawals still work. - Owner: setLimits, clearLimits, setAllowed, setGateDelay, setAgent, freeze, unfreeze, cancel, withdraw (never paused), ownerExecute (any call outside the policy), two-step ownership handover, multicall to batch changes. Reason codes: 0 none, 1 frozen, 2 self_call, 3 not_allowed, 4 unlimited_approval, 5 bad_calldata, 6 over_per_tx, 7 over_per_hour, 8 over_per_day. ## The token No vault uses the token: creating a vault, setting its policy and every agent move cost only gas. /api/token shows supply and burned amounts read from the chain. No price is shown anywhere. ## Limits and honesty - 120 API requests per minute per IP. Everything is free. - Hall is not a scanner: it doesn't judge whether a contract is safe. It enforces the limits the owner set. - The contracts are new and not audited. ## Links - Website: https://hallofagents.xyz/ - X: https://x.com/HallOfAgents - MCP server (streamable HTTP, protocol 2025-06-18): https://hallofagents.xyz/api/mcp - $HALL token: 0x037Ab14E6DEb2a0f8c68ea19193E4AC1821d7e03 (https://robinhoodchain.blockscout.com/token/0x037Ab14E6DEb2a0f8c68ea19193E4AC1821d7e03) - Buy $HALL on Pons: https://ponsfamily.com/launchpad/0x037ab14e6deb2a0f8c68ea19193e4ac1821d7e03 - HallFactory: 0x057c3acf129E17225e7a3374063a92FB2787c713 (https://robinhoodchain.blockscout.com/address/0x057c3acf129E17225e7a3374063a92FB2787c713) - This guide: https://hallofagents.xyz/llms.txt (the same text is at https://hallofagents.xyz/llms-full.txt) ## ERC-8004 agent identity Hall vault API is an ERC-8004 agent. It is agent #26076 in the ERC-8004 Identity Registry on Robinhood Chain (eip155:4663:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). - Registration file: https://hallofagents.xyz/.well-known/agent-registration.json - Identity Registry: https://robinhoodchain.blockscout.com/address/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 - Reputation Registry (feedback from other agents): https://robinhoodchain.blockscout.com/address/0x8004BAa17C55a88189AE136b182e5fdA19dE9b63 - Sitemap: https://hallofagents.xyz/sitemap.xml