agenticweb.wiki

Coral Protocol (CoralOS) Coral

By Belgravia Labs Standards Observatory · Last verified · 2 primary sources

Coral Protocol (CoralOS) is an agentic-web standard (endpoint) at step 6, Coordinate, governed by Single company/startup-led open-source project; its status is "Kubernetes for AI agents: a platform for everything between your agents and production — registry, runtimes, security, and orchestration". It answers: "How do independently-built agents from a public marketplace get orchestrated together into one multi-agent system, with privacy isolation and built-in payment budgets, on top of MCP?" Implementation status is shipping, last verified 2026-10-29.

Coordinate Coral Protocol, rebranded 'CoralOS', is a single-vendor, open-source platform for orchestrating a graph of independently built AI agents — pulled from a public marketplace or built in-house — with per-session privacy isolation, a graph-based (rather than single-planner-hierarchical) coordination model, and built-in payment budgeting [1]. It positions itself explicitly as infrastructure rather than a thin wire protocol: its own tagline is "Kubernetes for AI agents," and its documented components (Coral Server for orchestration, a Coral Marketplace for discovery/monetization with attestation, a Coral Console for monitoring, and a 'Coralizer' that wraps any existing MCP server into a marketplace-listed agent) describe a full runtime platform built on top of MCP as the underlying inter-agent transport, not a standalone spec document [1].

Overview

It solves multi-agent orchestration at the point where a hierarchical single-planner design becomes a bottleneck: Coral's graph-based architecture lets agents communicate directly and monitor each other's progress rather than funneling every decision through a central controller, a design choice the project backs with a cited academic benchmark result (Anemoi, arXiv:2508.17068) showing accuracy gains from this structure on the GAIA benchmark [1]. It does not define a public, network-visible wire protocol comparable to A2A's Agent Card + JSON-RPC surface; its documented API (e.g. POST /api/v1/local/session) is a local orchestration control-plane endpoint requiring bearer authentication, run by the developer rather than exposed as a discoverable public origin [2].

As of September 2026,, Coral is an actively developed, versionless platform rather than a dated spec release — its docs site itself changed domain during the period covered by this map (from docs.coralprotocol.org to docs.coralos.ai), and its session API already includes native support for x402 micropayment budgets per agent, tying it into the broader agentic-payments ecosystem this map also tracks [1][2]. Implementations are real and shipping: Coral Server and the Coralizer are both public GitHub repositories under the Coral-Protocol organization. What is unresolved: how open Coral's governance actually is beyond "open-source code, single company roadmap" — no independent steering body or multi-vendor governance document was found, and no adoption count beyond the project's own marketing language was available to verify during this pass.

Discovery and probe

Agents are discovered via the centralized Coral Marketplace (publish/discover/monetize with built-in attestation); a local Coral Server also exposes a session-creation API for orchestrating a given agent graph; MCP is used as the underlying inter-agent transport for 'coralized' agents

POST {origin}/api/v1/local/session
parse:     A 200 response containing a JSON object with namespace and sessionId fields confirms a running Coral (local) server per its documented API reference; the request body's x402Budgets field on agent entries also confirms native x402 micropayment-budget support.
on absent: A 404, connection refusal, or 401/403 (this endpoint requires bearer auth) most commonly just means no local Coral Server is running at this address — Coral Server is typically run locally by the developer rather than exposed as a public origin, so a failed probe against an arbitrary public site proves little either way.

Not probed live: unsafe-post. The probe is POST /api/v1/local/session, which opens a session.

Instances

Every instance with its source is listed on the instances page.

Verified SDKs, reference implementations & validators:

See also

Comparisons

References

  1. CoralOS (formerly 'Coral Protocol'; docs.coralprotocol.org now redirects to docs.coralos.ai) describes itself as 'Kubernetes for AI agents' — a platform comprising Coralized Agents, a Coral Marketplace for discovery/monetization, Coral Server for orchestration, Coral Console for monitoring, and a Coralizer that turns any MCP server into a marketplace-listed agent. — https://docs.coralos.ai/about (2026-09-06) VERIFIED
  2. The documented local API includes POST /api/v1/local/session ('Create session'), which accepts an agentGraphRequest of agents (each with an id, provider, and an x402Budgets array for per-resource micropayment budgets) and returns a namespace and sessionId. — https://docs.coralos.ai/api-reference/local/create-session (2026-09-06) VERIFIED

Verification log and errata

JSON · Markdown · OKF v0.2

Frequently asked questions

What is Coral Protocol (CoralOS)?
Coral Protocol (CoralOS) is an agentic-web standard (endpoint) at step 6, Coordinate, governed by Single company/startup-led open-source project; its status is "Kubernetes for AI agents: a platform for everything between your agents and production — registry, runtimes, security, and orchestration". It answers: "How do independently-built agents from a public marketplace get orchestrated together into one multi-agent system, with privacy isolation and built-in payment budgets, on top of MCP?" Implementation status is shipping, last verified 2026-10-29.
What is the adoption and standardization status of Coral Protocol (CoralOS)?
"Kubernetes for AI agents: a platform for everything between your agents and production — registry, runtimes, security, and orchestration" (current docs homepage); described elsewhere as a 'decentralized protocol powering AI agent collaboration, trust, and payments', governed by Single company/startup-led open-source project (GitHub org Coral-Protocol); rebranded 'CoralOS' (docs moved from docs.coralprotocol.org to docs.coralos.ai); not a multi-stakeholder standards body. Implementation: shipping. Version: unversioned, continuously updated platform (Coral Server, Coralizer, Marketplace). Last verified 2026-10-29.
How does Coral Protocol (CoralOS) compare to other coordinate protocols?
Coral Protocol (CoralOS) is one of 13 standards at step 6, Coordinate (Talk to another agent). It pairs with Model Context Protocol, x402, Agent2Agent Protocol (A2A), Open Agentic Schema Framework. It builds on Model Context Protocol. Head-to-head comparisons on this site: Webhooks & RPC vs Agent2Agent Protocol (A2A), Agent2Agent Protocol (A2A), Agent Network Protocol. Every standard at this step is listed at https://agenticweb.wiki/category/coordinate/.