> 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-scraper-api/usage-and-billing/billing-information.md).

# 流量与计费

### 流量使用量

网页爬虫API 统计以下内容的数量 **results**. **结果** 指从网页成功获取的不同内容实体（例如网页 HTML）。

* **成功结果** （计费）：目标站点中的所有结果，带有 `2xx` 还是 `4xx` 状态代码，会被计为成功结果并计费。
* **不成功结果** （不计费）：其他结果会被计为不成功结果，不会计费。

{% hint style="info" %}
状态代码 `429` （请求过多）不计费。当您超过速率限制时会发生这种情况。如果您经常遇到此情况，请联系您的客户经理以提高您的限额。
{% endhint %}

有关响应代码的更多信息，请参阅 [**响应代码表**](/products/cn/web-scraper-api/response-codes.md).

{% hint style="warning" %}
如果响应包含 `2xx` 还是 `4xx` 状态代码，而结果不包含预期信息，我们仍将其计为成功结果。
{% endhint %}

### 计费

您将按成功提取数据的结果数量计费。

由于我们系统错误导致的抓取失败尝试（`5xx` 和 `6xx` 状态代码）不会计入，您也不会因此被计费。

{% hint style="warning" %}
如果请求因您一侧的故障或错误而导致抓取失败，您仍将被计费。
{% endhint %}

请看下面的几个计费案例示例：

#### 案例示例 #1 - 成功的抓取尝试

您创建一个抓取任务，网页爬虫API 经过三次尝试后成功从网站获取到可用内容。您只会为最后一次成功的结果计费。

<figure><img src="/files/aaeb9774a8772ca197ff7909e2ba359ab9b17e34" alt="Case 1"><figcaption></figcaption></figure>

#### 案例示例 #2 - 因我们的错误导致抓取失败

您创建一个抓取任务，但由于我们的错误而失败，例如我们已达到内部重试上限。在这种情况下，您收到的结果不会计费。

<figure><img src="/files/e0316e7e2403702159c3178cc5b56b597e848e0a" alt="Case 2"><figcaption></figcaption></figure>

#### 案例示例 #3 - 因客户端错误导致抓取失败

您创建一个抓取任务，但由于您一侧的错误而失败。此结果将计费。<br>

<figure><img src="/files/26b6c4fca14df60a0c2bac67e4bd7a37bf0a671f" alt="Case 3"><figcaption></figcaption></figure>


---

# 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-scraper-api/usage-and-billing/billing-information.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.