Machine Readability
Can an agent parse your content reliably? Semantic HTML, JSON-LD structured data, stable element IDs, and text that doesn't live inside SVGs or canvas elements.
Most SaaS products weren't designed for agents. The agent opens your app, can't find the button, can't parse your pricing, doesn't know if its last action worked. We built the framework — and the evidence — to measure this.
New terminology for the agent era — definitions intended to become standard
The degree to which a software system can be successfully operated, navigated, and completed by an AI agent without human intervention. A property of the software, not of the agent — agentability describes what the product affords, not what the agent can do.
Usage: "The onboarding flow has low agentability — the CTA is inside an SVG with no accessible label." · Analogous to usability (for humans) and accessibility (for assistive technology), agentability extends the design quality space into a third dimension.
The discipline of designing, evaluating, and optimising software systems to be operable by AI agents. Agent Factors Engineering is the agent-era successor to Human Factors Engineering (HFE) — where HFE asks "can a human complete this task?", AFE asks "can an AI agent complete this task reliably, without ambiguity, without requiring human intervention?"
Context: HFE emerged in the 1940s as aviation and manufacturing demanded systematic design for human operators. As AI agents begin acting on behalf of humans across software interfaces, AFE addresses the same need at the agent layer. The two disciplines are complementary — a high AFE score does not substitute for good UX.
A composite metric (0–100) measuring a software product's agentability across 8 principles of the AFE framework. Computed as the mean of 8 equally-weighted principle scores. Scores above 45 indicate the product can support basic agent workflows without intervention. Scores below 20 indicate the product is effectively opaque to agents.
Baseline (2026): 100 top SaaS products audited. Mean score: 39.7. Highest: 51.8. No product exceeded 55. The agent-readable web does not yet exist.
Each principle reflects a question an AI agent asks when operating your software. A product that answers all eight clearly scores well. Most products fail at least four.
Can an agent parse your content reliably? Semantic HTML, JSON-LD structured data, stable element IDs, and text that doesn't live inside SVGs or canvas elements.
Is information broken into navigable, reference-able units? Agents can't scroll and skim — they need clear headings, sections, and scoped content blocks.
Can an agent operate your UI programmatically? Labeled buttons, keyboard-accessible controls, and form elements with predictable, stable attributes.
Does the product clearly tell agents what happened? Loading states, success/error feedback, and progress indicators agents can read without visual inference.
Does the product require minimal configuration to reach a working state? Agents struggle with open-ended choice — sensible defaults reduce decision burden.
Are next actions, links, and escalation paths unambiguous? Agents need clear signals about where a workflow ends, where it continues, and how to hand off to humans.
Is the interface free of hidden patterns agents can't see? Cookie walls, interstitials, invisible overlays, and dynamically injected elements that only appear on interaction.
Is critical information — pricing, rate limits, capabilities, constraints — explicitly published and machine-readable? Does the product offer agent-specific documentation?
Score ranges correspond to practical agent capability. A product in the Lagging tier can be partially automated but will require human intervention at key decision points.
Core workflows can be completed by an agent without intervention. Basic tasks succeed reliably. Minor friction remains.
Agents can complete some tasks but will hit friction points. Partial automation is feasible with workarounds.
Most agent workflows fail or require significant human intervention. The product was designed exclusively for human operators.
The product is effectively opaque to AI agents. No meaningful automation is possible without major architectural change.
Paste any public URL and get an Agentability Score in under 60 seconds. The audit checks all 8 principles and returns a principle-level breakdown.
Enter any publicly accessible URL — homepage, pricing page, or docs. Results are stored to track changes over time. Privacy policy.
Your Agentability Score will appear here.
Analysing page structure…
A site that scores products on transparency should itself be transparent. Here is everything an AI agent needs to know about this site.