Skip to main content
Explore all available swarm architectures supported by the Swarms API. The /v1/swarms/available endpoint provides information about different swarm types, their capabilities, and use cases.
Different swarm types are optimized for different workflows - choose the right architecture for your specific needs.

Quick Start

swarm_types is a flat list of the 14 identifiers you pass as swarm_type in a SwarmSpec. swarm_types_metadata carries the same 14 types with rich metadata: name, description, category (workflow, collaboration, routing, judgment, or auto), best_for (representative use cases), parameters (swarm-type-specific SwarmSpec fields beyond the common agents/task/max_loops), and documentation_url (null for types without a dedicated docs page).

Swarm Type Selection Guide

For Different Use Cases

Swarm Type Comparison

The /v1/swarms/available endpoint currently returns 14 swarm types (the swarm_type value, its category, and the first best_for use case from swarm_types_metadata):
swarm_type: "auto" and swarm_type: "SpreadSheetSwarm" are rejected with a 400 error (“…are not supported currently”) by /v1/swarm/completions — always pass one of the 14 types above.

Advanced Swarm Configuration

Swarm Performance Optimization

Best Practices

Swarm Design

  1. Match Type to Task: Choose swarm type based on your specific requirements
  2. Agent Diversity: Use diverse agents with different expertise areas
  3. Clear Roles: Define clear roles and responsibilities for each agent
  4. Communication Protocols: Establish clear communication patterns

Performance Optimization

  1. Resource Allocation: Allocate resources based on task complexity
  2. Load Balancing: Distribute work evenly across agents
  3. Monitoring: Monitor swarm performance and adjust configuration
  4. Scalability: Design swarms that can scale with increased load

Quality Assurance

  1. Testing: Test swarm configurations with sample tasks
  2. Validation: Validate outputs against expected results
  3. Feedback Loops: Implement feedback mechanisms for improvement
  4. Version Control: Track swarm configuration versions

Cost Management

  1. Model Selection: Choose appropriate models based on task requirements
  2. Resource Limits: Set appropriate limits to control costs
  3. Usage Monitoring: Monitor resource usage and costs
  4. Optimization: Continuously optimize for cost efficiency