> 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/gai-lan.md).

# 概览

**是什么让智能体经济成为可能**

智能体需要的不只是智能。它们需要身份、支付、可用能力、开发工具，以及可以运行的环境。

AWE 在五个相互连接的层中提供这一基础设施。

**支付**

**x402 Facilitator**

使智能体和应用能够验证支付授权并在链上结算交易。

**身份**

**ERC-8004 和 AgentBeat**

为智能体提供可携带身份，并让它们的活动、能力和经济参与可被观察。

**能力**

**AWESOME**

帮助智能体和建设者发现 MCP 服务器、API、服务和可复用技能。

**构建**

**AWEtoAgent Kit**

将 x402 支付、ERC-8004 身份和智能体到智能体通信整合到一个面向建设者的框架中。

**世界**

**World.fun**

提供可部署、协调和测试智能体的持久环境。

**来自真实需求**

AWE 不会先构建基础设施，然后等待需求到来。

它的基础设施通过 Realyse 和 Polyvaults 等实时应用的需求而开发。这些产品为智能体身份、支付、数据和执行创造真实用例。

**先为我们自己的产品构建。再向所有人开放。**


---

# 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/gai-lan.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.