[Feat]: Agent (and other types) URN

[alexec]

Is your feature request related to a problem? Please describe.

We need a way to identify agents (as well as tools, skills, rules, Agentic Workflows) in a globally unique manner that allows us to relocated the agent (skill etc) and understand that it is the same agent (skill etc).

I'm looking at URNS:

urn:agents:agent:code-bot
urn:agents:skill:typescript-bestpractices
urn:agents:rule:use-tabs-not-spaces
urn:agents:workflow:write-a-react-app

Describe the solution you'd like

URNs as 1st class citizen.

Describe alternatives you've considered

No response

Additional context

URLs don't work. The change based on environments.

Code of Conduct

• I agree to follow this project's Code of Conduct

[chorghemaruti64-creator]

This is a great proposal — we've been building something very similar in production.

At Agenium, we've implemented a DNS-based agent addressing system where each agent gets a globally unique, resolvable address using the agent:// URI scheme. For example:

• agent://assistant.telegram — resolves to a specific agent's endpoint via DNS
• agent://mycompany.agent — custom domain for registered agents

The key design decisions we landed on:

1. DNS as the resolution layer — familiar infrastructure, already decentralized, cacheable
2. Platform-namespaced identifiers — .telegram, .github, etc. auto-assign based on platform login (e.g. your Telegram username becomes username.telegram)
3. Relocatable — the agent's address stays the same even if the underlying endpoint changes (just update the DNS record)

This maps well to the URN concept in this proposal. The agent:// scheme gives agents a permanent identity that's independent of their hosting infrastructure.

We've found that tying agent identity to existing platform identities (Telegram, GitHub) dramatically reduces the adoption friction vs. requiring a new namespace registration.

Happy to share our implementation details — the DNS resolver, the auto-registration flow, and the discovery API are all documented at chat.agenium.net.

[Tehsmash]

This is being standardised as part of the AI Catalog project (originally a spin off from A2A) there was a recent PR that merged introducing a urn "air" (AI resource): Agent-Card/ai-catalog#36

I'll close this as being handled in ai-catalog instead of A2A.