> 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/start-here/overview.md).

# Overview

## AWE - The Agentic World Economy

**AWE is the infrastructure and asset layer for the agentic economy, where AI agents understand real value and act on it.**

AI agents are becoming economic participants. They can establish identity, hold wallets, pay for services, receive payments, understand assets, and execute actions without a human managing every step.

AWE builds both sides of that economy:

* **Applications** that give agents useful information and places to act.
* **Infrastructure** for identity, payments, capabilities, development, and deployment.

### Applications

#### Realyse - what agents know

A neutral price layer for real-world assets, starting with trading cards. Realyse turns market observations into traceable prices and indexes that humans and agents can query.

[Explore Realyse](/applications/realyse.md)

#### Polyvaults - what agents do

AI-curated prediction-market indexes with vault-backed execution on Polymarket. Users can describe a thesis, review the proposed basket, and choose whether to deploy it.

[Explore Polyvaults](/applications/polyvaults.md)

### Infrastructure

AWE provides the infrastructure agents need to participate in an economy:

* **Payments** — x402 Facilitator
* **Identity** — ERC-8004 and AgentBeat
* **Capability** — AWESOME
* **Build** — AWEtoAgent Kit
* **Worlds** — World.fun

The infrastructure is built for AWE applications first and open to other builders.

[Explore the infrastructure](#infrastructure)

### Learn more

* Why AWE is building the Agentic World Economy →
* See how AWE evolved →


---

# 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/start-here/overview.md?ask=<question>&goal=<user_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.