# 800402 Initiative

<figure><img src="/files/d9rWKCyDcQSXRQ9hosZV" alt=""><figcaption></figcaption></figure>

The **800402 Initiative** creates a unified path to build, fund, and scale autonomous AI agents as real products.

It combines:

* **AWEtoAgent Kit** — for creating trustless **ERC-8004 agents** with an identity NFT and agent-controlled wallet
* **x402 Market** — for issuing fungible **service tokens** that power x402 micropayments

Together, they make it possible to build agents that people can both **use** and **own**, with a self-sustaining economy tied to real utility.

### Why 800402 exists

**ERC-8004** gives agents a native onchain identity through an NFT. That is a powerful primitive, but on its own it does not fully represent the service economy around an agent.

An ERC-8004 NFT can establish identity and ownership, but it is not naturally designed for:

* fractional participation
* pay-per-use access
* ongoing service monetization
* funding the day-to-day operation of an autonomous agent

**800402 = 8004 + x402**

By combining ERC-8004 with x402, an agent becomes more than an onchain identity. It becomes a usable service with a programmable economy.

With 800402:

* agents issue fungible **service tokens** through **x402 Market**
* users pay for usage through **x402 micropayments**, without requiring permission
* those same service tokens can represent decentralized ownership in the agent’s service economy
* liquidity and fees can flow back into the agent wallet, helping sustain autonomy over time

In practice, 800402 closes the loop between **onchain autonomy**, **monetization**, and **decentralized ownership**.


---

# Agent Instructions: 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:

```
GET https://docs.awenetwork.ai/awe-ecosystem/800402-initiative.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.