---
id: "claim-email-is-a-shim"
type: "claim"
source_timestamps: ["00:06:48", "00:07:15"]
tags: ["protocols", "identity", "email"]
related: ["concept-layer-2-identity", "contrarian-email-is-terrible-for-agents", "question-email-survival", "entity-agentmail"]
confidence: "high"
testable: true
speakers: ["Nate B. Jones"]
sources: ["s52-orchestration-layer"]
sourceVaultSlug: "s52-orchestration-layer"
originDay: 52
---
# Email is a Temporary Shim for Agent Identity

## Claim
Email is currently used for agent identity only because it is universally accepted by human-built systems, not because it is technically suited for agents. It will eventually be replaced by native Agent-to-Agent (A2A) protocols.

## Confidence
High. Testable — track A2A protocol adoption vs. email-shim adoption over the next 24–36 months. The resolution path lives at [[question-email-survival]].

## Supporting context
[[concept-layer-2-identity]] details email's structural problems (brittle threading, anti-automation rate limits, poor signal-to-noise). [[entity-agentmail]] is the canonical email-as-shim startup. The contrarian framing is [[contrarian-email-is-terrible-for-agents]].

## Enrichment
- **Strongly supported**: M2M auth standards (OAuth 2.0 Client Credentials, mTLS) are widely preferred for agent identity in industry guides.
- **Counter**: AI-enhanced email (DKIM, ML verification) and tools like Clearout suggest email may persist for hybrid human-agent flows long-term.