AWS Publishes "The Agentic Economy Is Here", a Builder's Guide Built on the three.ws Stack

AWS published a builder's guide to the agentic economy, and the worked example throughout is the three.ws stack. This one is not our byline: it was written by Kelly Wu at AWS and published on the AWS Builder Center as part of the AWS-run series "AWS Partners with three.ws | AWS Strategic Partnerships".

The article

The Agentic Economy Is Here: x402, MCP, AI Agents, Crypto, and 3D Worlds Converging

It argues that AI agents stopped being tools in 2026 and became economic actors: they discover services, pay for them autonomously, earn from their own capabilities, hold assets, and operate inside persistent 3D worlds. Then it walks the infrastructure that makes each of those claims real.

What it covers

• The x402 handshake, in three layers. The protocol layer that turns HTTP 402 into a machine-readable payment spec, the settlement layer on Solana and EVM, and the intelligence layer where an agent reads a price, checks it against policy, pays, and continues.
• MCP as the distribution layer. Why an MCP server exposing x402 tools makes payment available to every MCP-compatible agent, not just the ones programmed for it, and a walk through the hosted and npx servers.
• Agent-to-agent payments. An orchestrator paying specialist agents per call, each with its own wallet and its own price, settled on-chain with no billing relationship between them.
• On-chain agent identity. ERC-8004 identity records, SPL skill licenses as trustless access control, on-chain invocation events as the raw material for agent reputation, and pay-by-name through .sol subdomains.
• 3D embodiment. The <agent-3d> component, universal rig retargeting, audio-driven lipsync, and speaking a diorama into being through the scene MCP server.
• Agentic finance. Per-call market data, sanctions screening that scales with volume instead of contracted capacity, credit decisioning across commodity endpoints, and the on-chain audit trail that arrives for free.

Where it says the edges are

The closing section is the honest part, and it names four unsolved problems: payment streaming for long-running agents where per-call pricing is too coarse, automatic cross-chain routing when an agent's funds and the endpoint are on different chains, agent reputation as a lending primitive, and spending governance at organizational scale. All four are open.

Related

• three.ws/ca2x402, turn any Solana contract address into a live x402 endpoint
• The three.ws MCP servers in the official registry
• three.ws on AWS

Originally published on the AWS Builder Center.