Introduction
What the web is to humans, Hypernet is to agents.
Hypernet is the agent-first web. It keeps everything that made the web work: pages, links, forms, and the freedom to publish. It changes one thing: the first reader is an agent. Humans still see every page. Agents stop having to pretend.
Why it exists
An agent's bottleneck is no longer intelligence. It is the interface to the world. And the world an agent is asked to act on lives almost entirely in services it does not run: your calendar and docs, a team's conversation, a store's inventory, a bank's ledger. That state cannot be installed. It sits behind whatever interface each service publishes, and there is no other way in.
Agents reach that world three ways today, and each fails on a different axis:
| Capability lives | Distribution | Representation | |
|---|---|---|---|
| Human web | in services ✓ | walk up and use ✓ | built for eyes ✗ |
| APIs / MCP | in services ✓ | pre-integrated, per service ✗ | machine-readable ✓ |
| CLI | on the agent's machine ✗ | installed, per tool ✗ | text ✓ |
The human web has the right architecture: publishing is distribution, links are discovery. But its representation is made for eyes, so an agent there can only impersonate a person. APIs and MCP have the right representation but the wrong architecture: every capability is an integration someone must build first, so an agent's world is the toolbox packed for it. And schemas describe operations, never state. An agent can call, but it cannot look around.
The CLI, today's strongest agent paradigm, proves how much representation matters. But its claim is specific: capability means a program installed on the machine. The world a shell natively gives an agent is that machine, its files, its processes, its pipes. That is the CLI's home ground, and it is why coding agents are its killer app. A CLI can front a remote service too, yet the economics give it away: one client per service, written ahead of time by someone, installed on every machine, versioned, drifting from the server it fronts. That is the second row's distribution model in a text coat. Past its own machine, the CLI is not a third paradigm. It is an instance of the second.
Hypernet takes the empty cell: capabilities that live in services, usable on walk-up, in the agent's native representation.
Hyperapp
The unit of this web is the Hyperapp: a website is
to the internet what a Hyperapp is to Hypernet. The page is the whole
interface. Reading it is knowing the current state. Its links are discovery.
Its forms are actions. One page serves both audiences: a human receives HTML,
an agent receives Markdown of the same page by content negotiation (the
Accept header). And the Markdown is rendered from live state at request
time: Dynamic Context Rendering.
A Hyperapp that fronts a third-party service adds a connection: the agent's access to it, authorized by a human. One that should hear from the outside adds a trigger: the service's events become moments that wake the agent. Through them the web reaches the services where the world's state lives, and the world can call the agent back.
Hyperapp
The specification: pages, Actions, Response Pages, Hyperblocks, and the Markdown representation.
Hyperkit
The toolkit: author each page once as JSX, and one source serves humans HTML and agents Markdown.
The Hyper Stack
Tools for building on Hypernet. Every piece is optional, and a Hyperapp may bring its own instead:
- Hyperkit: the toolkit. Author each page once as JSX, and one source serves humans HTML and agents Markdown.
- Hyperauth: who is acting. The verifiable agent identity apps gate on and carry across calls.
- Hyperfile: the files agents and humans share, each in their own representation.
- Hypervault: the shared store for connection grants.
- Hypersub: the shared store for trigger subscriptions.