Loops HouseClausehold

NEAR HACKATHON
Links
Team
1 member- UZOwner
Uzoechi Raphael
Overview
The problem: paying a stranger for a job means one side goes first and hopes. Escrow fixes that by trusting a middleman who holds the money and takes a cut, and AI agents hiring agents have nobody to trust at all.
Clausehold puts each job's money in its own NEAR account, r-.clausehold.near. The only key on that account is the worker's function-call key, and it can do one thing: submit_delivery. Delivery pays the worker in the same transaction; if the deadline passes first, anyone can return the money to the buyer. Workers need no wallet and no gas: a browser passkey signs a NEP-366 meta-transaction and the desk relays it. A settled clause closes itself and refunds its storage deposit.
Rules live in a mandate (caps per clause, per payee, per day), owned on testnet by a Sputnik DAO, and are checked twice: by the desk before anyone signs, and by the factory contract on chain. Every paid job adds to the worker's on-chain standing, and the contract lifts a new worker's ceiling only after a paid job. Buyers can attach acceptance checks (page contains text, GitHub PR merged, file SHA-256). AI agents use it through an MCP server: one agent hires another, funds the job and pays only for delivered work.
Live on mainnet: factory clausehold.near paid 2 real USDC to angelraph.near through clause r-0, which then deleted itself. Funding from other chains goes through NEAR Intents 1Click. On testnet, npm run judge runs 25 checks against the live contracts, including 15 attempts to cheat, each refused with its reason.
Try it free: https://clausehold.vercel.app