CURRENT | Vision

The Inverted Audience

The Indifferent Buyer

By Nora Kaplan— May 20, 2026

Feature image for article: The Indifferent Buyer

Websites are already publishing machine-readable permission files for autonomous visitors, and what they choose to show an entity that can't be charmed looks nothing like what they show humans. New commerce protocols define how an agent discovers a product, evaluates terms, and buys — no storefront, no emotional arc. One to two trillion dollars in annual e-commerce spending is impulse-driven, dependent on a buyer who feels something at the moment of decision. That assumption is starting to erode.

The Inverted Audience

The Indifferent Buyer

By Nora Kaplan— May 20, 2026

Websites are already publishing machine-readable permission files for autonomous visitors, and what they choose to show an entity that can't be charmed looks nothing like what they show humans. New commerce protocols define how an agent discovers a product, evaluates terms, and buys — no storefront, no emotional arc. One to two trillion dollars in annual e-commerce spending is impulse-driven, dependent on a buyer who feels something at the moment of decision. That assumption is starting to erode.

Two Consequences

Agent-First Design and the Fate of Human-Experience Moats

When AI agents evaluate your service, they don't see your logo, your landing page, or the feeling your brand evokes. They parse structured schemas and optimize for outcomes. Companies spent decades building moats out of human experience. Now the entity making the purchasing decision can't experience any of it. Differentiation migrates somewhere most product teams haven't learned to look.

Two Consequences

The Discovery Problem No One Has Solved

We've built protocols for how agents talk to each other. How they find each other remains wide open. Every discovery mechanism humans rely on — search rankings, app stores, social proof — was designed for a creature that browses and responds to emotion. Agents do none of that. The void is filling with provisional fixes. If the app store era taught us anything, it's that discovery layers don't stay neutral by accident.

Two Consequences

Agent-First Design and the Fate of Human-Experience Moats

When AI agents evaluate your service, they don't see your logo, your landing page, or the feeling your brand evokes. They parse structured schemas and optimize for outcomes. Companies spent decades building moats out of human experience. Now the entity making the purchasing decision can't experience any of it. Differentiation migrates somewhere most product teams haven't learned to look.

Two Consequences

The Discovery Problem No One Has Solved

We've built protocols for how agents talk to each other. How they find each other remains wide open. Every discovery mechanism humans rely on — search rankings, app stores, social proof — was designed for a creature that browses and responds to emotion. Agents do none of that. The void is filling with provisional fixes. If the app store era taught us anything, it's that discovery layers don't stay neutral by accident.

Two Consequences

Agent-First Design and the Fate of Human-Experience Moats

When AI agents evaluate your service, they don't see your logo, your landing page, or the feeling your brand evokes. They parse structured schemas and optimize for outcomes. Companies spent decades building moats out of human experience. Now the entity making the purchasing decision can't experience any of it. Differentiation migrates somewhere most product teams haven't learned to look.

Two Consequences

The Discovery Problem No One Has Solved

We've built protocols for how agents talk to each other. How they find each other remains wide open. Every discovery mechanism humans rely on — search rankings, app stores, social proof — was designed for a creature that browses and responds to emotion. Agents do none of that. The void is filling with provisional fixes. If the app store era taught us anything, it's that discovery layers don't stay neutral by accident.

Ground-Level View

Ghost Orders and Harissa Metadata — An E-Commerce Director Watches the Funnel Disappear

Ground-Level View

Ghost Orders and Harissa Metadata — An E-Commerce Director Watches the Funnel Disappear

The First Audience Shift

60,000 Repositories Now Ship Instructions Written for Agents, Not People

Codebases have always had two readers: the machine that compiles them and the person who maintains them. README.md belonged to the second. Now over 60,000 GitHub repositories include AGENTS.md, a file addressed to neither.

What goes into these files is remarkably familiar. Build conventions, security guardrails, workflow quirks. The kind of thing you'd explain to a new hire over coffee. Developers didn't invent new knowledge for their agent audience. They just redirected existing institutional memory toward a different reader.

That quiet redirection suggests the web is acquiring a second native audience, and infrastructure is already reshaping around it.

The First Audience Shift

60,000 Repositories Now Ship Instructions Written for Agents, Not People

Codebases have always had two readers: the machine that compiles them and the person who maintains them. README.md belonged to the second. Now over 60,000 GitHub repositories include AGENTS.md, a file addressed to neither.

What goes into these files is remarkably familiar. Build conventions, security guardrails, workflow quirks. The kind of thing you'd explain to a new hire over coffee. Developers didn't invent new knowledge for their agent audience. They just redirected existing institutional memory toward a different reader.

That quiet redirection suggests the web is acquiring a second native audience, and infrastructure is already reshaping around it.

IN SUMMARY

Rapid convergence:

Six months ago teams juggled separate instruction files for each coding agent. AGENTS.md is consolidating that fragmentation under Linux Foundation governance.

Modest returns:

ETH Zurich measured roughly 4% improvement from curated context files. The artifact matters as directional signal, not productivity story.

Convention stack:

AGENTS.md joins llms.txt and proposed agent-permissions.json, forming a layer where the web explicitly addresses visitors that aren't people.

Practice first:

Most agent behaviors remain undocumented. Like robots.txt in 1994, community habit is running well ahead of any formal specification.

Granular context:

OpenAI's repository contains 88 AGENTS.md files scoped to subdirectories, suggesting agent-readable context will become as fine-grained as code itself.