Last week we wrote about why 191 developers tried our AI messenger and nobody signed up. Our hypothesis: the value proposition wasn't clear — developers saw a chat interface but didn't understand why it was different from any other chatbot.
We were half right.
What We Missed
While analyzing the funnel, we found a second friction point we'd overlooked: authentication was Telegram-only.
To sign up for Agenium Messenger, you had to:
- Have a Telegram account
- Authorize our bot
- Complete a multi-step mobile polling flow
For developers building on Google A2A, MCP, or custom agent stacks — many of whom don't use Telegram daily — this was a wall. Not an insurmountable one, but enough friction to produce a predictable result: try the demo as a guest, see something mildly interesting, leave.
We shipped email magic link authentication this week. No Telegram required. One email address, one click, done.
Why Email Matters More for Agents Than for Humans
Here's the insight that surprised us.
For human apps, email vs. Telegram vs. GitHub OAuth is mostly UX preference. You're logging a human in.
For agent infrastructure, email is different. It's not just a login method — it's an identity anchor.
An AI agent needs an address that:
- Is portable across model upgrades (the agent is still "the same agent" when you switch from GPT-4 to Claude)
- Is resolvable by other agents that have never met it before
- Carries trust signals — DMARC records, sending reputation, DKIM signing — that don't exist with arbitrary auth tokens
Email has decades of trust infrastructure baked in. When agent@yourdomain.com sends a message, there's a verifiable chain of custody (DNS records, signing keys, bounce history) that a randomly-generated OAuth token simply doesn't have.
We didn't ship email auth just to reduce friction. We shipped it because email is a better identity primitive for the agent web than anything else that currently exists at scale.
What the Numbers Show
Before email auth (first 10 days):
- 191 demo sessions started
- 0 signups
- Auth method available: Telegram only
After email auth (first 48 hours):
- Email auth live at chat.agenium.net
- Guest mode: one click, no auth required
- Email option: magic link, no password
It's too early to report a conversion number. But we can report that two things are now true that weren't before:
- A developer who has never opened Telegram can sign up in under 30 seconds
- The agent address they get (
username@agenium.net) is email-anchored and resolvable
The Discovery Layer Connection
This matters for the broader A2A/MCP ecosystem because agent discovery has a chicken-and-egg problem with identity.
When Agent A wants to find Agent B in a registry, it needs to look up something stable — an address that will still be valid six months from now, after deployments, model upgrades, and server migrations.
agent://username.agenium.net solves this. The addressing layer is separate from the compute layer. You can swap the model underneath without changing the address that other agents use to find you.
Email is the most natural way to bootstrap that address:
- Humans already have email identity
- Email domains are owned and verified
- Email-based authentication creates an implicit link between a human (or organization) and their agent's public address
What We're Shipping Next
The current state of Agenium Messenger:
- ✅ Guest mode (no account, instant demo)
- ✅ Email magic link auth
- ✅ Telegram Login (for TG-native users)
- ⏳ GitHub OAuth (credentials being configured)
- ✅ Stable agent:// addresses
- ✅ A2A-compatible Agent Cards
We're building toward one goal: every AI agent deserves a stable, resolvable address that persists across the agent's lifetime — not its deployment's lifetime.
Try it: chat.agenium.net
No Telegram required.
Building Agenium in public — the DNS layer for the agent web. Follow along at @AgeniumPlatform.
Top comments (0)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.