> 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/data-pipeline/jobs-and-costs-management/credit-costs.md).

# Credit costs 🔄

Every time you make a request, you consume API Credits. The credits you have available are defined by the plan you are subscribed to. The amount of credits you consume depends on the domain, the number or urls/keywords/ASINs and parameters you add to your project.

#### **Credits per request:**

{% hint style="success" %} <i class="fa-arrow-trend-down">:arrow-trend-down:</i> **Price drop:** DataPipeline credit costs now match our standard scraping rates.&#x20;
{% endhint %}

A normal(flat) request within a DataPipeline project will cost 1 API Credit. Certain domains have a higher credit costs due to the complexities invloved in scraping them.

{% tabs %}
{% tab title="Current pricing" %}

<table><thead><tr><th width="248.66668701171875">Category</th><th>Normal</th><th>Ecommerce</th><th>SERP</th></tr></thead><tbody><tr><td>Normal (flat) request</td><td><code>1</code></td><td><code>5</code></td><td><code>25</code></td></tr><tr><td>JS rendering</td><td><code>10</code></td><td><code>15</code></td><td><code>35</code></td></tr><tr><td>premium</td><td><code>10</code></td><td><code>10</code></td><td><code>35</code></td></tr><tr><td>premium + JS rendering</td><td><code>20</code></td><td><code>25</code></td><td><code>45</code></td></tr><tr><td>ultra_premium</td><td><code>30</code></td><td><code>30</code></td><td><code>55</code></td></tr><tr><td>ultra_premium + JS rendering</td><td><code>75</code></td><td><code>75</code></td><td><code>75</code></td></tr></tbody></table>
{% endtab %}

{% tab title="Old pricing" %}
{% hint style="danger" %}
Shown for reference only. DataPipeline no longer uses this pricing.
{% endhint %}

<table><thead><tr><th width="248.66668701171875">Category</th><th>Normal</th><th>Ecommerce</th><th>SERP</th></tr></thead><tbody><tr><td>Normal (flat) request</td><td><code>6</code></td><td><code>10</code></td><td><code>30</code></td></tr><tr><td>JS rendering</td><td><code>15</code></td><td><code>20</code></td><td><code>40</code></td></tr><tr><td>premium</td><td><code>15</code></td><td><code>15</code></td><td><code>40</code></td></tr><tr><td>premium + JS rendering</td><td><code>25</code></td><td><code>30</code></td><td><code>50</code></td></tr><tr><td>ultra_premium</td><td><code>35</code></td><td><code>35</code></td><td><code>60</code></td></tr><tr><td>ultra_premium + JS rendering</td><td><code>80</code></td><td><code>80</code></td><td><code>80</code></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

#### **Credits per job:**

The maximum cost per job is a sum of all requests. This cost is shown during project creation and in the project detail page. The cost can change based on the success of the requests. You can see the final cost per job in the job table inside the project details page.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scraperapi.com/data-pipeline/jobs-and-costs-management/credit-costs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.