> For the complete documentation index, see [llms.txt](https://rwapact.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rwapact.gitbook.io/whitepaper/integrations-and-standards/erc-8004.md).

# ERC-8004

Explains how ERC-8004 provides agent identity and reputation context within RWAPACT, connecting agent identity to session validation and bounded authorization.

## Agent identity context

ERC-8004 is the agent identity and reputation registry standard referenced in the RWAPACT technology stack. It provides identity context for the protocol's autonomous agent model.

Identity context matters because agent actions are not automatically authorized. RWAPACT must identify the acting agent before it can evaluate the agent's current authority and proposed trade.

### Identity and session authority

ERC-8004 supplies the agent identity context. KSO evaluates whether that agent is authorized within an active session.

The RWAPACT session model includes:

* Agent ID and owner
* Session ID, start time, end time, and status
* Budget, amount spent, asset scope, and maximum trade size

KSO uses this session context to validate the current action. KPV then evaluates whether the specific trade complies with policy.

```
ERC-8004 identity context
           |
           v
KSO validates active session authority
           |
           v
KPV evaluates the proposed trade against policy
           |
           v
RWAPACT Pact authorizes or rejects execution
```

### Identity does not equal authorization

A valid agent identity does not grant unrestricted RWA trading authority. Final authorization remains the responsibility of the RWAPACT Pact.

For example, an agent may have a valid identity and active session. It may then request a trade outside the permitted asset scope or policy limits. The identity remains valid, while KSO or KPV can reject the action.

This model gives autonomous systems bounded authority. Identity establishes who is acting. Session validation and policy enforcement establish whether the current action is permitted.


---

# 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://rwapact.gitbook.io/whitepaper/integrations-and-standards/erc-8004.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.