---
id: "concept-agent-web"
type: "concept"
source_timestamps: ["00:09:07", "00:10:21"]
tags: ["internet-evolution", "data-structures"]
related: ["concept-open-brain", "claim-notion-evernote-obsolete", "concept-semantic-search"]
definition: "The divergence of digital infrastructure into systems optimized for human consumption (visual layouts, folders) versus systems optimized for AI agents (APIs, vectors, semantic search)."
sources: ["s22-saas-replacement"]
sourceVaultSlug: "s22-saas-replacement"
originDay: 22
---
# The Agent Web vs. The Human Web

## Definition

The divergence of digital infrastructure into systems optimized for human consumption (visual layouts, folders) versus systems optimized for AI agents (APIs, vectors, semantic search).

## The Fork

Quoting the speaker (see [[quote-internet-forking]]): *'The internet right now is forking.'* On one side is the **Human Web** — fonts, layouts, cover images, nested folders, hierarchical pages. Apex predators here include [[entity-notion-d22]], Evernote, Apple Notes, traditional browsers. On the other side is the emerging **Agent Web** — APIs, structured data, vector embeddings, [[concept-semantic-search]], and protocols like [[concept-model-context-protocol]].

## Why This Distinction Matters

Trying to use Human Web tools to feed AI agents is a structural mismatch (see [[claim-notion-evernote-obsolete]] and [[contrarian-notion-is-dead]]). An agent does not care about a beautifully styled Notion dashboard. It needs:

- Flat, queryable data — not nested toggles.
- Mathematical similarity over high-dimensional vectors — not visual scanning.
- Programmatic access via APIs and MCP — not OAuth-gated UIs.

The right move is therefore not to bolt a chatbot onto a legacy note tool, but to build infrastructure that is **native to the Agent Web** from the ground up — the [[concept-open-brain-d22]].


## Related across days
- [[concept-agentic-economy]]
- [[concept-agent-discovery]]
- [[concept-agent-callable-primitive]]
