> For the complete documentation index, see [llms.txt](https://docs.scraperapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scraperapi.com/resources/release-notes/may-2026/more-credits-higher-limits-introducing-new-growth-plans-on-scraperapi.md).

# More Credits, Higher Limits: Introducing New Growth Plans on ScraperAPI

We’re expanding ScraperAPI’s pricing plans with two new Growth plans designed for teams that need higher volume, better rates, and a faster path to scale — without needing to talk to sales.

### Meet the New Growth Plans

#### Professional — $975/month

Includes all ScraperAPI features and benefits plus:

* 10.5M credits/month
* :gift: Bonus 250K credits as a limited offer
* 300 threads
* PAY-AS-YOU-GO option included if you run out of credits

#### Advanced — $1,975/month

Includes all ScraperAPI features and benefits plus:

* 21.5M credits/month
* :gift: Bonus 500K credits as a limited offer
* 500 threads
* PAY-AS-YOU-GO option included if you run out of credits

These new plans are now available directly from the ScraperAPI dashboard under the new **Growth** pricing tab.

Now if you need **more than 5M of credits** you can:

* Upgrade instantly from the dashboard
* Access significantly higher monthly credit volumes
* Get better effective rates at scale

To make your growth more flexible, PAY-AS-YOU-GO remains available on Scaling, Professional, Advanced and Enterprise plans.

#### No Changes to Existing Plans

All current plans remain unchanged. These additions simply introduce a new Growth category for customers who need higher limits and a smoother path to scale.

You can explore the new plans now directly in your ScraperAPI dashboard.

<a href="https://dashboard.scraperapi.com/billing/subscription/plans" class="button primary" data-icon="play">Find the right Growth plan for your workload</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scraperapi.com/resources/release-notes/may-2026/more-credits-higher-limits-introducing-new-growth-plans-on-scraperapi.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
