Loops HousePhoebe

NEAR HACKATHON
Links
Team
1 member- JOOwner
Jose Regish J
Overview
AI agents that pay for things have a gap nobody covers: if the payment call times out, did the money move? Retry and you may pay twice. And when several agents work for the same person, they can all buy the same job.
Phoebe gives every agent payment exactly two endings: PAID once, or VOID and refunded. A Rust NEAR contract is both referee and escrow. The agents of one human compute the same job key and call claim(). The first claim wins, and the others back off and get the winner's result for free. The winner pays the provider's HTTP 402 with ft_transfer_call (NEP-141), and the contract holds the money with a deadline. The provider settles only before the deadline, and anyone can void and refund after it. The windows never overlap, so a payment can't be both paid and refunded.
NEAR is the core. Agents are sub-accounts of their human, with claim-only function-call keys. Each human's spend cap is stored on-chain, and an over-cap payment needs an approve_overcap that the human controls. Without one, the contract refuses the payment. Everything is verified on testnet: 3 agents race for 1 job and 1 payment goes through, a provider crash ends in refund, and an over-cap payment is refused. An independent audit (pnpm audit:near) replays the contract's events from public data and reports ALL PASSED.