Reference & Lookup Data · Integration
Firecrawl
Add Firecrawl to your product for your customers, and give your AI agents governed access to it.
Firecrawl at api.firecrawl.dev splits four operations that people often conflate: scrape returns one page, map returns a site's URLs quickly without fetching their content, crawl walks a site asynchronously, and extract pulls structured fields against a supplied JSON schema. Only scrape is synchronous; crawl and extract return a job id you poll, and crawl results are paginated with a next URL rather than an offset, so you keep following the cursor until it is absent. A scrape response is shaped by the formats you request (markdown, html, rawHtml, links, screenshot, json) and returns metadata including the resolved status code, so a page that soft-404s still comes back successful with a 404 in metadata. The onlyMainContent default strips navigation and footers, which is usually right but silently removes content when the useful text lives in a sidebar. Billing is per page credited, so a crawl's cost is a function of the limit you set rather than the request count. fastn holds each customer's own key, drives the polling, and keeps credit usage attributed per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Firecrawl key so page fetching in your product runs against their credits and their limits
Map a customer's documentation site and let them choose which sections to ingest before you crawl
Scrape a submitted URL to clean markdown and store it as the source for a knowledge base entry
Run a scheduled crawl over a customer's own site and flag pages whose content has changed
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent scrape a URL a user supplied and answer from the returned markdown rather than from memory, with every fetch audited per tenant
Have an agent map a site and report how many pages a full crawl would cost in credits before running it
Allow an agent to run a schema-based extract over a set of pages and report which fields came back empty
Example prompt
Scrape this pricing page with Firecrawl and tell me what the plan tiers and limits actually are.
Set up Firecrawl in 4 steps
- 01Enable the Firecrawl connector from your fastn dashboard.
- 02Have each customer authorise their own Firecrawl account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Firecrawl integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Firecrawl integration without building it. Your customers connect their own Firecrawl account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Firecrawl update is not your on-call problem.
- One integration serves your product and your agents. The same governed Firecrawl connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to Firecrawl, across other categories.
Salesforce
HubSpot
Notion
SnowflakeFirecrawl integration FAQ
How do I add a Firecrawl integration to my product?
Enable the Firecrawl connector in your fastn dashboard, then let each customer authenticate their own Firecrawl account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Firecrawl client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Firecrawl account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Firecrawl account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Firecrawl integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent scrape a URL a user supplied and answer from the returned markdown rather than from memory, with every fetch audited per tenant
Who maintains the Firecrawl integration?
fastn does. When Firecrawl changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Firecrawl lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Firecrawl results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Firecrawl is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Firecrawl integration?
A common starting point: let a customer connect their own Firecrawl key so page fetching in your product runs against their credits and their limits. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Firecrawl integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Firecrawl does not change your per-connector cost. You can start free with 3 connected accounts.
Add Firecrawl to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.