Loops HouseAgent Allowance on NEAR

NEAR HACKATHON
Links
Team
1 member- ZAOwner
Zach Riehn
Overview
Problem: a small business lets an AI agent handle supplier payments, and one convincing email ("we moved banks, resend INV-1044 to our NEW account") or a prompt injection can empty the account. Product: Agent Allowance on NEAR. The agent can investigate and propose a payment, nothing more. How NEAR fits: the agent account holds only a function-call access key for vault.propose_payment, so NEAR itself rejects any attempt to approve, transfer or add keys. A vault contract holds the money rules where the agent can't edit them: it pays only the supplier's payout account on file and enforces a shared blocklist, per-supplier, per-payment and daily caps, one payment per invoice and a STOP switch. Rule-breaking proposals are stored as Refused with the reason, so every attempt is on the public record. Only the owner account can approve, and approval re-checks every rule. Before signing, an agent-side wrapper also scores the receiver (blocklist, payout on file, account exists, contract or not, account age, payment history). A live testnet run shows 10 PASS results, including the scam payout refused by both the wrapper and the vault, and the agent key rejected by NEAR for approve and transfer. 12 contract tests pass. Built with AI coding agents (Claude, with Codex reviewing) under Zach Riehn's direction.