Scraping API PricesAll products / Apify
Apify pricing
How Apify turns prepaid platform spend into resource and Actor usage, what remains workload-specific, and who it suits.
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 Apify counts
Nothing to count: Apify publishes no rate for a page fetch. Its 1 published billing meter prices 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
Apify 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 Apify 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 Apify plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Starter | $29.00 | n/a | n/a | 29 usd | 32 |
| Scale | $199.00 | n/a | n/a | 199 usd | 128 |
| Business | $999.00 | n/a | n/a | 999 usd | 256 |
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 |
|---|---|---|---|
| compute.unit | 0.2 usd | gb_hour | source |
What Apify does not publish
- Actor-specific event prices cannot be represented as one platform-wide multiplier.
- The effective monthly annual plan prices were not printed.
- Storage, data transfer, and proxy prices were not expanded because the comparable workload depends on the selected Actor.
What Apify is
Apify is a cloud platform for running Actors, which are packaged programs for web scraping, browser automation, and data workflows. Teams can write their own Actors or use offerings in Apify Store. This makes it materially different from Bright Data Web Scraper API, Zyte API, and ScrapingBee: those nearby choices lead with managed endpoints or predefined extraction services, while Apify leads with a runtime, storage, scheduling, proxies, and a marketplace of independently priced Actors. It is for developers and data teams that want a place to operate scraping jobs, not just a URL-in, response-out API. Sources: Apify pricing, Apify Store, Bright Data Web Scraper pricing, Zyte pricing, and ScrapingBee pricing, retrieved 2026-07-26.
How billing works
A paid plan provides prepaid platform spend rather than one universal request allowance. An Actor run can consume compute based on allocated memory and runtime, plus storage, data transfer, proxy traffic, and any Actor-specific event charges. Rented Actors may also carry their own charges. Retries create additional runs and therefore can consume additional resources. The common buying mistake is to treat a compute unit as the price of a scraped page. A compute unit measures computing resources, while the cost per useful record depends on the Actor, memory allocation, runtime, retries, transfer, proxy use, and event schedule. Sources: Apify pricing and Apify usage and resources documentation, retrieved 2026-07-26.
What Apify does not publish as one answer
- A platform-wide price per page, request, or delivered record, because Actors use different resources and may define different paid events. Sources reviewed: Apify pricing and Apify Store, retrieved 2026-07-26.
- One multiplier that converts an Actor’s advertised output into total platform cost. Source reviewed: Apify usage and resources documentation, retrieved 2026-07-26.
- Effective monthly figures for annual billing in the public plan table, although an annual discount is advertised. Source reviewed: Apify pricing, retrieved 2026-07-26.
- A universal success-only rule. Resources are consumed while a run executes, including runs that fail. Source reviewed: Apify usage and resources documentation, retrieved 2026-07-26.
Who it suits
Apify suits teams that need scheduled jobs, reusable code, datasets, proxies, and a choice between building and renting Actors. It is especially reasonable when engineers can test the exact Actor and record its real resource profile before committing volume. It is less suitable for procurement that needs one public success-only rate for a standardized request, or for a buyer unwilling to inspect Actor-specific charges. The reason is structural: Apify sells a programmable platform, so cost predictability comes from workload testing and configuration control rather than from one global unit. Sources: Apify pricing, Apify Store, and Apify usage documentation, retrieved 2026-07-26.
Answer
What Apify 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.A vendor page moved or could not be matched closely enough. Treat this as an older snapshot and check the vendor before buying.