Why integrate TealTiger with CrewAI?
CrewAI enables powerful multi-agent collaboration, but lacks built-in governance. TealTiger adds:- Agent-level policies - Control what each agent can do
- Cross-agent coordination - Track decisions across the crew
- Cost attribution - Know which agent spent what
- Audit trails - Complete visibility into multi-agent workflows
Quick start
Install both packages:Integration patterns
Pattern 1: Agent wrapping (recommended)
Wrap each agent to add governance:- Per-agent policies
- Clear cost attribution
- Independent governance
- Need to wrap each agent
Pattern 2: Crew-level governance
Apply policies at the crew level:- Single integration point
- Consistent policies across agents
- Less granular control
Pattern 3: Tool-level interception
Govern specific tools used by agents:- Fine-grained control
- Can govern third-party tools
- More code to write
Complete example: Multi-agent research crew
Here’s a complete example of a CrewAI research crew with TealTiger governance:What gets governed?
TealTiger governs these CrewAI components:Agent actions
Every agent action is evaluated:- Tool usage
- LLM calls
- Inter-agent communication
- Task execution
Crew coordination
Crew-level governance:- Total crew cost
- Execution duration
- Agent collaboration patterns
- Resource allocation
Tool executions
Every tool call is checked:- Tool allowlists per agent
- Approval requirements
- Cost attribution
- Audit logging
Policy examples for CrewAI
Example 1: Role-based access
Different policies for different agent roles:Example 2: Cost control per agent
Limit spending for each agent:Example 3: Approval workflows
Require approval for sensitive operations:Monitoring multi-agent workflows
View crew metrics
View agent audit logs
Track crew execution
Best practices
- Wrap agents individually - Better cost attribution and control
- Set per-agent budgets - Prevent any single agent from overspending
- Use crew-level limits - Cap total crew cost and duration
- Enable audit logging - Track multi-agent interactions
- Test in MONITOR mode - Validate policies before enforcing
- Use correlation IDs - Link related agent actions
Common issues
Issue 1: Agents bypassing policies
Problem: Some agent actions aren’t being governed Solution: Ensure all agents are wrapped:Issue 2: Cost attribution unclear
Problem: Can’t tell which agent spent what Solution: Use agent IDs:Issue 3: Crew exceeds budget
Problem: Total crew cost exceeds limits Solution: Set crew-level budget:Next steps
Policy overview
Learn how to write policies
Cookbook examples
See real-world examples
API reference
Explore the Python API
Other integrations
View all integrations

