Create chat and worker agents with the model, instructions, tools, knowledge, and policy that define how they operate. Publish only after the required governance checks pass.
The builder carries agent configuration, policy assignment, impact assessment, deployment gates, run history, and lifecycle records together. There is no separate governance handoff after the build.
Build interactive chat agents for people, or worker agents for jobs triggered manually, on a schedule, by webhook, API, workflow step, or file upload.
Ground an agent in approved documents, choose its tools, and restrict it to knowledge data when the task demands a bounded answer.
Every agent runs under a policy template that combines data, access, spend, and violation rules. It can lock models, limit tools and sources, require human approval, and determine how a violation is handled.
Draft agents do not become Live until required pre-flight checks pass. Published agents retain run history, gate evaluations, and lifecycle changes.
Per-policy model locks, daily spend caps, and alert thresholds set agent guardrails. Alerts warn as a threshold is reached; a spend cap blocks the run.
Daily and monthly budgets notify the people responsible. A monthly hard limit blocks new worker runs until the limit is raised or the period resets.
Run history records status, inputs, outputs, tools, token use, estimated cost, duration, and any guardrail outcome. Open a run when a result needs review.
Start with an agent mode, team, policy, trigger, model, instructions, tools, and data.
Use the agent canvas for file-upload work, or let schedules, webhooks, APIs, and workflows start runs.
Inspect run history and the governance record beside the agent, including risks, evaluations, data sources, and gate history.