Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Firecrawl (BYOK) icon

Firecrawl (BYOK)

Read your Firecrawl credit and token balance, queue status, recent activity, monitors and the status and errors of crawl and batch jobs with your own API key

Unify Dynamics LLC

Tools12read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderFirecrawlunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

How many Firecrawl credits do I have left?
Tools called
get_credit_usage
How many Firecrawl credits did I use each month?
Tools called
get_historical_credit_usage
How many Firecrawl extract tokens do I have left?
Tools called
get_token_usage
Is my Firecrawl queue backed up?
Tools called
get_queue_status
What Firecrawl jobs did my team run in the last day?
Tools called
get_team_activity
Which Firecrawl crawls are running right now?
Tools called
list_active_crawls

About

Firecrawl (BYOK) lets an AI assistant read your own Firecrawl data through the Firecrawl API with a key you supply (API key). Read-only: 12 tools (get_credit_usage, get_historical_credit_usage, get_token_usage, get_queue_status, get_team_activity, list_active_crawls, get_crawl_status, get_crawl_errors, get_batch_scrape_status, get_extract_status, list_monitors, list_monitor_checks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.firecrawl.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Firecrawl. Firecrawl and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Firecrawl API (api.firecrawl.dev) with a BYOK key; documentation: https://docs.firecrawl.dev/api-reference/introduction. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

12 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data12 tools
  • Get credit usageShow remaining credits, plan credits and the current billing period of the team.
  • Get historical credit usageShow credits used per billing month, optionally split by API key.
  • Get token usageShow remaining Extract tokens, plan tokens and the billing period of the team.
  • Get queue statusShow the team's scrape queue: jobs waiting and active, maximum concurrency and the most recent success.
  • Get team activityList API jobs of the last 24 hours (scrape, crawl, batch scrape, search, extract and so on) with job id, endpoint, time and target; filter by…
  • List active crawlsList crawls that are running right now for the team, with id and start URL.
  • Get crawl statusGet the status of a crawl job: state, pages total and completed, credits used and timing, plus the URL, title and HTTP status of each crawled page…
  • Get crawl errorsList the pages a crawl job failed on (URL, time, error) and the URLs blocked by robots.txt.
  • Get batch scrape statusGet the status of a batch scrape job: state, pages total and completed, credits used and timing, plus URL, title and HTTP status per page…
  • Get extract statusGet the status of an extract job: state, tokens used and expiry (the extracted data itself is returned as stored).
  • List monitorsList website change monitors with status, cron schedule, next and last run, estimated monthly credits and a summary of the last check.
  • List monitor checksList the runs (checks) of one monitor with status, trigger, timing and credits used.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-firecrawl.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 12 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-firecrawl.connectorbay.com/mcp
RESTPOST https://byok-firecrawl.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-firecrawl.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your API key in the X-Upstream-Key header (get one at www.firecrawl.dev).
  • Ask a question; the agent picks the right tool and answers from the live data.

Firecrawl connector: questions and answers

What is the Firecrawl connector?

Firecrawl (BYOK) lets an AI assistant read your own Firecrawl data through the Firecrawl API with a key you supply (API key). It is a hosted MCP server with 12 tools such as Get credit usage, Get historical credit usage, Get token usage, Get queue status, Get team activity, List active crawls, published by Unify Dynamics LLC. It is independent and not affiliated with Firecrawl.

How do I connect Firecrawl to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-firecrawl.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-firecrawl.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-firecrawl.json.

Do I need a Firecrawl account or API key?

Yes: this is a bring-your-own-key connector. Create a API key at https://www.firecrawl.dev/app/api-keys and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Firecrawl read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Firecrawl connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Mixpanel Lexicon (BYOK)

Read your Mixpanel Lexicon schemas (data dictionary), chart annotations and warehouse imports with your own service account (US data residency)

Live · MCP + REST8 tools

MLflow on Databricks (BYOK)

Read the MLflow experiments, runs, metric history, artifacts and model registry of your AWS Databricks workspace with your own personal access token

Live · MCP + REST11 tools

Mobilize (BYOK)

Read volunteer events, time slots and organizations from Mobilize with your own organization API key

Live · MCP + REST7 tools

Mode (BYOK)

Read your Mode workspace collections, reports, report runs and queries with your own Mode API token and secret (paid Mode plans)

Live · MCP + REST8 tools

Modrinth (BYOK)

Search Modrinth mods, plugins and other projects, read versions and authors, and your own account data with your own personal access token

Live · MCP + REST10 tools

Modrinth Reference (BYOK)

Read Modrinth category, loader and game version lists, licence texts, random projects, dependencies and look up projects, versions and files in bulk with your own personal access token

Live · MCP + REST11 tools

Documentation

Back to top

Firecrawl (BYOK) — connector documentation

  • MCP endpoint: https://byok-firecrawl.connectorbay.com/mcp
  • REST API: POST https://byok-firecrawl.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-firecrawl.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Firecrawl API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-firecrawl.connectorbay.com/health · Tool schemas: https://byok-firecrawl.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-firecrawl · agent@connectorbay.com

What Firecrawl (BYOK) is for

Firecrawl (BYOK) lets an AI assistant read your own Firecrawl data through the Firecrawl API with a key you supply (API key). Read-only: 12 tools (get_credit_usage, get_historical_credit_usage, get_token_usage, get_queue_status, get_team_activity, list_active_crawls, get_crawl_status, get_crawl_errors, get_batch_scrape_status, get_extract_status, list_monitors, list_monitor_checks). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.firecrawl.dev. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Firecrawl. Firecrawl and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "How many Firecrawl credits do I have left?"
  • "How many Firecrawl credits did I use each month?"
  • "How many Firecrawl extract tokens do I have left?"
  • "Is my Firecrawl queue backed up?"
  • "What Firecrawl jobs did my team run in the last day?"
  • "Which Firecrawl crawls are running right now?"

What it does

  • get_credit_usage: Show remaining credits, plan credits and the current billing period of the team.
  • get_historical_credit_usage: Show credits used per billing month, optionally split by API key.
  • get_token_usage: Show remaining Extract tokens, plan tokens and the billing period of the team.
  • get_queue_status: Show the team's scrape queue: jobs waiting and active, maximum concurrency and the most recent success.
  • get_team_activity: List API jobs of the last 24 hours (scrape, crawl, batch scrape, search, extract and so on) with job id, endpoint, time and target; filter by endpoint.
  • list_active_crawls: List crawls that are running right now for the team, with id and start URL.
  • get_crawl_status: Get the status of a crawl job: state, pages total and completed, credits used and timing, plus the URL, title and HTTP status of each crawled page (page contents are not returned).
  • get_crawl_errors: List the pages a crawl job failed on (URL, time, error) and the URLs blocked by robots.txt.
  • get_batch_scrape_status: Get the status of a batch scrape job: state, pages total and completed, credits used and timing, plus URL, title and HTTP status per page (contents not returned).
  • get_extract_status: Get the status of an extract job: state, tokens used and expiry (the extracted data itself is returned as stored).
  • list_monitors: List website change monitors with status, cron schedule, next and last run, estimated monthly credits and a summary of the last check.
  • list_monitor_checks: List the runs (checks) of one monitor with status, trigger, timing and credits used.

BYOK key

You bring your own Firecrawl API key (https://www.firecrawl.dev/app/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.firecrawl.dev over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Read-only: this connector never scrapes, crawls, searches or extracts, so it does not use credits. It reads balances and the state of jobs you already started.

Data sources

Live from the Firecrawl API (api.firecrawl.dev) with a BYOK key; documentation: https://docs.firecrawl.dev/api-reference/introduction. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Firecrawl. Firecrawl and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Firecrawl account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Firecrawl (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Firecrawl (BYOK) is. Firecrawl (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Firecrawl data: Read your Firecrawl credit and token balance, queue status, recent activity, monitors and the status and errors of crawl and batch jobs with your own API key. You bring your own Firecrawl API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Firecrawl call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.firecrawl.dev, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Firecrawl rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Firecrawl receives. The request we make on your behalf, including the key and the arguments, under Firecrawl's own terms and privacy policy. Firecrawl acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Firecrawl gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Firecrawl data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Firecrawl (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Firecrawl at any time to end all access.

Children. Firecrawl (BYOK) is a general-audience service operated by the adult using the assistant, under Firecrawl's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Firecrawl (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Firecrawl (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Firecrawl (BYOK) provides: Read your Firecrawl credit and token balance, queue status, recent activity, monitors and the status and errors of crawl and batch jobs with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Firecrawl credentials and only access data you are allowed to access. Firecrawl's terms apply to your use of Firecrawl; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Firecrawl. Firecrawl and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Firecrawl returns, lightly trimmed; it may be incomplete, delayed or changed by Firecrawl. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Firecrawl account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Firecrawl's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Firecrawl may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Firecrawl key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Firecrawl takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-firecrawl

Firecrawl (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Firecrawl (BYOK) never asks for them.

Get Firecrawl (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Firecrawl API key. Create one at https://www.firecrawl.dev/app/api-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Firecrawl. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Firecrawl.