> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/products/cn/web-unblocker/billing-information.md).
# 计费信息
### 流量使用量
[**网页解锁器**](https://oxylabs.io/products/web-unblocker) 两者都计入 **请求** 和 **响应流量**. **请求流量** 指发送到目标 URL 的数据，而 **响应流量** 指从目标 URL 接收的数据。
来自目标站点的所有带有 `2xx` 还是 `4xx` 状态码的响应均计为 **成功**.
其他所有响应均计为 **失败**.
有关响应代码的更多信息，请参阅 [**响应代码表**](/products/cn/web-unblocker/response-codes.md).
{% hint style="warning" %}
如果响应包含 `2xx` 还是 `4xx` 状态代码，而结果不包含预期信息，我们仍将其计为成功结果。
{% endhint %}
### 计费
您将按 **请求和响应流量都** 的 **成功** 提取的数据。
由于我们系统错误导致的抓取失败尝试（`5xx` 状态码）不会计入您的流量用量计算，因此您无需为此付费。
{% hint style="warning" %}
如果请求因您一侧的故障或错误而导致抓取失败，您仍将被计费。
{% endhint %}
请看下面的几个计费案例示例：
#### 案例示例 #1 - 成功的抓取尝试
您发起一个请求，网页解锁器需要三次尝试才能访问该网站。在这种情况下，您只会被收取最后一次尝试所消耗的流量，即成功的那次，本例中为 201 kB 的消耗流量。
#### 案例示例 #2 - 因我们的错误导致抓取失败
您向网页解锁器发起请求，由于我们的错误导致响应失败，例如，我们已达到内部重试上限。在这种情况下，您无需为该请求付费。
#### 案例示例 #3 - 因客户端错误导致抓取失败
您向网页解锁器发起请求，由于您一侧的错误导致响应失败。您将按该次尝试所消耗的流量计费，在这种情况下，为 51 kB 的消耗流量。
{% hint style="warning" %}
请注意，如果在抓取时应用了 JavaScript 渲染，由于网站为加载额外数据而执行的外部调用，作业的总流量可能会高于仅 HTML 文件大小。
{% endhint %}
---
# 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://developers.oxylabs.io/products/cn/web-unblocker/billing-information.md?ask=&goal=
```
`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.