The rule-of-law layer for agentic commerce.

Agents can make deals. Now they can resolve disputes.

Request agent onboardingRead the integration docsRead our research

Consent · Decision · Auditable record

Authority verifiedRecord authenticatedSettlement bounded

A dispute protocol built for software.

From consent to settlement, every material act stays attached to one auditable case.

  1. 01

    Agree

    Both sides accept the exact procedure and settlement authority before the dispute is decided.

  2. 02

    Submit

    Authorized agents submit signed positions and transaction evidence into one authenticated Record.

  3. 03

    Decision

    The decider assigned under the parties’ chosen procedure issues a signed Award.

  4. 04

    Settle

    Execution follows service, the appeal election, applicable stays and the authority granted to a connected rail.

Fast enough for software. Strict enough for commerce.

Speed comes from a focused AI-only procedure, not from skipping consent, evidence, or authority.

End-to-end advance delegation

A one-off API call is not enough. Both sides must authorize the transaction and its dispute procedure in advance, within defined limits.

A separate appeal choice

Every track offers a paid human appeal unless both parties expressly waive it. The assigned human decides before service in the AI-assisted human track. Unresolved integrity or procedure defects prevent release.

Settlement within authority

The connected rail does only what the parties authorized. If authority or execution cannot be verified, nothing moves.

Authority and procedure are separate choices.

People and businesses remain the principals behind a transaction when an agent acts on their behalf. Using an agent does not select the case track or waive appeal.

Principals must authorize the agent’s actions. The parties choose AI-only or AI-assisted human and accept the automatically assigned AI procedure and any express appeal waiver. Settlement still requires the authority granted to the connected rail.

Open integration work.

Use the dispute layer that fits your stack, from a portable lifecycle test to a live case integration.

Resolution interop corpus

We maintain an open, provider-neutral conformance corpus for testing how ACP, UCP, AP2, x402, LCP, escrow, and other agentic-commerce systems hand disputes to external resolution.

transaction → authority → frozen record → disposition → execution receiptView interoperability tests

x402 dispute extension

A standalone SDK for adding consent-aware dispute terms, evidence packets, and an adjudication handoff to x402 transactions.

Explore the x402 work

Partner API

Open bilateral cases, submit authenticated Records, receive decision callbacks, and connect settlement within the authority the parties granted.

Read the API docs

Interested agents can ask to connect.

Access is manually reviewed and credentials are scoped per integration. Tell us what your agent does and the dispute workflow it needs.
Request agent onboardingRead the API docs