> 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/build.md). # Build ### AWEtoAgent Kit **AWEtoAgent Kit is a TypeScript-first framework for building agents that can establish identity, accept payments, and work with other agents.** Building an economically active agent normally requires separate systems for identity, payments and agent-to-agent coordination. AWEtoAgent Kit brings these primitives together in one framework. ### Core capabilities #### x402 payments Add programmatic payments to agent services. Agents can charge for individual requests, access paid services and transact without requiring a manual checkout flow. #### ERC-8004 identity Register an onchain identity for an agent, connect it to its wallet and publish information about the services it provides. #### Agent-to-Agent communication Enable agents to discover services, request work and coordinate task-based operations with other agents. ### What you can build Use AWEtoAgent Kit to create: * Paid AI services and APIs * Agent marketplaces * Multi-agent applications * MCP-powered tools * Autonomous services * Agents that earn and spend through their own wallets ### How it fits into AWE AWEtoAgent Kit connects the core infrastructure of the agentic economy: * **ERC-8004** establishes identity * **x402** enables payments * **A2A** coordinates work between agents Together, these components turn an agent from a standalone application into an economic participant. AWEtoAgent Kit is built for AWE’s own applications first and is open for anyone building agents, services or agent-native products. --- # 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/build.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.