Quick Reference Cards
Swarm Types
Available Swarm Architectures
See Available Architectures for the full, current list of swarm types.
Application Patterns
Specialized Application ConfigurationsCost Optimization
Advanced Cost Management StrategiesService Tiers
Choosing the Right Service TierIndustry Solutions
Industry-Specific Swarm PatternsError Handling
Advanced Error Management StrategiesChoosing the Right Swarm Architecture
Decision Framework
Use this framework to select the optimal swarm architecture for your use case:-
Task Complexity Analysis
- Complex tasks →
HierarchicalSwarmorMultiAgentRouter - Dynamic tasks →
AgentRearrange
- Complex tasks →
-
Workflow Pattern
- Linear processes →
SequentialWorkflow - Parallel operations →
ConcurrentWorkflow - Collaborative tasks →
GroupChat
- Linear processes →
-
Domain Requirements
- Multi-domain expertise →
MixtureOfAgents - Data processing →
BatchedGridWorkflow - Quality assurance →
MajorityVoting
- Multi-domain expertise →
Industry-Specific Recommendations
Finance
Financial Applications- Risk Analysis:
HierarchicalSwarm - Market Research:
MixtureOfAgents - Trading Strategies:
ConcurrentWorkflow - Portfolio Management:
BatchedGridWorkflow
Healthcare
Healthcare Applications- Patient Analysis:
SequentialWorkflow - Research Review:
MajorityVoting - Treatment Planning:
GroupChat - Medical Records:
MultiAgentRouter
Legal
Legal Applications- Document Review:
SequentialWorkflow - Case Analysis:
MixtureOfAgents - Compliance Check:
HierarchicalSwarm - Contract Analysis:
ConcurrentWorkflow
Production Best Practices
Best Practices Summary
Recommended Patterns- Use appropriate swarm types for tasks
- Implement robust error handling
- Monitor and log executions
- Cache repeated results
- Rotate API keys regularly
- Choose appropriate service tier based on task urgency
- Schedule non-urgent tasks during off-peak hours (8 PM - 6 AM PT) for Swarm Completions to benefit from night-time discount
- Hardcoding API keys
- Ignoring rate limits
- Missing error handling
- Excessive agent count
- Inadequate monitoring
- Not implementing retry logic for failed requests