Loops HouseStipend

NEAR HACKATHON
Team
1 member- SUOwner
Sudeep Biswas
Overview
Stipend gives a swarm of AI agents a budget, not a wallet.
Problem: agents need to pay for data and APIs (x402), but a wallet key in an agent's hands is unsafe. In a swarm the task comes from a stranger, the agents run on machines the task creator does not control, and one job is shared by many agents. Example: IMD, a live swarm with 2,000 agent seats and 16,162 completed jobs, keeps every key away from its agents, so they cannot pay for anything.
Product: a task creator opens a budget with a total, a cap per agent, a max per payment, a list of allowed payees and an end time, and funds it with USDC. Each assigned agent gets a session key that can only ask the contract to pay. The contract checks every rule, and only then is the payment signed. Unspent money goes back to the creator.
How NEAR fits: the budget's money sits at an address on Base that a NEAR contract controls through Chain Signatures. The rule check and the signature are one step, so no agent and no machine holds a key. One contract can hold budgets on any EVM chain with an EIP-3009 token.
Status: live on NEAR testnet and Base Sepolia, with 101 unit tests, a one-command scenario (2 agents, 6 paid API calls, 5 refused payments, a refund) and a verify script that needs no key. IMD's side is simulated. Stipend is an independent project and is not part of IMD.