What is an included allowance?

The allowance matters because it is a boundary, not a unit price or a promise of useful output. One plan may stop at the boundary, another may charge overage, and another may let the buyer purchase a separate pack. The real page capacity can also be smaller than the credit allowance when rendering, proxy, extraction, or target modes consume multiple credits. (ScraperAPI pricing and Firecrawl pricing, checked 2026-07-26.)

ScraperAPI includes one shared monthly credit allowance on each plan. A basic request uses one credit, while published target and feature modes can use more. Unused credits reset each billing period, lower plans stop at their limit unless upgraded, and pay-as-you-go is reserved for Scaling and above without a public unit rate. (ScraperAPI pricing and ScraperAPI credit rules, checked 2026-07-26.)

Browserbase includes several separate allowances rather than one interchangeable pool. Its plans list browser hours, Search calls, Fetch calls, Agent runs, and residential proxy traffic, with distinct additional-usage rules. Unused proxy data cannot be treated as extra browser time, and staying inside browser hours does not prove that proxy traffic is also inside its allowance. (Browserbase pricing, checked 2026-07-25.)

SerpApi includes a monthly number of searches. One successful search counts once regardless of whether it returns many results or none, while cached, errored, and failed searches do not count. Hourly throughput is published separately by plan, so the monthly search allowance does not grant unlimited use at one moment. (SerpApi pricing, checked 2026-07-26.)

Firecrawl uses a shared credit allowance across several differently metered products. A basic scrape or crawl page uses one credit, search is metered by result count, browser use by minutes, and other features have their own credit rules. Plan credits generally do not roll over, with stated exceptions for auto-recharge and some custom annual credits. (Firecrawl pricing and Firecrawl Browser Sandbox, checked 2026-07-26.)

Before signing up, write down each allowance’s exact unit, period, endpoint, and expiration rule. Check whether meters share a pool, what happens at exhaustion, which response statuses count, and whether concurrency or rate limits create a second boundary. Convert the expected workload into each vendor’s billable units before comparing allowance totals. (ScraperAPI pricing, SerpApi pricing, and Firecrawl pricing, checked 2026-07-26; Browserbase pricing, checked 2026-07-25.)