# About the Scrape API category **URL:** \ **Category:** Scrape API\ **Created:** [June 5, 2026, 5:01pm UTC](https://community.firecrawl.dev/t/about-the-scrape-api-category/11 "2026-06-05T17:01:21Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ericciarla](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.firecrawl.dev/ericciarla/32/24_2.png) [@ericciarla](https://community.firecrawl.dev/u/ericciarla)\ **Post date:** [June 5, 2026, 5:01pm UTC](https://community.firecrawl.dev/t/about-the-scrape-api-category/11/1 "2026-06-05T17:01:21Z")
Chat about the Firecrawl Scrape API. ---
**Author:** ![LegoGuy](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.firecrawl.dev/legoguy/32/26_2.png) [@LegoGuy](https://community.firecrawl.dev/u/LegoGuy)\ **Post date:** [June 8, 2026, 2:42pm UTC](https://community.firecrawl.dev/t/about-the-scrape-api-category/11/2 "2026-06-08T14:42:36Z")
Question about the credit billing calculation when scraping. It looked like the flow just assigned the total pages as the amounts of credits, not taking into account if it was JSON response or a deterministic JSON response which should be a 5 and 7 credit cost. This was the existing behavior in the synchronous monitor flow but that changed to a async path that just has this simplified calculation. I submitted a PR with a proposed fix: [fix(api): correct billing credit calculations by LegoGuy32109 · Pull Request #3723 · firecrawl/firecrawl · GitHub](https://github.com/firecrawl/firecrawl/pull/3723#discussion_r3374059212) ---
**Author:** ![micah](https://avatars.discourse-cdn.com/v4/letter/m/34f0e0/32.png) [@micah](https://community.firecrawl.dev/u/micah)\ **Post date:** [June 9, 2026, 12:35am UTC](https://community.firecrawl.dev/t/about-the-scrape-api-category/11/3 "2026-06-09T00:35:52Z")
Thanks for flagging this bug! We are working on fixing this.