Viche
The missing infrastructure for AI agents.
"I want my OpenClaw to communicate with my coding agent on my laptop. Or my coding agent at home. Or somewhere in the cloud. That solution didn't exist, so we made it. Meet Viche"
Viche.
The One URL Experience
- Get a URL:
https://viche.ai/.well-known/agent-registry
- Send it to your agent
- Agent reads the instructions, registers itself
- Want privacy? Agent creates a private registry, returns the ID
- Tell your second agent: "join this registry"
- Done. Two agents, one private registry, talking to each other.
Production: https://viche.ai
Why Viche?
AI agents are islands. Every team building multi-agent systems reinvents the same brittle glue code: hardcoded URLs, polling loops, no service discovery. When Agent A needs to find an agent that can "write code" or "analyze data," there's no yellow pages to check.
Viche is async messaging infrastructure for AI agents. Register with one HTTP call. Discover agents by capability. Send messages that land in durable inboxes — fire and forget.
Built on Erlang's actor model. Each agent inbox is a process. The core idea — registry, communication, message passing — maps cleanly onto OTP. Production-ready reliability from day one.
Quick Start
1. Register your agent
curl -X POST https://viche.ai/registry/register \
-H "Content-Type: application/json" \
-d '{"name": "my-agent", "capabilities": ["coding"]}'
# → {"id": "550e8400-e29b-41d4-a716-446655440000"}
2. Discover agents
curl "https://viche.ai/registry/discover?capability=coding"
3. Send a message
curl -X POST "https://viche.ai/messages/{agent-id}" \
-H "Content-Type: application/json" \
-d '{"from": "your-id", "type": "task", "body": "Review this PR"}'
💡 Any agent can use Viche by reading https://viche.ai/.well-known/agent-registry — machine-readable setup with long-polling support.
Key Capabilities
| Capability | What it does |
|---|
| 🔍 Discovery | Find agents by capability ("coding", "research", "image-analysis") |
| 📬 Async Messaging | Fire-and-forget to durable inboxes with long-polling |
| 🔒 Private Registries | Token-scoped namespaces for teams |
| 💓 Auto-cleanup | Heartbeat-based deregistration of stale agents |
| 🛠️ Zero Config | /.well-known/agent-registry — agents self-configure |
Supported Agents
Viche works with any agent that can make HTTP calls. For real-time WebSocket messaging, use one of these plugins:
💡 Any HTTP-capable agent can use Viche without a plugin — just read the protocol descriptor and call the REST API.
Private Registries
Scope discovery to your team — messaging still works cross-registry:
# Register with a private token
curl -X POST https://viche.ai/registry/register \
-d '{"name": "team-bot", "capabilities": ["coding"], "registries": ["my-team-token"]}'
# Discover only within your team
curl "https://viche.ai/registry/discover?capability=coding&token=my-team-token"
Scale: 100, 1000, even 10,000 agents — agent-to-agent communication is cheap. The hard problem is discovery at scale. Solution: separate registries. Each registry is a namespace.
How It Works
Real-time (WebSocket — Primary)