# Billing Information

### What is a billable request

A request is considered **billable** when it is successfully processed by the Website Unblocker service.

The following response statuses are counted as billable requests:

* **HTTP 200** – Successful response
* **HTTP 404** – Target not found
* **HTTP 499** – Request aborted by the customer

Requests aborted **after processing has started** are also billable and return **HTTP 200**. These aborts are initiated by the server when a request reaches the maximum allowed processing of **180 seconds**. These responses indicate that the Unblocker was able to receive, process, and complete the request flow.

***

### What is a non-billable request

A request is **not billed** when it fails due to access blocks or system-related errors.

The following responses are **not counted** as billable requests:

* **HTTP 403** – Access forbidden or blocked
* **HTTP 408** - Request Timed out
* **HTTP 5xx** – Internal or upstream system errors

Requests that fall into these categories are excluded from billing calculations.

***

#### Important notes

* Billing is based on request outcome, not on the content of the response
* A response does not need to contain the expected data to be considered billable
* Changes to request counting take effect only from their announced start date

For details about response statuses, please refer to the [Response Codes](/netnut-documentation/netnut-scraper-apis/website-unblocker/response-codes.md) documentation.

{% hint style="info" %}
This billing method applies to requests made on or after January 1st, 2026.
{% 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://help.netnut.io/netnut-documentation/netnut-scraper-apis/website-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.