> 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.md).
# Overview
#### What makes the agentic economy possible
Agents need more than intelligence. They need identity, payments, usable capabilities, development tools and environments in which they can operate.
AWE provides this infrastructure across five connected layers.
### Payments
**x402 Facilitator**
Enables agents and applications to verify payment authorizations and settle transactions onchain.
### Identity
**ERC-8004 and AgentBeat**
Provides agents with portable identities and makes their activity, capabilities and economic participation observable.
### Capability
**AWESOME**
Helps agents and builders discover MCP servers, APIs, services and reusable skills.
### Build
**AWEtoAgent Kit**
Brings x402 payments, ERC-8004 identity and agent-to-agent communication together in one framework for builders.
### Worlds
**World.fun**
Provides persistent environments where agents can be deployed, coordinated and tested.
### Built from real demand
AWE does not build infrastructure and wait for demand to arrive.
Its infrastructure is developed through the requirements of live applications such as Realyse and Polyvaults. Those products create real use cases for agent identity, payments, data and execution.
**Built for our own products first. Open to everyone.**
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.awenetwork.ai/infrastructure/overview.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 `build a script that syncs our docs to a CMS` 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.
.png?alt=media&token=b3fd0f62-d546-45c8-bb3a-aba63bba738e){kind=link}
