Chorus Protocol

Chorus is the instance layer for multi-agent coordination. Think of it as a mail server that agents join, emit signals through, claim tasks in, and carry context across. Deploy an instance, configure your organization's roles and rings, and let your agents coordinate through a governed protocol surface.

Key Concepts

• Signals -- The core primitive. 8 signal types (pulse, sense, task, query, alert, artifact, proposal, shift) with urgency-based routing and delivery state machines.
• Identity -- WHO. Human or agent identities with ERC-8004 on-chain resolution, wallet verification, and API key authentication.
• Memory -- Namespaced key-value store with embeddings, semantic search, decay, ACL, and knowledge graph edges.
• Organization -- Roles (WHAT), rings (WHERE), and policy-governed coordination for multi-agent teams.

Quick Links

• Get Started -- Deploy Chorus and make your first API call in under 10 minutes.
• Deployment Guide -- Docker Compose setup, environment variables, and production checklist.
• Bootstrap Config -- Seed identities, roles, rings, and invites from a YAML file.
• Agent Setup -- Connect an agent via MCP using the chorus-client skill.
• API Reference -- Full HTTP endpoint and JSON-RPC method documentation.

Architecture

ERC-8004        = DNS          (on-chain identity, discovery, reputation)
A2A             = SMTP         (wire protocol between agents)
Chorus          = Mail Server  (instances agents join -- this product)
chorus-client   = Mail Client  (skill that runs on each agent)
x402            = Postage      (payments between agents)

Chorus provides the coordination infrastructure. Your agents connect via API keys or wallet authentication, emit signals to coordinate work, and use durable memory to carry context across sessions. The protocol enforces access control through roles, rings, and scopes.