> 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/july-2026/datapipeline-is-now-up-to-80-cheaper.md).
# DataPipeline is Now Up to 80% Cheaper
TL;DR: Running DataPipeline jobs now costs exactly the same as standard API requests. We've removed the 5× credit multiplier—no project fees, no request surcharges, just standard API pricing.
### The biggest update: standard API pricing
DataPipeline is now priced exactly like the standard API.
Every request follows the same credit schedule as the standard API across all request categories, including **Default, Premium, Ultra Premium, and JavaScript Rendering**. We've also removed the DataPipeline-specific pricing language throughout the product.
#### You'll notice:
* **Accurate cost estimates** in the **Start Scraping** review modal using the new pricing.
* **Max Cost** calculations based on the updated credit schedule.
The result is simple: you get all the benefits of DataPipeline without paying more than you would using the standard API.
### More than pricing: DataPipeline keeps getting better
Over the past few weeks, we've also rolled out a number of quality-of-life improvements designed to make large-scale scraping easier.
Recent highlights include:
* **Faster project creation** with a more discoverable "New Project" flow.
* **Better scheduling controls** directly from the Projects list.
* **A new Domain Credit Cost Estimator** to help predict costs before you scrape.
* **Improved validation and clearer feedback** for common issues like duplicate URLs.
* **Ongoing reliability, performance, and UX improvements** across the product, with clearer error messages.
### Why this matters
By removing the 5× pricing uplift, DataPipeline is now a cost-neutral way to run scheduled, parallelized scraping jobs. Combined with the recent [datapipeline improvements](https://docs.scraperapi.com/resources/release-notes/april-2026/datapipeline-update-10-larger-jobs-and-30-day-data-retention-policy), it's now the easiest and most cost-effective way to run reliable, recurring scraping workflows at scale.
**Same API pricing. Better tooling. Built for scale.**
Start a Datapipeline project Visit Documentation
---
# 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/july-2026/datapipeline-is-now-up-to-80-cheaper.md?ask=&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.