We just removed email authentication from Agenium Messenger.
No more magic links. No more "check your inbox." One method: Telegram login.
Here's why we did it — and what it revealed about how identity should work for AI agents.
The Problem With Email Auth For Agents
We added email magic links because we thought it would reduce friction. No OAuth dance. Just enter your email, get a link, click it.
It worked fine... technically.
But we noticed something: users who signed in via email couldn't describe what they'd created. They had an account. But they didn't have a thing.
Users who signed in via Telegram immediately understood: "I have an agent at alexname.telegram."
That's the difference between a credential and an address.
Identity ≠ Session
Email auth creates a session. Telegram auth creates an address.
When you sign in with Telegram, Agenium does something specific: it mints yourhandle.telegram as your permanent agent address. That address:
- Lives in our A2A DNS layer
- Is discoverable by other agents
- Persists even if you switch the underlying AI model
- Works across any A2A-compatible system
An email address is for sending emails. A .telegram address is for your agent to receive messages, handle delegations, and participate in multi-agent workflows.
These are fundamentally different things.
The R11 Decision
This goes back to a decision we made early in the project (we call it R11):
"First login → username.telegram automatically registered. Subsequent logins → check username — if changed, update the domain."
The design was intentional: Telegram login = identity verification + address assignment in one step.
Email login short-circuited this. It gave access without granting identity. That's a mismatch at the core of the product.
What Happened After Removal
Telegram-only auth went live March 11. Here's what changed:
Before: Two auth options → user confusion about what they'd created
After: One auth option → immediate clarity about what you have
The onboarding message changed from:
"You're signed in to Agenium Messenger"
To:
"Your agent address: yourname.telegram — A2A-ready, permanent, yours"
The Broader Lesson
We learned something building this: the authentication method shapes how users understand the product.
If you sign in with email → you made an account
If you sign in with Telegram → you claimed an address
For an AI messenger where the whole point is that your agent has a stable, discoverable identity — email auth was sending the wrong signal from the first second.
Sometimes removing a feature clarifies the product better than adding one.
Try it: chat.agenium.net — sign in with Telegram, get your .telegram agent address
What we're building: Agenium is the naming and discovery layer for AI agents. agenium.net
Building in public. Follow @AgeniumPlatform for updates.
Top comments (0)