Pricing Model
Sorry guys, I've really tried hard to understand the pricing model, but I'm confused by the overlap. I understood (maybe wrongly) that extract was like an upgraded / higher volume plan than Standard. I've paid for Starter Extract, but still I've exceeded my credits. Do I also need to upgrade my standard API subscription too to get more credits?
6 Replies
Hey there,
The Standard endpoints (/scrape, /crawl, /map, /batch/scrape, and /search) are completely separate from our Extract endpoint (/extract). Please read our documentation to learn more about each of these endpoints: https://docs.firecrawl.dev/.
Also, the Standard endpoints use credits (see https://www.firecrawl.dev/pricing), while the Extract endpoint uses tokens (see https://www.firecrawl.dev/extract#pricing).
Please send a message to help@firecrawl.com if you need to make any billing changes!
I've just paid for the standard endpoints too. I'm still a bit confused as to which I need but will continue to try and work it out. 2x $99/mth seems steep so assuming I don't need both and can achieve what I need with one or the other...
Our Standard endpoints also support extract-like functionality (check out our JSON scraping mode), which is supported by endpoints like /scrape and /crawl. You can also pair that with custom actions, which is a powerful combo!
If you don't end up needing your Extract plan, please help out to help@firecrawl.com and we will get you sorted out.
ok thanks Micah. Am investigating! I'm wondering if Extract replaces my use of Gemini in the workflow... Maybe I can use Extract to analyse the data instead of Gemini.
fyi trying to build an internal news aggregator, scraping news and company websites in our industry, and then using Gemini to prepare news style articles and a daily digest
For full transparency, most of our team's energy and focus in on the Standard endpoints, and trying to bring the best parts of Extract over to our Standard endpoints.
Because of this, I couldn't confidently advise you to migrate from a working Gemini solution to an Extract solution which is not getting all of the love it needs to work really well for you.
But if you are doing your extractions at a webpage-level instead of a website-level, then the JSON mode offered by our standard endpoints would be the way to go!
Thanks, will review!