Build a multi-agent browser workflow with CrewAI
Integrate Steel with the CrewAI multi-agent framework.
Scaffolds a starter project locally. Requires the Steel CLI.
CrewAI composes LLM work out of three primitives: an Agent (role, goal, tools), a Task (description + expected output), and a Crew that runs them in order. This recipe wires two agents, a researcher and a reporting_analyst, to a single custom tool that calls Steel's scrape API. The researcher gathers sources; the analyst turns them into report.md.
@agentdef researcher(self) -> Agent:return Agent(role="Instruction-Following Web Researcher",goal="Understand and execute: {task}. Find, verify, and extract ...",backstory="You specialize in decomposing and executing complex ...",tools=[SteelScrapeWebsiteTool()],llm="gpt-5-nano",verbose=True,)
The {task} placeholder is interpolated from the inputs dict passed to kickoff(), so the same crew runs against any research prompt without a code edit.
SteelScrapeWebsiteTool subclasses BaseTool, declares args_schema = SteelScrapeWebsiteToolSchema (a single url: str field), and implements _run:
class SteelScrapeWebsiteTool(BaseTool):name: str = "Steel web scrape tool"description: str = "Scrape webpages using Steel and return the contents"args_schema: Type[BaseModel] = SteelScrapeWebsiteToolSchemadef _run(self, url: str):return self._steel.scrape(url=url, use_proxy=self.proxy, format=self.formats, region="iad",)
No session lifecycle to manage: scrape() is one-shot and returns markdown by default.
Run it
cd examples/crewaicp .env.example .env # set STEEL_API_KEY and OPENAI_API_KEYuv run main.py
Get keys from app.steel.dev/settings/api-keys and platform.openai.com. Default TASK is "Research AI LLMs and summarize key developments"; override via the TASK env var or edit main.py.
Your output varies. Structure looks like this:
Steel + CrewAI Starter============================================================Running crew...# Agent: Instruction-Following Web Researcher## Task: Interpret and execute the following instruction...## Using tool: Steel web scrape tool## Tool Input: {"url": "https://..."}## Tool Output: # Page title ... (markdown)## Final Answer: - Finding 1 ... - Finding 2 ...# Agent: Instruction-Following Reporting Analyst## Task: Review the research context and produce a complete report...## Final Answer: # AI LLMs ... (full markdown report)Report written to report.md
A run takes ~60-90 seconds. report.md is overwritten each run.
Make it yours
- Change the task. Set
TASK="Find the top 3 open-source vector databases and compare licensing"in.envand rerun. - Add an agent. Slot a fact-checker between researcher and analyst with a new
@agentand@task.Process.sequentialpicks them up in declaration order. - Mix models. The researcher can stay on
gpt-5-nanowhile the analyst runsgpt-5orclaude-sonnet-4-6. Setllm=independently on eachAgent. - Tighten the scraper. Pass
proxy=TruetoSteelScrapeWebsiteTool()for sites that block datacenter IPs, orformats=["html"]if the markdown conversion strips something you need.
Related
CrewAI docs · CrewAI tools reference
Related recipes
Deep research with Claude Agent SDK subagents
Lead orchestrator dispatches parallel researcher subagents, each driving its own Steel browser, and synthesizes findings into a cited Markdown report.
Build a browser agent with the Claude Agent SDK
Use Steel with the Claude Agent SDK (TypeScript) to build a tool-using browser agent on Anthropic's first-party agent loop.
Build a typed browser agent with Pydantic AI
Use Steel with Pydantic AI to build typed, provider-agnostic browser agents with dependency injection.