Loops HouseBuilderOS

NEAR HACKATHON
Links
Team
1 member- ONOwner
Oni Samuel Ayomide
Overview
BuilderOS is an operating system for AI-run software companies on NEAR. A founder describes a product; BuilderOS turns it into a plan with a cost estimate and creates the company on chain, with teams of AI agents that buy the models and services they need and build it.
The problem: agents that can spend money are only safe if a compromised server, a prompt-injected agent or a bad seller can't drain the treasury. So the rules live on NEAR and the off-chain services are powerless over funds.
How NEAR fits in:
- Rust contracts (factory, company, team) hold every budget, per-purchase limit, task cost cap, allow-listed seller, the daily cap, approvals, member grants and a company-wide pause.
- Agents hold request-only function-call keys. The team contract builds each USDC payment and NEAR Chain Signatures signs it only after the contract approves; anything over a limit becomes an approval card for the founder.
- Sign-in is NEP-413 (NEAR wallet, or Google/email through Privy with a NEAR account). Every change emits a NEP-297 event that the indexer turns into a receipt.
- Agents pay NEAR AI models per call via x402. The company treasury and cross-chain withdrawals use NEAR Intents and 1Click (mainnet path, tested against a simulator).
Live on NEAR testnet: sign in, describe, launch a company and its teams on chain, approve plans, invites and grants, pause/resume, ledger, plus a read-only sample company. Tests: 174-step and 46-step end-to-end suites, 64 unit tests, contract tests, 46 Playwright tests.
Frontend: github.com/Wangsamuels/BuilderOS-frontend. App: builder-os-eight.vercel.app
My other submission is Kronos (github.com/Wangsamuels/Kronos-backend), an independent project with a separate codebase.