ResidentOS

Inspiration

Apartment buildings are full of informal food sellers, meal prep operators, and neighbors coordinating orders through chats and screenshots. We wanted to turn that messy, high-trust workflow into a lightweight operating system powered by agentic infrastructure.

What it does

ResidentOS lets residents subscribe to meals through a Telegram bot, submit Zelle receipt screenshots, and get verified automatically. The seller dashboard updates in real time with subscribers, payments, flagged receipts, and delivery manifests.

How we built it

We used IronClaw as the Telegram agent runtime, NEAR AI for private receipt extraction, InsForge for Postgres-backed state, edge functions, and realtime events, and Tigris for private artifact storage of receipts and manifests. Render hosts the live dashboard, while ResidentOS MCP tools let the IronClaw agent write directly into the product workflow.

Challenges we ran into

The hardest parts were sponsor integration boundaries: getting IronClaw on NEAR AI Cloud to load runtime environment variables correctly, wiring MCP tools so the agent could do more than chat, and keeping backend request volume low enough to avoid rate limits. We also had to make receipt verification strict enough to require confirmation numbers instead of accepting vague “I paid” messages.

Accomplishments that we're proud of

We built a full loop: Telegram intake, AI receipt understanding, private artifact storage, database writes, realtime dashboard updates, and manifest generation. We are especially proud that each sponsor is used in the core path rather than as a side demo.

What we learned

Agent instructions are not enough by themselves; agents need reliable tools, clear approval paths, and narrow schemas. We also learned that hosted agent environments need careful env propagation, restart behavior, and rate-limit-aware dashboard design.

What's next for ResidentOS

Next we would harden the IronClaw tool flow, expand InsForge realtime notifications, improve NEAR AI receipt validation across more payment formats, and use Tigris for richer audit trails. Longer term, ResidentOS can support multi-seller buildings, recurring meal plans, inventory, delivery routing, and sponsor-powered agent workflows for local commerce.

Built With

• ai
• insforge
• ironclaw
• near
• render
• tigris