---
id: "concept-layer-2-identity"
type: "concept"
source_timestamps: ["00:05:29", "00:08:02"]
tags: ["identity", "protocols", "communication"]
related: ["concept-the-agent-stack", "claim-email-is-a-shim", "entity-agentmail", "entity-model-context-protocol", "contrarian-email-is-terrible-for-agents", "question-email-survival"]
definition: "The transitional infrastructure layer providing agents with verifiable identities and the ability to send/receive messages."
sources: ["s52-orchestration-layer"]
sourceVaultSlug: "s52-orchestration-layer"
originDay: 52
---
# Layer 2: Identity & Communication

## Definition
The transitional infrastructure layer that gives agents verifiable identities and the ability to send and receive messages.

## Why agents need their own identity
For an agent to function as an independent entity on the internet, it must be able to send and receive messages, authenticate with services, and hold a verifiable identity recognized by other systems.

## The current pragmatic shim: email
The short-term solution has been to treat **email addresses as identity**. Startups like [[entity-agentmail]] (a $6M seed) let developers programmatically create fully-threaded inboxes for agents, so the agent can sign up for SaaS products and receive verification codes.

But email is fundamentally a human-centric protocol. It suffers from:
- brittle threading
- rate limits designed to block automated spam
- a terrible signal-to-noise ratio for agentic context windows

See [[claim-email-is-a-shim]] and [[contrarian-email-is-terrible-for-agents]] for the explicit critique.

## The long-term necessity
A native Agent-to-Agent (A2A) identity and communication protocol — emerging from on-chain identities, dedicated A2A standards, or service discovery via [[entity-model-context-protocol]]. Until a universal standard wins, betting on email is a pragmatic business decision but not a sound architectural foundation.

## Open question
[[question-email-survival]]: will email persist or be displaced?

## Enrichment / counter-perspective
Industry M2M auth standards (OAuth 2.0 Client Credentials, mTLS) are widely preferred for agent identity, supporting the speaker's thesis. A counter-perspective notes that AI-augmented email (DKIM, ML verification) may endure for hybrid human-agent worlds.