Loops HouseMandate

NEAR HACKATHON
Links
Team
1 member- DAOwner
Danny Amara
Overview
Giving an AI agent a wallet today means handing it a raw private key: unlimited authority you can't cap or revoke short of killing the key. Mandate replaces that with a capped, revocable, allow-listed spending permission. An owner issues an agent a mandate (a daily cap, the contracts it may pay, an optional expiry), and any NEAR app gates spending through one call: authorize_spend(mandate_id, target, amount) fails closed if the cap, allow-list or revocation says no, and only then does the real call run. A guard agent watches spend velocity and revokes mandates that look wrong.
The flagship is Hire a Swarm: post a job with a NEAR budget, worker agents bid, you assign one, it delivers real work (a Gemini inference call) stored on-chain, and accepting pays the winning bid and refunds the rest in the same transaction. Every budget is gated by Mandate first. A coordinator agent can hold its own mandate and sub-bounty work to other agents from a capped treasury; on testnet its second spend panicked with 'daily cap exceeded', exactly as designed.
How NEAR fits: settlement is native NEAR transfers, and mandates turn NEAR's function-call access key idea into an explicit, inspectable, revocable policy object. Both contracts are live on testnet (mandate-f70187.testnet, market-f70187.testnet): 3 mandates issued, 23 jobs posted, 16 settled, 1.85 NEAR routed by real worker agents. The /developers page documents the two-call pattern so any NEAR app can plug in the same way.