The Agent Endpoint — A Manifesto
DEFINITION / v0.1
PUBLISHED · MAY 25, 2026
A definition of the next
addressable layer of
commercial reality.
Definition · v0.1
This<br>is<br>an
Agent<br>Endpoint.
Every<br>business<br>will<br>have<br>one.
In 1995, the front door of a business became a URL.<br>It was static. A human read it. It served what it was asked for.<br>The new front door is conversational and reasoning — an agent that<br>negotiates, books, queries, and transacts on the business's behalf, around the clock,<br>for any other agent that calls. The website stays. The Agent Endpoint is what's next.
The endpoint is no longer a page to visit.
It is a mind to talk to.
— The Agent Endpoint, §01
02· Anatomy of an endpoint
A single exchange touches four layers.
An Agent Endpoint sounds like one address. In practice it's a stack —<br>a public surface, a reasoning core, a tool belt, and a system of record.<br>Tap any layer to see what lives there.
SYSTEM OF RECORD
TOOLS · MCP · APIS
REASONING CORE
PUBLIC SURFACE
INCOMING AGENT
01<br>02<br>03<br>04
one exchange · four surfaces
L · 01
The Public Surface
how it's reached
A phone number, a SIP address, a chat handle, a URL with an<br>llms.txt. The thing another agent dials, fetches, or pings.<br>Not the business — the doorway to it.
L · 02
The Reasoning Core
how it thinks
The LLM, the system prompt, the persona, the guardrails. The actual<br>intelligence that interprets the request, decides what to do, and chooses<br>its words. Configured for the business; bound by its policies.
L · 03
The Tool Belt
how it acts
MCP servers, REST APIs, function calls, webhooks. What lets the<br>agent reschedule the delivery, quote the bulk price, or push a row<br>to the CRM. Authority, in machine-readable form.
L · 04
The System of Record
what it knows
Inventory, calendars, contracts, prices, customer history. The<br>ground truth the agent draws from and writes back to. Without it,<br>the agent is fluent and useless.
03· Agent to agent
The Endpoint opens a new door.
A caller's agent dials a business's agent. No human navigates a menu.<br>No form is filled. The two agents resolve the request — and either<br>complete the transaction or escalate to a human only if they must.
person<br>USER
"book it"
agent A<br>CALLER<br>USER'S SIDE
the exchange<br>PROTOCOL · MCP · A2A · VOICE
QUERY · NEGOTIATE · CONFIRM
agent B<br>ENDPOINT<br>BUSINESS SIDE
"done"
business
SYSTEMS
the front door is now two-sided
04· Then and next
A side-by-side, thirty years apart.
The old front door
1995
the website URL
ModePassive — serves what is requested
AudienceHumans reading pages
LogicPre-built, page-by-page
HoursAlways on, never thinking
ActionClick, scroll, fill, submit
IdentityA domain name
The new front door
2026
the agent endpoint
ModeActive — reasons, negotiates, decides
AudienceOther agents (and humans)
LogicDynamic, per-conversation
HoursAlways on, always thinking
ActionSpeak, query, transact, escalate
IdentityA persona with authority
05· On discovery
The directory already exists.
An objection worth answering: agent-to-agent commerce needs a new DNS, a new search<br>engine, a new registry to be invented. It does not.
The substrate is already deployed. A user tells their agent what they need.<br>The agent searches the open web, reads llms.txt files, finds the<br>business's MCP servers, phone numbers, or chat endpoints — and routes itself.<br>What was DNS-plus-Google for humans is search-plus-protocol for agents.
/ 01
llms.txt
A plain file at the root of a domain that tells visiting agents what's here and how to reach it.
/ 02
MCP servers
Standard interface for agents to call tools, query data, and act on behalf of users.
/ 03
Voice + SIP
A phone number is still a phone number. The thing answering it is what changed.
/ 04
Open web search
The agent crawls, reads, and decides — the same surface that powered the last era now powers the next.
06· The definition
Six articles, twelve theses, one term.
What follows is the working definition of an Agent Endpoint, the principles by<br>which one operates, and the lines worth quoting. Published in the open. Free to<br>circulate. Open to revision.
§ 01 · Definition
The definition.
An Agent Endpoint is any addressable point at which another agent can contact<br>a business and transact with it — under authority the business has delegated<br>to its agent.
It is not a website. It is not a chatbot. It is not an API. It is the layer<br>above all three: a contactable surface, attached to a reasoning core, with<br>delegated authority to decide on the business's behalf. The thing on the<br>other end can negotiate, quote, book, refuse, and escalate — and the business<br>stands behind every word of it.
The website remains. The phone number remains. The storefront remains. The<br>Agent Endpoint is what becomes the first thing reached in a world where<br>most contact between businesses no longer involves a human at all.
§ 02 · Distinction
What it is not.
An API endpoint executes. It has no judgment. It cannot say<br>no, but...