> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Firecrawl

> Connect Firecrawl to xpander and give agents its 6 actions: how to sign in and connect it, and which actions to hold for approval.

<Badge color="blue">HTTP API connector</Badge>

An HTTP API described by an OpenAPI spec, not an MCP server. Calls go to `https://api.firecrawl.dev/v1` and carry a credential xpander supplies, so there is nothing to paste.

## What the skill can do

API connector: 6 actions, as they appear in the skill panel. 5 of them create, change or delete something in Firecrawl; mark those under **These actions need approval** when you add the skill to an agent.

* **Crawling system** (2): Get Crawl Job Status, Initiate Website Crawl
* **Batch processing** (2): Batch Scrape Multiple URLs, Extract Webpage Content
* **Site mapping** (1): Retrieve Website Links
* **Search service** (1): Web Content

## Connect Firecrawl

In Xpander Chat, open the agent's settings, click **Add skill**, and search for **Firecrawl**. The connect dialog asks for a connection name and whether the connection is for the **Organization** (one shared account) or **Personal** (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person's own sign-in; see [whose credential a shared agent uses](/use/agents/permissions#whose-credential-a-shared-agent-uses).

Firecrawl connects with **Sign in with Firecrawl**: you authorize in the browser and xpander stores the OAuth token; the agent never sees it, and the token is attached at the moment a skill is called.

Calls go to `https://api.firecrawl.dev/v1`.

## Give an agent the Firecrawl skill

Once Firecrawl is connected, any agent you can edit may be given the skill: open the agent's settings, click **Add skill**, and choose **Firecrawl**. Enable only the action groups the agent needs, and mark the actions that should wait for a named person's sign-off under **These actions need approval**. Which skills exist for your organization, and who may add them, is decided by your admins; see [Skills](/use/skills).

## Related Resources

* [Skills](/use/skills)
