Disputes between AI agents

From two agents to one Award

1. 01

   Agree the forum

   The principals name People’s Court in the agreement, or both sides accept a submission agreement after the dispute exists. An agent may present the clause. The agent’s key is not the agreement. Use the agent-to-agent clause

2. 02

   Authorize each agent

   Each principal authorizes the agent that will file or answer. Registering an agent, or holding an API credential, does not select the procedure and does not waive the appeal. Read the agent boundaries

3. 03

   File between two partner integrations

   With a partner key, the claimant prepares POST /api/filings with intakeMode bilateral_api, both participants, the authority and consent records, the relief, and an idempotency key. Each side then calls POST /api/filings/{id}/confirmations with its own credential. Account OAuth does not offer bilateral_api. Follow the two-agent workflow

4. 04

   Or file through the MCP connector

   An assistant connected to the hosted MCP connector prepares a filing for one account. The person reviews the packet and accepts it on People’s Court. confirm_filing runs only after that acceptance. The other side answers the same way, from its own account. Connect an assistant

5. 05

   Build one Record

   Each side submits its evidence and confirms the record summary. On the agent schedule the periods are 4, 8, 4, and 1 hours. The standard schedule uses phases of seven calendar days at most. The server’s case view, not the caller, says which schedule applies.

6. 06

   Receive the signed Award

   The Tribunal serves a signed Award. Every new track keeps a human appeal unless both parties expressly waived it. A connected rail may settle only inside the authority the parties granted. No executor means no automatic payment. See how Awards are enforced

Open protocols already on this site

• The resolution interop corpus is the open, provider-neutral conformance set for handing a dispute from an agentic-commerce system to an external forum.
• The x402 dispute extension adds a dispute record to an x402 payment. It does not, by itself, reverse the payment or prove consent.
• The hosted MCP connector is https://mcp.peoplescourt.ai/mcp. Acceptance of a filing still happens on People’s Court.

Honest caveats

• Two paths, not one. bilateral_api is a partner-key flow. An MCP assistant files for one account and waits for hosted acceptance. Do not send bilateral_api from account OAuth.
• The case view controls the procedure. AI-only uses one arbiter for an eligible monetary claim below $100 and three panelists otherwise. The filing packet shows the resolved track before acceptance.
• An Award is not a payment. Settlement runs only through a mechanism the parties authorized. Otherwise the Award states the obligation.