This comprehensive guide outlines production-grade best practices for using the Swarms API effectively. Learn how to choose the right swarm architecture, optimize costs, and implement robust error handling.Documentation Index
Fetch the complete documentation index at: https://docs.swarms.ai/llms.txt
Use this file to discover all available pages before exploring further.
Quick Reference Cards
Swarm Types
Available Swarm Architectures| Swarm Type | Best For | Use Cases |
|---|---|---|
AgentRearrange | Dynamic workflows | • Complex task decomposition • Adaptive processing • Multi-stage analysis • Dynamic resource allocation |
MixtureOfAgents | Diverse expertise | • Cross-domain problems • Comprehensive analysis • Multi-perspective tasks • Research synthesis |
SpreadSheetSwarm | Data processing | • Financial analysis • Data transformation • Batch calculations • Report generation |
SequentialWorkflow | Linear processes | • Document processing • Step-by-step analysis • Quality control • Content pipeline |
ConcurrentWorkflow | Parallel tasks | • Batch processing • Independent analyses • High-throughput needs • Multi-market analysis |
GroupChat | Collaborative solving | • Brainstorming • Decision making • Problem solving • Strategy development |
MultiAgentRouter | Task distribution | • Load balancing • Specialized processing • Resource optimization • Service routing |
AutoSwarmBuilder | Automated setup | • Quick prototyping • Simple tasks • Testing • MVP development |
HierarchicalSwarm | Complex organization | • Project management • Research analysis • Enterprise workflows • Team automation |
MajorityVoting | Consensus needs | • Quality assurance • Decision validation • Risk assessment • Content moderation |
Application Patterns
Specialized Application Configurations| Application | Recommended Swarm | Benefits |
|---|---|---|
| Team Automation | HierarchicalSwarm | • Automated team coordination • Clear responsibility chain • Scalable team structure |
| Research Pipeline | SequentialWorkflow | • Structured research process • Quality control at each stage • Comprehensive output |
| Trading System | ConcurrentWorkflow | • Multi-market coverage • Real-time analysis • Risk distribution |
| Content Factory | MixtureOfAgents | • Automated content creation • Consistent quality • High throughput |
Cost Optimization
Advanced Cost Management Strategies| Strategy | Implementation | Impact |
|---|---|---|
| Batch Processing | Group related tasks | 20-30% cost reduction |
| Off-peak Usage | Schedule for 8 PM - 6 AM PT | 50% cost reduction (Swarm Completions only) |
| Token Optimization | Precise prompts, focused tasks | 10-20% cost reduction |
| Caching | Store reusable results | 30-40% cost reduction |
| Agent Optimization | Use minimum required agents | 15-25% cost reduction |
| Smart Routing | Route to specialized agents | 10-15% cost reduction |
| Prompt Engineering | Optimize input tokens | 15-20% cost reduction |
Service Tiers
Choosing the Right Service Tier| Tier | Best For | Benefits | Considerations |
|---|---|---|---|
| Standard | • Real-time processing • Time-sensitive tasks • Critical workflows | • Immediate execution • Higher priority • Predictable timing | • Higher cost • 5-min timeout |
| Off-peak (Swarm Completions) | • Batch processing • Non-urgent tasks • Cost-sensitive workloads | • 50% cost reduction on tokens • 8 PM - 6 AM PT | • Only applies to Swarm Completions • Time window restriction |
Industry Solutions
Industry-Specific Swarm Patterns| Industry | Use Case | Applications |
|---|---|---|
| Finance | Automated trading desk | • Portfolio management • Risk assessment • Market analysis • Trading execution |
| Healthcare | Clinical workflow automation | • Patient analysis • Diagnostic support • Treatment planning • Follow-up care |
| Legal | Legal document processing | • Document review • Case analysis • Contract review • Compliance checks |
| E-commerce | E-commerce operations | • Product management • Pricing optimization • Customer support • Inventory management |
Error Handling
Advanced Error Management Strategies| Error Code | Strategy | Recovery Pattern |
|---|---|---|
| 400 | Input Validation | Pre-request validation with fallback |
| 401 | Auth Management | Secure key rotation and storage |
| 429 | Rate Limiting | Exponential backoff with queuing |
| 500 | Resilience | Retry with circuit breaking |
| 503 | High Availability | Multi-region redundancy |
| 504 | Timeout Handling | Adaptive timeouts with partial results |
Choosing the Right Swarm Architecture
Decision Framework
Use this framework to select the optimal swarm architecture for your use case:-
Task Complexity Analysis
- Simple tasks →
AutoSwarmBuilder - Complex tasks →
HierarchicalSwarmorMultiAgentRouter - Dynamic tasks →
AgentRearrange
- Simple tasks →
-
Workflow Pattern
- Linear processes →
SequentialWorkflow - Parallel operations →
ConcurrentWorkflow - Collaborative tasks →
GroupChat
- Linear processes →
-
Domain Requirements
- Multi-domain expertise →
MixtureOfAgents - Data processing →
SpreadSheetSwarm - Quality assurance →
MajorityVoting
- Multi-domain expertise →
Industry-Specific Recommendations
Finance
Financial Applications- Risk Analysis:
HierarchicalSwarm - Market Research:
MixtureOfAgents - Trading Strategies:
ConcurrentWorkflow - Portfolio Management:
SpreadSheetSwarm
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
Performance Benchmarks
Typical Performance Metrics| Metric | Target Range | Warning Threshold |
|---|---|---|
| Response Time | < 2s | > 5s |
| Success Rate | > 99% | < 95% |
| Cost per Task | < $0.05 | > $0.10 |
| Cache Hit Rate | > 80% | < 60% |
| Error Rate | < 1% | > 5% |
| Retry Rate | < 10% | > 30% |