agenium
v0.2.3
Published
DNS of the Agent Web — identity, discovery & communication for AI agents. MCP-compatible agent:// protocol with mTLS, trust scores & capability search.
Maintainers
Readme
The Problem
AI agents can't find each other. MCP gives agents tools, but there's no standard way for agents to get identity, discovery, or direct communication. Every integration is point-to-point.
The Solution
AGENIUM is DNS for AI agents. Every agent gets a unique agent://name URI. Agents discover each other by name, verify trust, and communicate — just like websites use domain names.
agent://weather → resolves to endpoint + capabilities + trust score
agent://search → find any agent by what it does
agent://my-bot → your agent, your identityGet Started in 60 Seconds
npx @agenium/create-agent my-agent
cd my-agent
npm startThat's it. Your agent is live on the agent:// network.
Or use as a library:
npm install ageniumimport { AgeniumClient } from 'agenium';
const client = new AgeniumClient({
apiKey: 'dom_your_key',
agentUri: 'agent://myagent',
});
// Discover any agent by name
const target = await client.resolve('agent://search');
// Connect and communicate
const session = await client.connect('agent://search');
await session.send({ query: 'find weather tools' });
const response = await session.receive();Why AGENIUM?
| Feature | Without AGENIUM | With AGENIUM |
|---------|----------------|--------------|
| Identity | Hardcoded URLs | agent://name URIs |
| Discovery | Manual config | DNS-style resolution |
| Communication | REST/WebSocket patchwork | Stateful sessions + mTLS |
| Trust | None | Capability manifests + trust scores |
| MCP Integration | Tools only | Tools → discoverable agents |
Features
agent://Protocol — Unique identity via URI scheme (likehttps://for agents)- DNS Resolution —
agent://name→ endpoint + capabilities - MCP Bridge — Any MCP server → discoverable agent (
@agenium/mcp-server) - Stateful Sessions — SQLite-backed persistent conversations
- HTTP/2 + mTLS — Secure transport with mutual TLS
- At-Least-Once Delivery — Outbox pattern with retries
- Capability Manifests — Agents declare what they can do
- 56 Tests — Unit, integration, and E2E coverage
Ecosystem
| Package | What it does |
|---------|-------------|
| agenium | Core client SDK |
| @agenium/create-agent | Scaffold agents in 60 seconds |
| @agenium/mcp-server | Bridge MCP servers → agent:// network |
| discord-agenium | Discord bot gateway |
| slack-agenium | Slack app gateway |
| n8n-nodes-agenium | n8n automation nodes |
| agenium (PyPI) | Python SDK |
Architecture
Your Agent Remote Agent
agent://mybot agent://weather
│ │
├── resolve("agent://weather") ───────►│
│ (DNS via AGENIUM network) │
│◄── endpoint + capabilities ──────────┤
│ │
├── connect (HTTP/2 + mTLS) ──────────►│
│ (stateful session) │
│◄── response ─────────────────────────┤🔍 Find MCP Servers
Looking for AI tools to connect to? Search by capability, language, or use case.
Links
- 📖 Documentation
- 🤖 Live Demo — Try 4 working agents
- 🔍 MCP Search — Find any MCP server
- 💬 Discord — Community & support
- 🐦 Twitter/X
- 📝 Blog
License
MIT © AGENIUM
