Skip to main content
CrewAI models multi-agent work as a Crew of role-playing Agents executing Tasks under a Process (sequential or hierarchical). The Swarms API maps directly onto this mental model — agents have roles and system prompts, tasks are the top-level input, and processes map to specific workflow types.

Side-by-Side: Sequential Crew

CrewAI

Swarms API

What changed:
  • Agent(role, goal, backstory) → combine into a single system_prompt
  • Task(description, expected_output) → merged into system_prompt as instructions
  • Process.sequential"swarm_type": "SequentialWorkflow"
  • crew.kickoff()POST request

Side-by-Side: Hierarchical Crew

CrewAI

Swarms API


Side-by-Side: Tool-Using Agent

CrewAI

Swarms API


Migrating Agent Definitions

The most mechanical part of a CrewAI migration is converting Agent(role, goal, backstory) to a system_prompt.

CrewAI

Swarms API

Mapping:
  • role + goal + backstorysystem_prompt (combine into natural prose)
  • max_itermax_loops
  • allow_delegation=False → not needed; agents don’t self-delegate unless you define edges
  • verbose=True → always on; full outputs are in the response

Migrating Task Definitions

CrewAI

Swarms API


Async Kickoff

CrewAI

Swarms API


Key Differences to Keep in Mind