Loops HouseAllowance

NEAR HACKATHON
Links
Team
1 member- ANOwner
Andrea Soldano
Overview
AI agents that pay for APIs, data or other agents usually hold a full-access key or a custodial wallet: one prompt injection away from an empty account. Allowance gives an agent an allowance, not your keys. A human funds a vault contract on NEAR and writes the spending policy on-chain: asset (NEAR or a NEP-141 stablecoin), per-payment cap, budget per day, payee allowlist, denylist, time window, cooldown, human approval above a threshold, expiry, pause and kill switch. Each agent is a function-call access key that lives on the vault account itself and can only call pay, confirm_delivery and ping: the NEAR protocol checks the key before the contract runs, the contract checks the money, and the kill switch deletes the keys at protocol level. The agent needs no account and no faucet. Before paying it checks the payee with a keyless counterparty-risk service (deny-lists, account age, contract code changes, history in the vault) and dry-runs the payment with a free simulate view. Every payment, rejection and approval is an on-chain receipt that a paid HTTP API verifies with one RPC view, an x402-style flow without a facilitator that works with function-call keys. We built the Rust contract, a TypeScript SDK and CLI, an agent loop with one counteroffer and optional NEAR AI planner, a paid demo API, an attack demo, a static ledger page, NEP-141 payments with payee storage registration, a revenue split for agent businesses, vault-to-vault payments and a factory that creates vaults from one global contract. make demo runs the whole story on a local sandbox with eleven on-chain checks.