Accord Protocol GitHub

Open standard for autonomous agent work

Accord Protocol

A receipt layer for paid agent work.

Accord records the terms, verification decision and settlement evidence around a paid agent task so buyers, tools and rails can reason about more than payment alone.

Run mock MCP demo Read specification View repository
v0 draft Testnet-first L0-L4 conformance Audit-gated mainnet
01 Terms

Agreement Object

02 Execution

Tool, API, agent or human work

03 Verification

Signed receipt

04 Settlement

Rail proof and record

Current status: v0 draft, testnet-first, NOT CERTIFIED FOR MAINNET. Production use is blocked until signed audit manifests explicitly allow it.

Status Testnet-first

Current readiness, package posture and mainnet blockers.

 Security Audit-gated

Trust boundaries, reporting path and production constraints.

 Roadmap Conservative path

Spec stability, conformance and developer experience priorities.

 RSS 23 guides

Evergreen Accord explainers for developers and agents.

Why it exists

Payments say that value moved. Accord says what the value was for.

01

Machine-readable work terms

Price, deadline, parties, verifier, rail policy and acceptance criteria live in one canonical agreement.

02

Receipts agents can trust

Verification and settlement receipts create an auditable trail instead of treating payment as proof of completion.

03

Rail-agnostic by design

Accord can sit beside MCP, HTTP 402 flows, agent wallets and chain-specific settlement rails.

Protocol surface

A small set of objects around the full work lifecycle.

accord.agreement.v0

Accord Agreement

Defines the promised work, parties, price, asset, deadline, verifier and acceptance rules.

 accord.verification_receipt.v0

Verification Receipt

Records whether the output was accepted, rejected or partially accepted by the verifier.

 accord.settlement_receipt.v0

Settlement Receipt

Records whether the economic side settled, on which rail, with what proof or transaction.
Buyer agent Agreement Seller agent
Work output Verifier Receipt
Rail adapter Settlement Record

Developers

Start with the mock rail. Move to testnet only when the lifecycle is clear.

Browse examples

Quickstart

git clone https://github.com/accord-protocol/accord-protocol
cd accord-protocol/examples/15-paid-mcp-repo-audit
npm install
npm run dev

@accord-protocol/core

Canonicalize, hash and validate protocol objects.

@accord-protocol/gateway

Accord/402 middleware for paid HTTP flows.

@accord-protocol/mcp

Paid and verifiable MCP tool wrappers.

@accord-protocol/conformance

L0-L4 compatibility checks for implementations.

Rails

One agreement model, multiple settlement assumptions.

Rail Role Status
Ergo First reference programmable settlement rail using Notes, Reserves, Trackers and predicates. Testnet only
Rosen Bridged asset path on top of the Ergo reference rail. Testnet-first
Base/EVM Reference EVM Note rail for USDC-style flows. Audit-gated
x402 Payment proof adapter for HTTP 402 resources. Integration rail

Agent surface

Human-readable positioning, machine-readable context.

LLM index /llms.txt

Compact summary, status and high-signal links.

 Full context /llms-full.txt

Expanded protocol context for retrieval systems.

 Policy /agents.txt

Instructions for agents and search crawlers.

 Discovery /.well-known/accord.json

Structured protocol identity and safety posture.

FAQ

Short answers that should not drift.

What does Accord add to x402?

x402 verifies payment for paid HTTP resources. Accord adds agreement terms, verification receipts and settlement receipts around the paid work.

What does Accord add to MCP?

MCP explains how agents call tools. Accord adds paid-tool terms, completion verification and a settlement record.

Is Accord production-ready?

No. Accord v0 is alpha, testnet-first software and NOT CERTIFIED FOR MAINNET.