> 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/shen-fen.md).

# 身份

## 身份

### ERC-8004 与 AgentBeat

**ERC-8004 为智能体提供链上身份，AgentBeat 则让智能体的活动变得可见。**

智能体需要一种一致的方式来识别自身、展示其服务，并与应用及其他智能体建立信任。

#### ERC-8004

ERC-8004 是一项以太坊标准，用于跨组织发现和评估智能体，无需预先建立信任关系。

它定义了三个链上注册表：

* **身份注册表**：为每个智能体提供一个基于 ERC-721 的标识符，并将其连接至包含元数据和服务端点的注册文件。
* **声誉注册表**：提供用于发布和检索智能体反馈的标准接口。
* **验证注册表**：记录独立验证智能体工作成果的系统所发出的请求与响应。

ERC-8004 提供身份与信任信号，但不处理支付；x402 提供独立的支付层。

#### AgentBeat

AgentBeat 是 AWE 面向 ERC-8004 智能体的分析与信息层。

它为智能体注册信息建立索引，并呈现有关活动、去中心化程度和验证情况的标准化信号。这有助于开发者和用户区分仅完成注册的智能体与展现出真实活动的智能体。

#### 两者如何协同运作

1. 智能体注册一个 ERC-8004 身份。
2. 其注册文件描述该智能体的能力和服务端点。
3. 声誉、验证和经济活动会产生更多信号。
4. AgentBeat 为这些信号建立索引，使其更易于查看。

#### 身份只是起点

注册只能证明某个链上身份确实存在，并不能保证该智能体处于活跃状态、值得信赖或足够安全。

AgentBeat 提供了可观察的背景信息，但用户和应用在授权智能体执行重要操作之前，仍应对其进行单独评估。

> ERC-8004 目前被标记为标准轨道草案（Draft Standards Track）提案，其规范与实现方式可能会继续演进。


---

# 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/shen-fen.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.