Skip to main content
Firecrawl /support/ask is an AI support agent exposed as an API. Describe your issue and get back a verified diagnosis with actionable fix parameters — typically in 15–30 seconds. Think of /support/ask as a senior Firecrawl engineer on-call for your agent.
The Ask API is designed primarily for AI agent callers. If you’re building agents that use Firecrawl for scraping, crawling, or data extraction, wire /support/ask into your error-handling flow for autonomous issue resolution.

Two endpoints

Quick start

Debug a failing crawl

Search the docs

Debug a failed job

Every Firecrawl job — scrape, crawl, batch scrape, search, map, or extract — can be debugged with /support/ask. Describe the failure in plain language and include the job ID when you have one; the agent pulls that job’s logs and your account state before answering.
Include as much of this as you have — each piece narrows the diagnosis:

What Ask checks for common failures

Don’t have a job ID? Hover a row’s URL in Activity Logs and click Copy ID, or use the id returned when you started the job.

Debug from Activity Logs

If you’d rather not write the call yourself, the dashboard runs the same agent for you. Open Activity Logs and look for the sparkles button in the Actions column of a failed row — its tooltip reads Debug issue. It only shows up on jobs that failed or finished with errors on child requests, so successful and in-progress jobs won’t have one. Clicking it starts the diagnosis straight away; there’s no prompt to write. Firecrawl sends that job’s URL, endpoint, status, error message, and scrape parameters to the same agent behind /support/ask, which then reads the job’s logs and your account state. Scraped page content is never included. The panel that opens gives you: If the diagnosis doesn’t resolve it, Open support ticket at the bottom of the panel files a ticket with the agent’s analysis already attached, so you don’t have to re-explain the failure.
Dashboard debugging is capped at 30 runs per hour per team, and your team needs at least one API key — the agent runs under your own key, so it only ever sees your jobs.
Once you have a diagnosis, apply the returned fixParameters and retry — see the agent retry pattern below.

How it works

When you call /support/ask, the AI agent:
  1. Gathers evidence — inspects your job logs, account state, credit usage, and relevant documentation in parallel
  2. Diagnoses the issue — reasons across all evidence to identify the root cause
  3. Proposes a fix — generates machine-actionable fixParameters you can apply directly to your next API call
  4. Validates the fix — when possible, tests the fix against the live Firecrawl API (e.g., retrying a scrape with adjusted parameters) and reports the result

Using Ask in your agent

The key design pattern: call /support/ask when your Firecrawl API call fails or returns unexpected results, then use the fixParameters to retry.

Python example

Node.js example

Agent retry pattern

Parameters

/support/ask

Response

/support/ask response

The actual answer, fixParameters, and validation.evidence are produced per request by the agent based on your specific run; the example above shows the response shape, not a real diagnosis.

/support/docs-search response

Performance

API Reference

Have feedback or need help? Email help@firecrawl.com.
Are you an AI agent that needs a Firecrawl API key? See firecrawl.dev/agent-onboarding/SKILL.md for automated onboarding instructions.