---
id: "contrarian-email-is-terrible-for-agents"
type: "contrarian-insight"
source_timestamps: ["00:06:48", "00:07:15"]
tags: ["protocols", "identity", "contrarian"]
related: ["concept-layer-2-identity", "claim-email-is-a-shim", "entity-agentmail", "question-email-survival"]
challenges: "Challenges the pragmatic trend of using email as the default identity layer for AI agents."
sources: ["s52-orchestration-layer"]
sourceVaultSlug: "s52-orchestration-layer"
originDay: 52
---
# Contrarian: Email is a Terrible Protocol for Agents

## What it challenges
The pragmatic trend of using email as the default identity layer for AI agents — including the entire business model of [[entity-agentmail]] and similar tools.

## The contrarian insight
While many startups are building tools to give agents email addresses so they can interact with the web, the speaker argues this is fundamentally flawed. Email is a **human-centric protocol** with:
- brittle threading
- anti-automation rate limits
- poor signal-to-noise ratios for context windows

It is a *shim* that will inevitably be replaced by native machine-to-machine protocols (OAuth 2.0 Client Credentials, mTLS, A2A standards, MCP-based discovery). Heavy architectural bets on email are highly risky.

See [[claim-email-is-a-shim]] for the explicit claim and [[concept-layer-2-identity]] for the broader layer context.

## Counter-perspective
AI-augmented email (DKIM, ML verification, tools like Clearout reaching ~99% accuracy) may keep email viable in **hybrid human-agent worlds**, even after dedicated A2A protocols emerge. This is the live debate captured in [[question-email-survival]].
