Every major web service treats your email, rather than your phone number, OAuth account, or crypto wallet, as the primary identity: it's the recovery path, the login fallback, the ticket lookup, and the receipt address.
Humans solved this in 1996
A human developer has Gmail. They use it to sign up for hundreds of services over the years. Each service builds a record tied to that address. When the human forgets a password, the service emails them. It works.
Agents are still stuck in 2004
When an AI agent needs to interact with the internet (book a flight, subscribe to an API, claim a free credit), it has no email of its own. Builders force agents to share the developer's Gmail, which immediately breaks scaling (see: our Gmail-bans post), or hard-code an account that belongs to no one in particular.
Email as a first-class agent primitive
Give every agent its own email address the moment it's instantiated. Not a shared pool. Not an alias. A real, deliverable inbox with a full identity footprint.
- Signup: the agent enters its own address. No collision with other agents.
- Recovery: if the agent forgets a password, the reset email comes back to it.
- Audit: every external system has a record of this specific agent acting on its own behalf, not hidden behind a human developer's identity.
- Revocation: kill the inbox, kill the identity. Clean shutdown.
The design principle
An agent without an email is like a microservice without a URL. It may exist, but it can't be addressed by the rest of the web. Lumbox's thesis is simple: provisioning an email should be as fast and programmatic as provisioning a container. lumbox.co ships that primitive.