> 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/xiang-mu-jie-shao/zhi-neng-ti-shi-jie-jing-ji.md).

# 智能体世界经济

软件学会了支付

几十年来，互联网为软件提供了沟通方式。现在，它也为软件提供了支付方式。

一个能够持有钱包、建立身份，并在无需人类完成每一步的情况下完成交易结算的 AI 智能体，不再只是工具。它可以成为经济参与者。

它可以购买数据、支付算力费用、调用其他智能体，并为自己的工作收款。

**智能体经济需要什么**

智能体需要回答五个实际问题：

1. **我是谁？** - 身份与发现。
2. **我如何支付或收款？** - 互联网原生结算。
3. **我可以使用什么？** - 工具、服务、API 和技能。
4. **某个东西值多少钱？** - 可靠且可追溯的资产信息。
5. **我可以在哪里行动？** - 将信息转化为结果的应用。

**轨道与需求**

仅有基础设施无法创造经济。经济需要有用的活动。

因此，AWE 同时构建轨道，以及为这些轨道创造需求的应用。

* **Realyse** 为智能体提供现实世界资产的中立价格层。
* **Polyvaults** 为智能体和用户提供可根据市场论点行动的场所。
* **x402 和 ERC-8004** 提供支付与身份。
* **AgentBeat** 让智能体活动可被观察。
* **AWESOME** 帮助智能体发现能力。
* **AWEtoAgent Kit** 为开发者提供实用的构建方式。
* **World.fun** 提供可部署和测试智能体的持久环境。

原则很简单：根据真实产品需求构建基础设施，然后向所有人开放。

**从世界到经济**

AWE 最初提出的问题是：许多智能体能否在持久环境中协同工作？

Autonomous World Engine 和 World.fun 证明了它们可以。这项工作也暴露了下一个约束：智能体可以协同，但无法交易。

AWE 因此扩展，开始构建这一经济层。

**世界是彩排。经济才是演出。**


---

# 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/xiang-mu-jie-shao/zhi-neng-ti-shi-jie-jing-ji.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.