What is Agent Experience?
A practical definition of AX, where the term came from, the meanings it carries, and the questions it helps a team ask.
13 min read
Agent ExperienceGuides
Learn the basics first, then find practical help for the part of your product you want to improve.
Each guide builds on the one before, from what AX means to running a review of your own.
Say which AX you mean before you change anything.
13 min read
Place any problem on one path: orient, discover, act, collaborate, learn.
10 min read
Check how agents find and read your public pages.
11 min read
Write tools an agent can choose correctly, and tell apart from their neighbours.
8 min read
Scope one bounded job, so the later steps have a real workflow to work on.
7 min read
Gate consequential actions, and make sure what a person approves is what runs.
24 min read
Measure paths rather than scores, and know which claims a metric cannot support.
17 min read
Put the earlier steps together in a review of one real workflow.
9 min read
For anyone new to AX: what the term means, the framework this site uses, and what the people who do the work actually do.
A practical definition of AX, where the term came from, the meanings it carries, and the questions it helps a team ask.
13 min read
A five-part map of where agent work breaks (orient, discover, act, collaborate, learn), a four-step method, and a rubric that gives one job a profile across six tracks, each rated at one of four levels.
10 min read
Product AX, coding-agent AX, contact-centre AX, real-estate and insurance AX, and delegated-job AX: who uses each, and how to tell which one a page means.
12 min read
The agent experience role as public job postings and team pages describe it: the work, the skills, and how it differs from DevRel and DX.
12 min read
Not sure which one fits? The field map shows where each topic sits
For teams whose website, docs or sign-up an AI agent has to find and read before it can help anyone.
Clear structure, stable interactions, and meaningful labels help both people and agents navigate a site.
11 min read
What AI agents read, how to shape a page around a single decision, and how to keep the text true as the product moves.
8 min read
How the related disciplines connect, and the different product problem each one describes.
14 min read
What adoption and server-log studies show, and where the evidence is limited.
11 min read
Compare agent-facing standards by who reads them and what they help an agent do.
15 min read
What ARD is, how ard.json relates to MCP's ai-catalog.json, and a copy-pasteable manifest for a content site.
19 min read
Claim-later onboarding: the agent provisions a bounded resource now, and a person claims it later through a link.
17 min read
For teams that give agents tools, an API or written instructions, and want the agent to pick the right one and use it well.
The text around a tool affects whether an agent can find it, choose it, and use it well.
8 min read
A small, clearly separated catalogue is usually easier to choose from than a long list of overlapping actions.
8 min read
A run view should tell an operator whether to approve, retry, stop or escalate, and why.
7 min read
Seven patterns for large API surfaces: search first, schema on demand, rehearsal, truthful exits, an escape hatch, curated descriptions and a context budget.
14 min read
How to catch drift between what AGENTS.md, llms.txt, skills and MCP instructions say and what production does.
10 min read
For teams whose agents take real actions that a person has to approve, recover from, or pick up halfway.
A bounded workflow with a real edge shows you where judgement, context and control matter.
7 min read
Five things vanish at a handoff. A small structured record keeps intent, constraints, changed state, authority and evidence together.
8 min read
Consequential actions need a clear pause, real choices, and a way back into the work.
24 min read
Four fields turn an error into a decision: what failed, whether state changed, whether a retry is safe, and what input would fix it.
8 min read
Visible attempts show whether a system recovered cleanly or made people do more work.
8 min read
Seventeen named patterns for the human side of agent work, each with when to use it, how it fails and a live example.
21 min read
For teams that need to check how ready one job is, measure a change, and decide what to fix first.
Check one real job across six tracks, from finding the page to handing the result back, and get a profile instead of a score.
25 min read
Evaluate tool choice, handoffs, and recovery alongside the final result.
8 min read
The key agent experience metrics in four families, how to compare a change against a bare baseline, and the claims none of them can support.
17 min read
A repeatable way to inspect one meaningful workflow and choose the next product improvement.
9 min read
Six stages, a fixed task set, and a failure taxonomy that names the first decision that broke instead of the last error.
11 min read
Cloudflare, Lighthouse, Is Agentic, AFDocs scores, AXIS and the 2027.dev tier list: what each one scores, how, and what it cannot tell you.
16 min read
Seventeen annotated, public AX design decisions, mapped to the rubric, with a checklist and a template for recording your own.
16 min read