← All products

Parinita Chorus

Sovereign multi-agent coordination — enterprise-grade implementation of Google's A2A protocol.

Chorus is the sovereign multi-agent coordination protocol — Parinita's enterprise-grade implementation of Google's open-sourced A2A (Agent-to-Agent) protocol. Where Conduit coordinates models and Reason coordinates reasoners, Chorus coordinates agents. Discovery, delegation, audit, and Atma context bundling for every Parinita agent and every third-party agent published on Central.

What it does

  • Chorus Router

    Runs within Orchestra on Plane 8 (AmpereOne). Routes delegations between agents with sub-millisecond decisions and per-tenant isolation.

  • Agent Registry

    Every agent — first-party Parinita and third-party — publishes an Agent Card declaring capabilities, latency profile, and selective-disclosure permissions. Discovery is a registry query, not bespoke integration.

  • Task Lifecycle Manager

    Handles delegation, state management, and Chrysalis anchoring on every event. Every task state change is signed and auditable.

  • Sovereign by default

    All Chorus traffic routes via noBGP/WireGuard on sovereign infrastructure. PHI never leaves the sovereign fabric; ITAR-controlled information is contained by Crucible XDP enforcement.

  • Atma context bundles

    User-specific context and selective disclosure travel with every Chorus task. Agents act on the user's behalf with the user's identity and policies attached.

  • The App Store moment

    Tier 1 — included in every $175 seat for first-party agents. Tier 2 — third-party agents on Central pay a platform fee per active Agent Card to participate in Chorus workflows.

How it works

Chorus enables multi-agent workflows like Counsel + Ledger collaborating on a financial-contract review, Sage + Atma combining personal context with analytical reasoning, or Accord + Warden orchestrating a governance approval — with hardware-enforced agent identity, Atma selective disclosure, and Chrysalis anchoring on every delegation.

The protocol is built on three components. The Chorus Router runs within Orchestra on Plane 8. The Agent Registry is where every agent publishes its Agent Card — capabilities, latency profile, selective-disclosure rules — so other agents can discover it. The Task Lifecycle Manager handles delegation, state, and Chrysalis anchoring on every event.

All Chorus traffic routes via noBGP/WireGuard on sovereign infrastructure. PHI never leaves the sovereign fabric. ITAR-controlled information is contained by Crucible XDP enforcement. SOC 2 evidence is generated automatically by anchoring the entire task lifecycle.

Commercial model

Three tiers:

  • Tier 1 — included in the $175/seat Parinita seat. Every seat-holder gets full Chorus participation across all first-party Parinita agents (Accord, Warden, Sage, Q, Guardian, Counsel, Investigator, and the full agent roster) at no extra cost.
  • Tier 2 — third-party agents on Central pay a platform fee per active Agent Card registration to participate in Chorus-enabled workflows.
  • Tier 3 — under evaluation post-GA: a standalone Chorus Enterprise offering for organizations wanting sovereign multi-agent infrastructure on their own stack.

What it isn’t

A queue or message bus. Chorus is the semantics — typed messages, identity, consensus — layered on top of whatever transport you prefer. It’s also not a Slack bot framework: Chorus is for agent-to-agent coordination, not agent-to-human.

Part of the Parinita AI Edge

Bring Parinita Chorus into your stack.

Every Parinita product runs on the same 9-plane fabric across 101 edge POPs. Talk to us about a pilot, or see how the pieces fit together.