Choosing the Right Scraper API Plan

Geonode Scraper API offers two pricing models:

• Request-Based pricing, where successful page extractions use requests from your available balance.
• Unlimited plans, where you pay a flat monthly price and your plan determines the number of concurrent threads.

This guide helps you decide which model is better for your workload.

Quick Comparison

If you already know which pricing model you need, you can go directly to the detailed guide:

Choose Request-Based Pricing If

Request-Based pricing is a good fit when your extraction volume changes from month to month or you do not need a large amount of concurrent processing.

Consider Request-Based pricing if:

• Your scraping volume is relatively small.
• Your workload is unpredictable.
• You only run extraction jobs occasionally.
• You want your pricing to be based on request usage.
• You are testing or starting a new scraping workflow.
• You do not need a high number of concurrent threads.

Request-Based pricing also includes a free tier with 1,500 requests per month, which makes it suitable for getting started without immediately choosing a paid plan.

Explore Request-Based Pricing

Choose Unlimited If

Unlimited plans are designed for workloads that require a larger amount of extraction capacity and predictable monthly pricing.

Consider an Unlimited plan if:

• You regularly process a large number of pages.
• You need to run many extractions in parallel.
• Your application can take advantage of higher concurrency.
• You want a predictable monthly cost.
• You regularly run large Batch or Crawl jobs.
• You do not want to manage a monthly request balance.

Unlimited plans are priced according to concurrent threads.

For example, the available plans provide different concurrency levels:

When all available threads are busy, additional work waits until a thread becomes available.

Explore Unlimited Pricing

Compare Common Workloads

Use your expected workload to determine which pricing model is more appropriate.

These recommendations are based on the difference between the two pricing models. Your actual choice should depend on both your request volume and the amount of parallel processing your application requires.

Consider Concurrency

Concurrency is particularly important when comparing plans.

A higher concurrency level allows more extraction tasks to run at the same time.

For example:

If your application processes URLs sequentially, increasing concurrency may not provide much benefit.

If your application can submit many extraction tasks at the same time, a higher-concurrency Unlimited plan can provide greater throughput.

Consider Batch and Crawl Jobs

Batch and Crawl jobs have their own job-size limits.

These limits apply to an individual job and are separate from the monthly request allowance on request-based plans or the unlimited request volume on Unlimited plans.

For Unlimited plans, the job limits are:

If a workload is larger than the maximum size of a single job, split it into multiple jobs.

Example Scenarios

You are testing the API

If you are testing a new extraction workflow or only need a small number of requests, start with Request-Based pricing.

The free tier provides 1,500 requests per month.

You scrape occasionally

If you only run extraction jobs when you need specific data and your monthly volume varies, Request-Based pricing can be a better fit.

You pay according to the request capacity you need instead of committing to a fixed Unlimited concurrency level.

You process thousands of pages regularly

If your application regularly processes thousands of pages and can run extraction tasks in parallel, an Unlimited plan may be a better fit.

The main consideration becomes how many concurrent threads your workload needs.

You run large Batch or Crawl jobs

If your application regularly runs large Batch or Crawl jobs, consider an Unlimited plan with enough concurrency and job capacity for your workload.

You can split larger workloads across multiple jobs when required.

A Simple Decision

Use this as a quick starting point:

You Can Change Plans as Your Workload Grows

Your initial choice does not need to be permanent.

You can start with Request-Based pricing while evaluating your workload. If your extraction volume grows or you need more parallel processing, you can move to an Unlimited plan.

Similarly, if your workload does not require high concurrency, a request-based plan may be more appropriate.

The best plan is the one that matches your actual workload rather than simply choosing the plan with the highest limits.

Related Guides

• Request-Based Pricing

• Unlimited Scraper API Pricing

• Extract a Single URL

• Extract Multiple URLs