What This Example Shows
- The “describe-it-and-go” workflow: natural language in, a fully composed multi-agent swarm out
- Four real use cases that each produce a different team shape from a one-line goal
- How to point a single endpoint at competitive teardowns, content pipelines, financial diligence, and security reviews
- Why this is the right starting point when you don’t yet know which swarm architecture you need
Why This Matters
Most teams stall at the same step: “I know what I want — write a competitive teardown of these five companies — but I don’t know which swarm type to pick or how to write the four agent prompts.” The Auto Swarm Builder removes that step. You describe the job in plain English; it decides how many agents to spawn, what each one specializes in, what swarm architecture they should run under, and then it executes the result. The pattern below is the same regardless of domain — what changes is the one-linetask you write.
Step 1: Setup
task strings.
Use Case 1: Competitive Teardown
You want a head-to-head analysis of five competitors. You do not want to hand-write five analyst prompts.Behind the scenes the builder typically produces a coordinator-plus-specialists shape for this kind of task — one specialist per company or one per analysis dimension. You don’t need to specify either; the task description is enough.
Use Case 2: Content Pipeline From a Single Brief
A marketer wants an entire piece of content produced from a one-line brief, not just a draft.Use Case 3: Investment Memo From a Ticker
A junior analyst wants a first-draft memo on a company without orchestrating a hierarchical swarm by hand.Use
max_loops=2 (or higher) when you want the swarm to critique and refine its own draft before returning. For a single-pass output, leave it at 1.Use Case 4: Security Review of a Proposed Architecture
An engineering lead has a design doc and wants a structured threat model without standing up a security team.Parsing the Response
The shape varies slightly byexecution_type, but the consistent pattern is:
return-agents or return-agents-objects.
When to Reach for This
| Scenario | Hand-built swarm | Auto Swarm Builder |
|---|---|---|
| You know the exact agent roles and prompts | Best fit | Overkill |
| You have a one-line goal and a deadline | Days of design work | One POST |
| You want consistent structure across many domains | You must template each | One endpoint, N tasks |
| You’re prototyping a new workflow | Slow to iterate | Iterate by editing prose |
| You’re handing the system to non-engineers | They can’t write prompts | They can write a goal |
The Cost Math
Pricing varies by model, agent count, andmax_loops — these are illustrative ranges.
| Workload | Human equivalent | Auto Swarm Builder |
|---|---|---|
| Competitive teardown of 5 companies | Analyst, 1-2 days, ~$1,200 | ~$1-3 per run, minutes |
| 1,500-word researched blog post | Freelancer, 1 day, ~$500 | ~$0.50-2 per run, minutes |
| Investment memo from a ticker | Junior analyst, 4 hours, ~$400 | ~$1-3 per run, minutes |
| STRIDE threat model | Security consultant, 1 day, ~$2,000 | ~$1-3 per run, minutes |
Common Pitfalls
The swarm picked a different architecture than I expected
The swarm picked a different architecture than I expected
The builder optimizes for the task description, not for a swarm type you had in mind. If you need a specific architecture (sequential, hierarchical, group chat, etc.), wire it up directly via
/v1/swarm/completions and skip the builder. The builder is for “I don’t know” cases.403 error
403 error
The endpoint is premium-only. Confirm your account tier on https://swarms.world/platform/account — Pro, Ultra, or Premium is required.
Output structure looks different on a second run
Output structure looks different on a second run
The builder generates new agents each call, which can shift the output schema. If you need stable downstream parsing, pin the design once and switch to a hand-built swarm. Use the builder as a design assistant; productionize the result.
Next Steps
- Auto Swarm Builder Execution Types to inspect or extract the generated agents
- Supply Chain Hierarchical Swarm for a hand-built hierarchical swarm you can model after a builder output
- Multi-Agent Router when you want the builder’s
return-swarm-router-configshape running in production