Scraping API PricesAll products / ScrapeGraphAI
ScrapeGraphAI pricing
How ScrapeGraphAI spends shared credits across scraping, extraction, search, crawling, and monitoring, with the remaining gaps.
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What ScrapeGraphAI counts
Nothing to count: ScrapeGraphAI publishes no rate for a page fetch. Its 6 published billing meters price other work.
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
ScrapeGraphAI bills failed fetches, so a 5% failure rate is billed work.
- ∅
Cash per month
Not comparable here
no published rate for request.basic
Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Not comparable. This product publishes no rate for this kind of work.
no published rate for request.basic
This is a finding about what ScrapeGraphAI publishes, not a gap in the data. It stays visible so a definitive market claim cannot quietly ignore it.
Published exact bills for comparable products
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every ScrapeGraphAI plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Starter | $20.00 | $17.00 | n/a | 10,000 credit | 3 |
| Growth | $100.00 | $85.00 | n/a | 100,000 credit | 15 |
| Pro | $500.00 | $425.00 | n/a | 750,000 credit | 50 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| request.markdown_convert | 1 credit | request | source |
| request.screenshot | 2 credit | request | source |
| request.ai_extraction | 5 credit | request | source |
| search.query | 2 credit | result | source |
| crawl.page | 1 credit | page | source |
| request.stealth | 5 credit | request | source |
What ScrapeGraphAI does not publish
- Failure billing is not published.
- No plan-specific overage rate is published. One-time top-up packs cost $5 for 1,000 credits, $40 for 10,000 credits, or $150 for 50,000 credits. Source: https://scrapegraphai.com/ (retrieved 2026-07-26).
- The crawl per-page meter depends on the selected output format and optional stealth.
- request.stealth uses per request for the Scrape and Extract request meter, but the single structured row cannot also express the source's per-result Search, per-page Crawl, and per-tick Monitor variants. Source: https://scrapegraphai.com/ (retrieved 2026-07-26).
What ScrapeGraphAI is
ScrapeGraphAI is a web data API covering page scraping, structured extraction, search, crawling, and change monitoring. Buyers can request formats such as Markdown or screenshots, ask for AI-structured output, start a multi-page crawl, or monitor a page on a schedule. It is for developers building data and agent workflows that need more than raw HTML retrieval. Sources: ScrapeGraphAI and ScrapeGraphAI pricing guide, retrieved 2026-07-26.
Firecrawl, Tavily, and ScrapingBee are the nearest named comparisons. Firecrawl also combines scraping and crawling, Tavily leads with web search and retrieval for agent applications, and ScrapingBee combines an HTML API with AI extraction and dedicated endpoints. ScrapeGraphAI’s distinguishing commercial feature is one credit balance with endpoint-specific formulas for formats, search results, crawl startup and pages, monitor ticks, detected changes, and optional stealth. Sources: Firecrawl pricing, Tavily API credits, ScrapingBee pricing, and ScrapeGraphAI, retrieved 2026-07-26.
How billing works
One unit is one credit. A Markdown conversion, screenshot, and AI extraction each use a different replacement rate. Search consumption multiplies by the number of results and changes when a prompt is supplied. A crawl adds a startup charge and then charges every page according to its selected scrape format. Stealth is additive, while JavaScript rendering itself has no extra credit charge. Monitoring charges the selected format on each tick and adds credits when a change is detected. The common buying mistake is to count only top-level API calls. Search result count, crawl page count, monitor frequency, detected changes, output format, and stealth can all expand usage behind one workflow. Source: ScrapeGraphAI, retrieved 2026-07-26.
What ScrapeGraphAI does not publish
- Whether failed scrapes, blocked pages, or empty extraction results consume credits. Source reviewed: ScrapeGraphAI, retrieved 2026-07-26.
- One fixed cost for a crawl page, because the selected output format and optional stealth remain part of the formula. Source reviewed: ScrapeGraphAI, retrieved 2026-07-26.
- One billing unit for stealth across every endpoint. The modifier can attach to a request, result, page, or monitor tick depending on the operation. Source reviewed: ScrapeGraphAI, retrieved 2026-07-26.
Who it suits
ScrapeGraphAI suits teams that want search, scrape, extraction, crawl, and monitoring under one balance and can model each workflow as a small formula. It is less suitable for buyers seeking one credit per top-level job or a public success-only billing rule. The reason is that its breadth creates multiple legitimate workload multipliers, and failure treatment remains unstated. Sources: ScrapeGraphAI and pricing guide, retrieved 2026-07-26.
Answer
What ScrapeGraphAI costs, what it publishes, and what it does not. Every figure sourced and dated.
Recorded 2026-07-26 from the vendor's own pricing page.We could not confirm this price in the latest check, so it remains visible for context but cannot lead a price ranking. Check the vendor's pricing page before buying.