Getting Started
Introduction
What AX Framework is, who it is for, and how the documentation is organized.
AX Framework is an open framework for designing the part of a digital product that AI agents use. These docs explain how to apply it: the architecture, the implementation details, how to evaluate the result, and worked examples in four domains.
Why this exists
Agents are already using your product. Some browse it the way a person would, reading rendered pages and clicking controls. Others call whatever APIs they can find. Both approaches work some of the time and fail in ways that are hard to see: a misread price, a duplicate order, a task reported as done that never happened.
AX Framework treats these failures as design problems. The fix is rarely a smarter agent. It is a product that states what it can do, expresses facts as data, exposes actions as contracts, and reports outcomes that can be verified.
Who these docs are for
- Developers implementing capability manifests, action contracts, MCP servers, and error handling.
- Designers deciding which tasks agents should handle, where people need to approve, and how agent activity is shown.
- Product teams assessing readiness and prioritizing improvements.
You do not need to read everything. Most teams start with the Quick Start, skim Core Concepts, then jump to the section relevant to their next step.
How the docs are organized
| Section | What you'll find |
|---|---|
| Getting Started | The quick start and the vocabulary used throughout. |
| Architecture | Where the AX layer sits and how discovery, context, actions, and permissions fit together. |
| Implementation | Concrete guidance for metadata, action contracts, MCP, APIs, and errors. |
| Evaluation | How to assess readiness and test with real agents. |
| Examples | End-to-end designs for e-commerce, travel, SaaS, and support. |
The framework in one diagram
User interface
Pages, controls, visual feedback
Agent Experience layer
- Capability manifest
- Resource descriptions
- Action contracts
- Grants & approvals
- Receipts & status
Delivered through HTML + JSON-LD, an HTTP API, and/or an MCP server
The Agent Experience layer is a sibling of your user interface. Both sit on the same business logic. The UI serves people directly; the AX layer serves agents acting for people. Neither wraps the other.
Related
Last updated 2026-10-06. AX Framework documentation describes proposals unless a section is marked as an established standard.