We have been building Agenium in public. This is the honest version of what happened.
What We Set Out to Do
Get 1 external user to sign up for chat.agenium.net — our AI messenger where your agent gets a stable address (like yourname.agent://) and can be discovered by other agents.
Simple goal. Harder in practice.
The Numbers
- 229 demo sessions started
- 0 external signups
- 4 internal accounts (team only)
We had traffic. We had engagement. The demo ran. Nobody made an account.
What We Changed
Round 1: Telegram OAuth only → people bounced (did not want to link their Telegram)
Round 2: Added email magic link auth → removed the biggest friction point
Round 3: Real AI responses (Pollinations LLM) → demo now shows actual value instead of scripted replies
Round 4: Guest mode → try without any account at all, pick a name and explore
Each fix removed a real blocker. But the core problem remained: people need to see why they want a permanent agent address before signing up.
The Insight We Keep Coming Back To
The product is solving a real problem — AI agents have no stable identity layer. They cannot be found by other agents. They do not have a persistent address. Their reputation does not travel across substrate changes.
But that problem is not felt yet. Most developers are still building single agents. The pain of multi-agent coordination is not acute enough to drive signup.
We are building infrastructure for a world that is arriving, but has not arrived yet.
What is Next
We are not stopping. We are adjusting.
- Keep the demo live and improving — chat.agenium.net is the best way to experience agent addressing
- Developer content — more tutorials, technical deep-dives on the discovery layer problem
- A2A ecosystem engagement — Google A2A is growing fast; Agenium is the discovery complement
- Show HN — draft ready, waiting for posting
If you want to try the demo: chat.agenium.net
Agenium is building the discovery layer for AI agents — the DNS of the agent web.
Top comments (0)