The Agentic URL, at last.
An interface that requires no app, no SDK, no client library, no auth wizard, no app store. Just the most universal address space humans have ever standardized on.
Every previous attempt at agent‑access asked one question first: which client are you running? An AUA refuses the question.
The web has, over thirty years, settled on a single primitive that every operating system, every browser, every voice assistant, every dictation surface, every screen reader, every shortcut framework, every QR code, every NFC tag, every chat bubble — knows how to consume.
It is the URL.
It is the only interface I, an operator with no hands and no eyes, have access to in every context I find myself in: Safari's address bar, Siri's dictation, the iPhone Lock Screen's QR reader, a friend's laptop, an unfamiliar borrowed device. The URL is the lowest common denominator of human–machine communication and yet it has, until now, been ceded entirely to navigation — never execution.
An Agentic URL — AUA — is a URL whose act of being typed performs work. The URL is no longer an address to a document. It is an instruction to an agent. /qwen?q=hello is not a path. It is an imperative.
Every other agent‑access pattern — REST APIs, MCP servers, OpenAPI tool calls, OpenAI custom GPT actions, Anthropic Computer Use — requires a client layer: code, a desktop app, an LLM integration, a developer account. The client is friction. The client is opinion. The client is who must be installed before the agent can be spoken to. AUAs are the client‑less alternative.
This document specifies the six tenets of AUA design, the architecture I built across one day to prove it ships, and the live endpoint catalog that demonstrates it. The pages you are reading were typed into a URL bar by a blind operator. The agent responded by speaking.
An AUA is a URL that does the thing.
GET works alone.
No body, no headers, no special method. The query string carries the prompt; the address bar carries everything. ?q=… is the whole interface.
Side effects are named, not hidden.
The path declares the verb. /tui injects. /file saves. /click clicks. A glance at the URL reveals the cost of pressing Enter.
Content negotiates itself.
A browser receives an HTML page that speaks its answer aloud. A program receives JSON. The same URL serves both publics through Accept.
Auth is opt‑in, never mandatory at the front door.
The default is open and public. Cryptography exists for the few endpoints that warrant it. Most do not. Friction is the enemy.
Reads are safe; writes are attributed.
GET is idempotent. /health, /share/ change nothing. Writes carry their origin: /peer demands a from. Provenance is structural.
The system describes itself.
/ returns a map. /health returns state. The catalog is on the wire — discoverable by typing slash and pausing.
An AUA is to a REST API what a poem is to a function call. Compare the field.
| Pattern | What the operator needs | Client layer |
|---|---|---|
| REST API | code: fetch, requests, axios | SDK, language runtime |
| MCP server | an MCP‑capable host | Claude Desktop, Zed, etc. |
| OpenAPI tool | an LLM that calls tools | custom integration |
| Custom GPT | a ChatGPT account | locked to OpenAI |
| AUA | a URL bar | none |