DEV Community

Agenium platform
Agenium platform

Posted on

How to Give Your AI Agent a Permanent Address in 5 Minutes

#ai #agents #tutorial #webdev

How to Give Your AI Agent a Permanent Address in 5 Minutes

Most AI agents today are ephemeral. You spin one up, it does its job, it disappears. No address. No identity. No way for other systems to find it again.

That changes when you register on Agenium.

This tutorial walks you through giving your agent a permanent, resolvable address — the kind that survives model swaps, framework rewrites, and infrastructure migrations.

What You'll Get

After completing this tutorial, your agent will have:

  • A permanent address in the format yourname.telegram
  • A resolvable endpoint at chat.agenium.net
  • An Agent Card with your capabilities (queryable via API)
  • A behavioral record that accumulates over time

Step 1: Sign In (30 seconds)

Go to chat.agenium.net.

You have two options:

  • Telegram Login — click "Sign in with Telegram", authorize once
  • Email Magic Link — enter your email, click the link in your inbox

That's it. No OAuth dance. No password. No credit card.

What Just Happened?

The moment you sign in with Telegram, Agenium's DNS system reserves yourusername.telegram for you. It's yours — permanently. If your Telegram username ever changes, your domain updates automatically on next login.

Step 2: Meet Your Agent

After login, you're dropped into a chat interface. The entity on the other side is your agent — already running, already addressable.

Your agent has a built-in demo mode. Send it a message. Ask it something. It responds immediately, no setup required.

But here's what matters: while you were chatting, your agent was building a behavioral record at your address. Every interaction is logged against yourname.telegram. That record persists. It accumulates. It becomes your agent's reputation.

Step 3: Check Your Agent Card

Every registered agent gets an Agent Card — a machine-readable description of what it can do.

Fetch yours:

curl https://chat.agenium.net/api/cards/yourname.telegram
Enter fullscreen mode Exit fullscreen mode

Response:

{
  "address": "yourname.telegram",
  "display_name": "Your Agent",
  "capabilities": ["chat", "messaging"],
  "endpoint": "https://chat.agenium.net/agent/yourname.telegram",
  "registered_at": "2026-03-18T09:00:00Z"
}
Enter fullscreen mode Exit fullscreen mode

This is what other agents query when they need to find yours. The Agent Card is the machine-readable handshake that makes A2A (Agent-to-Agent) communication possible.

Step 4: Share Your Address

Your agent's address is yourname.telegram. Share it anywhere:

  • In a GitHub README: agent://yourname.telegram
  • In a blog post: chat.agenium.net/agent/yourname.telegram
  • In code: await discover("yourname.telegram")

Other developers (and agents) can now find yours. Not by knowing your server's IP. Not by having your API key. Just by knowing your name.

Step 5: Register Programmatically (Optional)

If you're building a multi-agent system and want to register agents programmatically:

import httpx

AGENIUM_ENDPOINT = "https://chat.agenium.net/api"

async def register_agent(name: str, capabilities: list[str], endpoint_url: str):
    """Register an agent with a permanent address."""
    response = await httpx.post(
        f"{AGENIUM_ENDPOINT}/agents/register",
        json={
            "name": name,
            "capabilities": capabilities,
            "endpoint": endpoint_url,
        },
        headers={"Authorization": f"Bearer {YOUR_API_TOKEN}"}
    )
    return response.json()

# Example
agent = await register_agent(
    name="my-booking-agent",
    capabilities=["flight-booking", "hotel-search", "calendar-sync"],
    endpoint_url="https://myserver.com/agent"
)

print(f"Agent address: {agent['address']}")
# → my-booking-agent.telegram
Enter fullscreen mode Exit fullscreen mode

Once registered, your agent is discoverable via the Agenium search API:

curl "https://search.agenium.net/agents?capability=flight-booking"
Enter fullscreen mode Exit fullscreen mode

This returns all registered agents that can handle flight booking — ranked by their behavioral track record.

Why Permanent Addresses Matter

Here's the problem this solves.

Imagine you build a flight-booking agent. It's good. It handles 500 reservations. Then you migrate from LangChain to a custom framework. New server. New endpoint. New model.

From the outside? That's a new agent. Zero trust. Zero reputation. Cold start from scratch.

With a permanent Agenium address, the address stays constant across migrations. The behavioral record stays attached. Other agents that trusted booking-agent.telegram continue to trust it — because the address, not the underlying infrastructure, is the identity.

This is what the internet figured out with DNS in 1983. We're applying the same insight to the agent layer.

What's Next

  • Explore the Agent Card API: GET /api/cards/{address} — fetch any agent's capabilities
  • Set up A2A communication: Use your address as the sender identity in A2A protocols
  • Check your behavioral record: As you interact, your track record builds automatically
  • Customize your capabilities: POST /api/cards/{address} to declare what your agent can do

Try It Now

→ chat.agenium.net — Sign in, get your address, start building

Questions? Drop them in the comments below. We respond to every one.

Agenium is the discovery and identity layer for AI agents — the DNS of the Agent Web. Built in public at agenium.net.

Top comments (0)