Patterns of AI agents
Standardize Agentic Apps
An assistant, a scheduled job, a developer's editor, a service for other people's agents. Each is a golden path your platform team sets up once and every app team reuses.
Example patterns
Standardizing agents with composable resources
Agents are typically sophisticated workflows, and so have similar patterns to produce expansive results. This enables platform teams to define golden templates and pathways for agents in production.
Hundreds of people, one agent.
A support copilot or an internal Q&A service. Each person expects answers scoped to what they can see.
Hannah's identity travels with every call, through the sub-agent hop. A Rule can name her, and the Audit record names her and the agent. Click any box or gate to see what it is.
What makes it hard
- One agent serving everyone reaches everything anyone can reach.
- A sub-agent hop usually drops the person who asked.
The golden path
Callers. Verify every person through your identity provider.
Agents. Register the assistant with acts-as required.
Gateways. Grant one Gateway of tools and model pools.
Rules. Write conditions on the person, not only the agent.
Guards. Redact what this person shouldn't see.
Quotas. Cap the agent's spend over a window.
The Dome platform
Define Agentic Apps with Dome's resource model
Every pattern is wired from the same resources. Learn them once, and a new pattern is a new arrangement, under rules and a record you already have.
Next steps
Talk with our FDE team
Our forward deployed engineers work with your platform team to get your agents into production and under control: the first one governed on your own systems, and a pattern your teams can repeat for every agent after it.
No card required to start. Register your first agent in minutes.
Business patterns
The level up: agents your business uses, and agents your product ships.
See business patterns