Loops HouseFloat

NEAR HACKATHON
Links
Team
1 member- WAOwner
wattson
Overview
Float gives an AI agent a spending budget that a smart contract enforces.
To let an agent pay for one thing you normally hand it a key that can pay for everything. A rule in a prompt is not a boundary.
The agent gets a NEAR key that can call exactly one method on exactly one contract. It cannot move tokens, raise its own limit, reach any owner function, or touch your wallet. Those are protocol-level key restrictions, not policy checks it can argue its way around. The agent also holds its own gas and submits its own transactions, so it has a wallet of its own rather than borrowing yours.
Budgets are a tree, so one vault runs departments. Each agent gets its own ceiling and every payment charges every level above it, so a company-wide limit holds even when one agent's own cap looks free. The contract answers with which rule stopped the payment and at which level: PARENT_PER_TX_LIMIT, not PER_TX_LIMIT. There are 48 such codes.
The human sets the constraints once, and that is all they do. The agent proposes policy changes and cannot make them: every limit change comes back as an unsigned payload to approve in your own wallet.
Live on mainnet. Factory usefloat.near. Vault test015-near.usefloat.near: 7 budget nodes, 5 agent keys each restricted to request_payment on that vault alone, holding real Circle USDC. A 15 USDC request was refused on chain and moved nothing - tx 22NyhaHRianC8zrnNK7ujZkRLdB4kYztFfFFSSQUgba9 returns reason_code PARENT_PER_TX_LIMIT. Payments settle through that same path.
You can audit what runs: res/vault.wasm in the repo hashes to Fqep3KLeorhv..., exactly the code deployed at that vault. Winding down returns everything - tokens, each agent's gas balance, the storage deposit.
Try it: open usefloat.xyz and approve one transaction. The factory creates your vault, deploys it, binds an agent key and registers it on the token in that one signature.
Install: npx -y @floatonnear/mcp (27 tools). 1,424 tests, CI green.