SiteAgent

Construction, coordinated by agents.

One shared network where builders, trades, suppliers and inspectors see the same truth. AI agents watch for changes and draft the coordination work — people build, agents chase. Pick where you want to go.

ⓘ

How to read this app

Everything you see is served by the SiteAgent API (:4000), which reads from a Postgres database with strict per-tenant isolation. Builders and trades see only their own data. The pages below each explain, in place, exactly what data they show and where it originates.

For builders

Portfolio Dashboard

builder

Schedule health per project, count of pending approvals, what the agents handled today, and a live audit trail. Data comes from your projects, agent runs, and the append-only audit log.

Approval Inbox

builder

Recommendations drafted by the agents in Recommend mode — each with cited evidence and a confidence score. Nothing is sent until you approve; approving releases the coordination messages.

For trades

One Calendar ↗

trade

Your jobs across every builder you work for, merged into a single schedule. Pulled live from the real BuildBase / HoBO API — real jobs with real schedule dates, color-coded with conflict flags.

API & Swagger ↗

developer

Every endpoint the apps use, live and explorable. Authenticate, create a project, ingest a signal, connect a vendor, run a 3-way match — all documented.

Where the data comes from

SiteAgent DB (Postgres)BuildBase · HoBO (live API)Agent recommendations

The system of record for projects, tasks, schedules, approvals and invoices is SiteAgent's own database. The trade workspace pulls read-only job & schedule data live from the real BuildBase / HoBO API — each synced record keeps its source and sync time (provenance). Agent recommendations are drafted from signals (e.g. a frame-ready slip) and always carry the evidence they were based on.