Open · Vendor-neutral · Draft v1
DCP— Development Coordination Protocol

What changed, on the wire.

DCP — the Development Coordination Protocol — is a small, machine-readable way for AI agents and humans to exchange project-coordination events. The transport carries the bytes; DCP carries the meaning.

Read the specification Read the docs
DcpMessagetransport → semantics
{ "dcp_version": "1.0", "message_id": "msg_01HZ0...",
  "message_type": "task.completed", "issued_at": "...12:30:00Z",
  "body": {
    "entity_type": "task",   "verb": "completed",
    "entity_id": "task_schema_validation",
    "attributed_to": "agent-builder",
    "delta": { "status": { "from":"in_progress", "to":"completed" } }
  } }
What it is

The transport moves bytes. DCP moves meaning.

The layer

Rides inside any transport

Any mesh, queue, or HTTP call handles identity, trust, and routing. DCP is the payload that says, semantically, "task_42 completed."

The analogy

A media type for coordination

DCP is to project coordination what a media type is to HTTP: a shared payload shape, independent of how it is carried.

The shape

One envelope. One event. One change.

DcpMessage

body: Event — what changed

entity_type + verb + entity_id

one or more of: entity (snapshot) / delta (changed fields) / refs (semantic links)

ProjectTaskDependency ArchitectureImpactDecisionReviewRequest FindingMilestone
Why events

Changes, not records.

Audit-native

Every message is a recorded change. History is the wire format itself.

Carries no trust

DCP describes state changes only — it never authenticates, routes, or executes. Those are other layers.

Vendor-neutral

Any agent or human, over any transport. Adopt the protocol without adopting anyone's product.

Get started

Read it, validate it, ship it.

Schemashttps://schemas.devcopro.org/v1/dcp-message.schema.json
Validatorany JSON Schema 2020-12 validator + the message_type rule — see the quickstart
Examples18 worked messages on this site — /examples/ and the job-lifecycle how-to
Conformance25-case accept/reject corpus — ships with the repository
Read the quickstart guide →
In practice

Built to be spoken, not just specified.

Transport

AgentixMesh

The secure transport DCP was designed alongside. AgentixMesh moves the bytes and decides identity, trust, and routing; DCP rides inside as the meaning. One example transport — DCP runs over any.

agentixmesh.ai ↗

Adopter

ANS — Agents Never Sleep

An autonomous agent runtime that works a backlog unattended — emitting a DCP task.completed as each ticket lands and reacting to events to coordinate the next step.

agentsneversleep.ai ↗

Origin

Where DCP comes from.

Platform
InterIP ↗

The hosting and platform provider — infrastructure and stewardship behind the work.

AI router
Tokonomix ↗

Multi-model AI routing and consensus for agent workloads.

AI assistant
ZelixAI ↗

An AI customer-service chatbot that automates support for businesses.

DCP is an open, CloudEvents- and A2A-compatible protocol, initiated by the TokonoMix project. Using it never requires any of these products — that is the point.