600+ agents, ready on day one.
The work the build path spends its first two years on, shipped with the platform. Every agent runs governed by WALDO, attributed to a user, and grounded in the Library of Alexandria.
Security agents
Alert triage, vulnerability scan review, phishing analysis, credential-abuse reporting, incident timelines.
HR agents
Onboarding checklists, policy Q&A, leave and benefits requests, review-cycle preparation.
Facilities agents
Work-order intake, vendor coordination, space and asset tracking, maintenance scheduling.
Finance / Legal agents
Invoice matching, contract clause review, expense audit, filing-deadline tracking.
IT Ops agents
Ticket triage, access requests, patch status reporting, asset inventory reconciliation.
DevOps agents
Pipeline monitoring, release notes, dependency audit, environment drift reports.
Sales agents
Account research, proposal assembly, CRM hygiene, renewal and pipeline reporting.
Privacy agents
Data-subject request handling, retention checks, consent audits, disclosure log upkeep.
The catalog grows with the platform, and anything in it can be forked and customized in Studio without leaving its governance envelope. What the catalog doesn't cover, your team builds on the same rails.
Same rules as everything else
Every agent action is policy-checked by WALDO and lands in the audit trail. Pre-built does not mean pre-trusted.
Runs as the user
Agents inherit the identity and permissions of the person who runs them. No shared service accounts, no silent escalation.
Runs inside the walls
Agents execute on your infrastructure against your systems. Nothing in the catalog requires an external service.
See the ten agents you'd deploy first.
A briefing maps the catalog to your org chart and picks a pilot set.