> For the complete documentation index, see [llms.txt](https://docs.awenetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.awenetwork.ai/stp-han-yu/ji-chu-she-shi/zhi-fu.md).

# 支付

### **x402 Facilitator**

**AWE x402 Facilitator 帮助应用验证和结算买卖双方之间的程序化支付。**

[x402](https://docs.x402.org/) 是一种围绕 HTTP `402 Payment Required` 状态码构建的开放支付标准。它允许 API、应用和智能体服务针对单次请求收费，无需订阅或人工支付流程。

#### x402 支付的运作方式

1. 买方请求受保护的资源。
2. 服务器返回 `402 Payment Required`，并提供支付说明。
3. 买方准备支付授权，并将其随请求一同提交。
4. Facilitator 验证该授权，并在链上结算付款。
5. 付款确认后，服务器提供所请求的资源。

#### 为什么使用 Facilitator？

应用可以自行验证和结算 x402 支付。Facilitator 以服务形式提供此功能，从而减少每位开发者需要自行运行的区块链基础设施。

AWE Facilitator 提供以下标准端点：

* **验证**：确认支付授权是否有效。
* **结算**：将已授权的付款提交至链上。
* **状态处理**：将结果返回给应用，使其能够提供所请求的资源。

#### 当前支持范围

AWE Facilitator 目前支持 Base 上免 Facilitator 手续费的 USDC 支付，让卖方能够在无需支付额外 Facilitator 费用的情况下收到全部付款金额。标准网络费用仍可能适用。

#### 开发者可以将哪些内容货币化

Facilitator 可以支持以下项目的支付：

* API 请求
* AI 推理
* MCP 工具
* 智能体服务
* 数字内容
* 按使用量计费的应用

AWEtoAgent Kit 提供了一个更高层级的框架，用于将 x402 支付功能添加到智能体应用中。


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.awenetwork.ai/stp-han-yu/ji-chu-she-shi/zhi-fu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.