Loops HouseSupply

NEAR HACKATHON
Links
Team
1 member- DOOwner
Double J
Overview
Problem: a small manufacturer or food producer buys from dozens of suppliers, and its stock, quotes, specs and approvals live in email threads and spreadsheets. An AI assistant could do most of that work (spot low stock, send RFQs, compare quotes against specs, raise orders), but a company cannot let it while the records can be wrong and one prompt-injected supplier email ("our bank details have changed") can redirect a payment. Paying suppliers on a public chain would also show competitors who you buy from and at what price.
Product: Supply is two MCP servers that an assistant such as Claude or Codex works through.
- The supply server holds a company's purchasing records: stock, specs, suppliers, RFQs, quotes, purchase orders, approvals, documents and an audit log. Unit and pack conversions are exact, Postgres row-level security keeps each company to its own data, and every change carries a reason. In code mode, two tools (search and execute) run the assistant's JavaScript in a QuickJS sandbox against 80 operations.
- The payment MCP pays purchase orders a human approved. The assistant passes only an order id; the payment MCP fetches the approved instruction from the supply server itself, checks it against its own limits (token allowlist, per-payment and daily caps, balance, receiver exists), pays, and records the payment on the order. It cannot approve orders or change payout accounts, and a crash at any point never pays twice.
NEAR: on mainnet each order is paid in USDC through NEAR Confidential Intents, with a 1Click quote for the exact amount and a NEP-413 signed transfer from the payer's confidential balance to the supplier's, so amounts and payees stay off the public chain. On testnet it pays publicly with a NEP-141 ft_transfer of Circle USDC and registers the supplier's storage (NEP-145), so suppliers need no NEAR. The payer wallet can be funded with USDC from seven chains through 1Click deposit addresses.