For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • What is Firecrawl?
  • Setting up Firecrawl
  • Using Firecrawl as a tool
  • Use cases
  • Next steps
Integrations

Firecrawl (web scraping)

Was this page helpful?
Previous

Exa (web search)

Next
Built with

Connect Firecrawl to let Agents scrape and extract content from web pages. Firecrawl is available as a built-in Agent tool, not as a Flow step.

What is Firecrawl?

Firecrawl is a web scraping service that converts web pages into clean, structured data. It handles JavaScript rendering, anti-bot measures, and data extraction.

Setting up Firecrawl

Firecrawl is available through platform keys, so you can use it without providing your own API key. If you want to use your own Firecrawl account:

  1. Sign up at firecrawl.dev
  2. Get your API key from the dashboard
  3. In Runtype, go to Settings → Integrations
  4. Find Firecrawl
  5. Enter your API key
  6. Click Save

Using Firecrawl as a tool

Enable the Firecrawl built-in tool when configuring an Agent. The Agent can then autonomously scrape web pages when needed.

The tool accepts:

  • url (required) — The page to scrape
  • formats — Output formats: markdown (default), html, rawHtml, screenshot, links
  • onlyMainContent — Strip navigation, footers, and ads (default: true)
  • waitFor — Milliseconds to wait for dynamic content before scraping

Use cases

  • Competitive intelligence: Monitor competitor pricing
  • Lead enrichment: Extract company data from websites
  • Content aggregation: Collect articles or listings
  • Research: Gather data from multiple sources

Next steps

  • Exa (web search) for finding pages to scrape
  • What are Agents? to build Agents that use Firecrawl