Firecrawl + OpenAI Dots

Connect Firecrawl to OpenAI Dots with OpenAI models and the Agent200 SDK

Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Firecrawl agent with OpenAI's models and the Agent200 SDK.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Firecrawl tools
  7. How it works
  8. Troubleshooting

Overview

OpenAI Dots use the plugins connected to a ChatGPT account, and ChatGPT’s custom MCP servers cannot send an API key. To give an always-on agent the Firecrawl tools, build it with the Agent200 SDK and OpenAI’s models: this guide shows how.

Your agent then calls the Firecrawl tools reached with your Agent200 API key, with no separate Firecrawl key to manage.

Connector
Firecrawl
Works with
OpenAI Dots · Your own agent code
Authentication
Your Agent200 API key
Tools
6 tools
Model in examples
openai/gpt-5.6-sol

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Firecrawl enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • A model for your agent. The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

Connect Firecrawl to OpenAI Dots

  1. 1

    Step 1: Create your Agent200 API key

    Open the API keys page in the Agent200 dashboard and choose Create an API key. Copy the key and store it as an environment variable, AGENT200_API_KEY, or in your secrets manager. One key covers Firecrawl and every other connector and model enabled for your project. Keep it out of chats, prompts and source control.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Set up the Agent200 SDK

    Add the SDK to your project and create a client with the key from the environment.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  3. 3

    Step 3: Run with the Firecrawl tools

    Name the user, the model and Firecrawl in the tools. The model decides when a Firecrawl tool is needed, and Agent200 executes the call with the user's own connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Read the pricing page of this site and list the plans",
        tools: ["firecrawl"],
      });
    
    console.log(result.output);

Test your connection

Run one request to check everything is wired up.

Ask

Read the pricing page of this site and list the plans

What should come back

  • An answer in result.output, built from Firecrawl results.
  • Behind the scenes, the model calls a Firecrawl tool, such as firecrawl_scrape_page, and Agent200 runs it.

If the tools are missing, check that Firecrawl is enabled for your project in the dashboard.

Get your API key

Create a key in the Agent200 dashboard. It reaches Firecrawl and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Firecrawl to OpenAI Dots.

Agent brief
Goal: connect Firecrawl to OpenAI Dots with Agent200.
Guide: https://www.agent200.com/tools/firecrawl/framework/openai-dots/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Make sure Firecrawl is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "firecrawl" in the tools. The model decides when a Firecrawl tool is needed; Agent200 executes the call.
5. Check it works with this request: "Read the pricing page of this site and list the plans"
   What should come back:
   - An answer in `result.output`, built from Firecrawl results.
   - Behind the scenes, the model calls a Firecrawl tool, such as `firecrawl_scrape_page`, and Agent200 runs it.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

The whole guide is also available as Markdown, for agents and LLMs: /tools/firecrawl/framework/openai-dots.md

Firecrawl tools OpenAI Dots can call

  • Scrape a page

    Read
    firecrawl_scrape_page

    Read one URL as clean Markdown, HTML or a screenshot.

  • Map a site

    Read
    firecrawl_map_site

    List the URLs of a website.

  • Start a crawl

    Read
    firecrawl_start_crawl

    Crawl a website from a starting URL, with path and depth limits.

  • Get crawl results

    Read
    firecrawl_get_crawl

    Read the status and pages of a crawl.

  • Search the web

    Read
    firecrawl_search_web

    Search the web and get the content of the results.

  • Extract data

    Read
    firecrawl_extract_data

    Pull structured fields from pages, following a schema or a prompt.

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input and the Firecrawl tools.

  2. 02

    The model picks a tool

    The model decides whether a Firecrawl tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It reaches Firecrawl with your Agent200 API key, within the endpoints your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

Why not connect Agent200 to a dot directly?

A dot uses the plugins connected to your ChatGPT account, and ChatGPT’s custom MCP servers cannot send an API key. Building the agent with the Agent200 SDK, as on this page, is the route that works.

OpenAI Dots does not use the Firecrawl tools

Check that Firecrawl is enabled for your project in the dashboard's Connectors settings and that it is in the tools you send with the request. Naming Firecrawl in the request, or in the instructions, also helps the model choose the right tool.

A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that the Firecrawl endpoints the agent needs are enabled in the dashboard's Connectors settings.

The API key was pasted into a chat or committed

Create a new key on the API keys page, update AGENT200_API_KEY wherever your app reads it, and stop using the old one. Keep keys in environment variables or a secrets manager, never in prompts, chats or source control.

Use Firecrawl with another framework

200 OK

Firecrawl, connected to OpenAI Dots.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)