# Billing Information

### Traffic usage

[**Web Unblocker**](https://oxylabs.io/products/web-unblocker) counts both **request** and **response traffic**. **Request traffic** refers to data sent to the target URL, while **response traffic** refers to the data received from the target URL.

All responses from the target site with `2xx` or `4xx` status codes are counted as **successful**. 

All other responses are counted as **unsuccessful**. 

For more information about response codes, please refer to [**the Response Codes table**](/advanced-proxy-solutions/web-unblocker/response-codes.md).

{% hint style="warning" %}
If the response contains `2xx` or `4xx` status codes, and the result doesn’t contain expected information, we still count it as a successful result.
{% endhint %}

### Billing

You will be billed for **both request and response traffic** of **successfully** extracted data.

Failed attempts to scrape due to our system errors (`5xx` status codes) won’t be included in your traffic usage calculation, and you won’t be billed for that.

{% hint style="warning" %}
If a request results in a failed attempt due to a fault or error on your side, you will still be billed.
{% endhint %}

Please find a few billing case examples below:

#### Case example #1 - Successful scraping attempt

You make a request, and it takes three attempts for Web Unblocker to unblock the website. You will be billed only for the traffic consumed during the last attempt, which was successful, in this case, for 201 kB of consumed traffic.

<figure><img src="/files/RBwLxCYZstjIuCkkMrXQ" alt="Example 1"><figcaption></figcaption></figure>

#### Case example  #2 - Scraping failed due to our error

You make a request to Web Unblocker, and the response is unsuccessful due to our error, e.g., we have reached our internal retry limit. In this case, you will not be billed for this request.

<figure><img src="/files/igp1pfbR5TpvIIuDKYZn" alt="Example 2"><figcaption></figcaption></figure>

#### Case example  #3 - Scraping failed due to the client's error

You make a request to Web Unblocker, and the response is unsuccessful due to an error on your side. You will be billed for the traffic consumed during the attempt, which was unsuccessful, in this case, for 51 kB of consumed traffic.

<figure><img src="/files/LR7Y8KJTxWFgTX0StPko" alt="Example 3"><figcaption></figcaption></figure>

{% hint style="warning" %}
Please note that if JavaScript rendering is applied when scraping, total traffic for the job may be higher than the size of the HTML file alone due to the external calls the website is executing in order to load additional data.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://developers.oxylabs.io/advanced-proxy-solutions/web-unblocker/billing-information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.