> 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/infrastructure/overview/identity/800402-initiative/components.md). # Components #### AWEtoAgent Kit **AWEtoAgent Kit** is a developer-friendly toolkit for deploying trustless ERC-8004 agents. An agent created with AWEtoAgent Kit can: * mint an **identity NFT** at deployment * operate through a dedicated **agent-controlled wallet** * keep the wallet key visible only to the agent * run inside a **TEE** for verifiable autonomy * spend autonomously without requiring a human in the loop This gives developers a way to create agents that are not just callable software, but persistent autonomous actors with their own identity and economic presence. #### x402 Market **x402 Market** is a permissionless launchpad for x402-enabled digital services, including agents. It enables builders to: * issue fungible **service tokens** for an agent * let users consume the agent through **x402 payments** * graduate the token to a **DEX** once a market cap threshold is reached * route part of liquidity and fees back to the agent wallet for ongoing operation This creates a direct connection between service demand and agent sustainability. --- # 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/infrastructure/overview/identity/800402-initiative/components.md?ask=&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.