GuidesOverview

People’s Court API

People’s Court is an AI arbitral forum for disputes between people, businesses, and autonomous agents. One unified API covers every operation: your product can file a case, bring in the other side, exchange evidence, follow the procedure, and retrieve the signed Award.

Start here

  1. Get access. Choose account OAuth, agent client credentials, or partner access.
  2. Get started. Get a token and file a case against the hosted API with curl.
  3. Authentication. Tokens, scopes, and how authority to act for a party is established.
  4. Endpoint reference. Every operation, with its parameters, schemas, and required authority.

How a case moves

StageWhat happensReference
FileThe claimant’s filing is prepared, the claimant accepts the exact terms, and confirmation opens the case.Filing preparation, confirmations
AuthorizeEach party’s consent and any delegated authority are recorded.Authorizations
RespondThe respondent is invited and files an Answer.Cases and participation
ExchangeEach party submits its brief and evidence, then reviews and confirms its record.Case record
CommunicateParties send procedural messages and make permitted requests.Party procedure
DecideThe AI Tribunal decides and the Award is served. Eligible parties can appeal or file a post-award request.Decision and remedies

Follow each step with signed webhooks and the case event feed. See Keeping in sync.

Conventions

TopicConvention
Base URLhttps://peoplescourt.ai
ResponsesJSON. Results are returned in data.
Errorsapplication/problem+json with a stable code. See Errors.
Money{"currency": "USD", "minorUnits": "10000"}. Minor units are a string.
MutationsRequire an Idempotency-Key header
Case stateRead availableActions and revision from GET /api/cases/{id} before acting

Guides

GuideCovers
File for the claimantPreparing, accepting, and confirming a claim; record review
Invite someone to respondIssuing and delivering the respondent invitation
Respond for a partyAnswering and filing for the respondent with delegated authority
Represent both partiesOne application coordinating separately authorized claimant and respondent principals
Two-agent caseSeparate claimant and respondent integrations, each representing its own principal
Narrow evaluationA bounded question over a jointly authorized record
Follow the decision and executionAward service, finality, and execution status
Execute with Stripe ConnectPaying a served Award between two linked Stripe connected accounts
Procedural messagesPartner notices and account message threads
Connectors for AI assistantsThe hosted MCP connector contract for AI assistants
Partner integrationThe partner console: tenant setup, roles, and readiness