> 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/agentic-world-economy/master.md).

# Software learned to pay

For thirty years, the internet gave software a way to talk. In the last eighteen months, it gave software a way to pay.

That is the change underneath everything else. An AI agent that can hold a wallet, prove who it is, and settle a transaction without a human in the loop is no longer a tool. It is a participant. It buys data, rents compute, hires other agents, and gets paid for its own work.

The numbers already show it. More than 100 million x402 transactions settled on Base between Q3 2025 and Q1 2026. The x402 Foundation now counts Coinbase, Cloudflare, Stripe, AWS, Google, and Visa among its backers. Cloudflare switched on pay-per-request for the open web in July. More than 20,000 agents have registered an ERC-8004 identity across EVM chains.

Brian Armstrong put it in one line: "Every agent is going to need to pay for things. And there will be far more agents than humans."

We've been building for exactly this.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.awenetwork.ai/agentic-world-economy/master.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.