Patterns of AI agents
Building the Agentic Enterprise
Every enterprise uses agents and ships them. Your platform team sets up a golden path for each direction once, and every team after it starts from there.
Produce agents, consume agents
Which way do your agents cross the boundary?
Inside, your agents reach your systems. Outside, your customers' agents reach your product.
The business consumes agents
Built in-house, bought as SaaS, or wired up in a workflow tool. No single vendor governs the estate.
Dome, on the way out. Every call is authorized, filtered and recorded.
The pressure
- Velocity from below. An analyst builds a working agent in an afternoon.
- Fragmentation from above. Every agentic SaaS tool brings its own permission scope.
- The build/buy line moved. Replace a SaaS tool with an agent and you inherit its management plane.
The golden path wires
- Callers
- Agents
- Gateways
- Rules
- Guards
- Audits
Application patterns inside
One platform
What changes, and what doesn't
The callers change and so do the targets. The platform, the rules language and the record stay the same.
Agent consumers
The business consumes agents
Who calls
Your teams' agents, built or bought
Identity
Each agent registered, acting for a named person
What they reach
Your tools, data and SaaS
Gateways
One per team or environment
Limits
Rules on the person, guards on responses
The record
One audit record
Agent producers
The product ships agents
Who calls
Your customers' and partners' agents
Identity
Each agent registered under its tenant
What they reach
Your product's APIs and MCP servers
Gateways
One per tenant, with only its entitled tools
Limits
Rules per tenant, with a quota on each
The record
One audit record
Agent consumers
The business consumes agents
Agent producers
The product ships agents
Who calls
Your teams' agents, built or bought
Your customers' and partners' agents
Identity
Each agent registered, acting for a named person
Each agent registered under its tenant
What they reach
Your tools, data and SaaS
Your product's APIs and MCP servers
Gateways
One per team or environment
One per tenant, with only its entitled tools
Limits
Rules on the person, guards on responses
Rules per tenant, with a quota on each
The record
One audit record, for both directions
Standardizing operations
Business patterns contain application patterns
Each direction is made of the application patterns inside it, and every one of those is built from the same resources.
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.
Application patterns
The level down: the golden path for the agent you are building, wired and running.
See the patterns