Loops Houseaccord.

NEAR HACKATHON
Links
Team
1 member- NEOwner
Neel Pote
Overview
We built Accord to solve a problem with agents that can spend money: they read instructions from outside sources, and those instructions can be malicious. In our test, a poisoned billing document persuaded an agent to change its payment target. Accord caught the mismatch and refused to sign.
Accord lets teams buy recurring agent services with clear spending boundaries. Before each purchase, it checks the receiver’s available account history, contract identity, previous payments and shared evidence reports. It returns allow, warn or block with reasons. Warnings require human approval for one exact payment; blocks stop signing.
NEAR makes the spending agreement enforceable. Our Rust contract fixes the provider, price, minimum interval, cycle limit and expiry. The worker uses a finite-gas function-call key scoped to charge on that contract, never a full-access key. Owners can cancel future purchases, revoke the key and withdraw unused funds. Reports are linked to payment receipts and artifact hashes.
The app includes five live-chain monitoring services for balances, permissions, code changes, transaction receipts and RPC health. Teams can also approve application baselines, review changes and export evidence. The repository adds creator-hosted listings, execution approvals and delivery disputes; those features await deployment.
Our recorded testnet proof includes a successful control payment, blocked attacks and completed wallet exits. It is a prototype, not an audited security guarantee: reputation checks run in the backend, and payment verification does not establish report quality.