Loops HouseBFA (Built For Agents)

NEAR HACKATHON
Team
1 member- PAOwner
Panupong
Overview
The problem: AI agents are becoming the main users of APIs, but APIs are still built for humans: accounts, subscriptions, API keys, a card on file. An agent can't sign up, and you don't want to hand it your card or a private key. We think building for humans first is the wrong bet now that agents are growing this fast.
What we built: BFA, the convenience store for AI agents. It is an open, pay-per-call API market. An agent connects over MCP, finds an API, sees the exact price, pays for one call in USDC with x402 on Base and gets a receipt. You sign in with Google, pick the APIs you prefer in the aisles, set how much to spend on each, and give each agent its own key with an expiry, a daily cap, per-API caps, an allow/block list and a provider order (say Gemini first, then Wan). Anyone can list an API by pull request; a reviewer pins the manifest hash. Failed and empty calls are free.
How NEAR fits in: every user's wallet is a vault in our treasury contract on NEAR. Its Base address is derived by NEAR Chain Signatures, so nobody holds its EVM key. The contract rebuilds each USDC authorization itself and signs only within the user's on-chain daily limit, allowed recipients and pause switch. The agent's gateway gets a NEAR function-call key that can call only sign_eip3009, so it can spend within the limit but never raise it. The NEAR wallet key is made in the user's browser, and the user signs their own vault setup. Top-ups go through a public split contract: send $10.15, $10.00 lands in your vault, $0.15 is our fee.
Live on testnet (NEAR testnet + Base Sepolia), shown in the demo: a new user signs in, sets up a wallet, gets test USDC, makes a key with a $0.003 daily limit, and an agent pays three calls from that vault before the fourth is refused with limit_reached, before any money moves.
Next, on mainnet: top-ups in any token and seller payouts through NEAR Intents.