# peoplescourt.ai Dispute Readiness Check

> peoplescourt.ai Dispute Readiness Check is a paid API for AI agents from peoplescourt.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns a deterministic pre-filing readiness report for a legal dispute, including supported venue/lane, composition requirements, filing fee quote, consent/evidence requirements, corpus compatibility, and timing warnings — without filing the case or assessing its merits.

## Facts

- Endpoint: POST https://peoplescourt.ai/api/x402/dispute-readiness
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/peoplescourt-ai-dispute-readiness-check-ae89890b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HKyHHmRzIEu2XvSqws5ov

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability peoplescourt-ai-dispute-readiness-check-ae89890b -d '<json body>'
```

Example prompt: Before I file my $850 breach-of-contract dispute against a freelancer I hired, can you run a dispute-readiness check to tell me which lane I'd use, what filing fee to expect, what evidence I need to include, and whether there are any timing issues I should know about?

## When to prefer this

Use this endpoint when an agent or user needs to verify whether a dispute meets pre-filing requirements before committing to submission — ideal for automated intake flows, pre-screening bots, or legal self-help tools that need a deterministic readiness signal without triggering a case filing. Prefer this over generic legal information APIs when you need a structured, machine-readable readiness verdict with a concrete fee quote and actionable checklist.

## Known failure modes

- Claim type or jurisdiction not supported — corpus incompatibility returned
- Missing required dispute parameters — validation error with list of required fields
- Ambiguous or insufficient dispute description — readiness report flags incomplete inputs
- Timing warning triggered — report indicates the claim may be outside allowed filing window
- Dispute amount outside accepted range — lane assignment fails with range error

## How this service works

Deterministic dispute-readiness report with supported lane, composition, published filing-fee quote, consent and evidence requirements, corpus compatibility, and timing warnings. No case is filed and no merits are assessed.

## Output

A structured dispute-readiness report containing: the supported procedural lane for the claim, composition and formatting requirements, a published filing fee quote in USD, consent and evidence requirements the filer must satisfy, corpus compatibility status, and any timing warnings (e.g. statutes of limitations, procedural deadlines). No merit assessment is made and no case is filed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "remedy": {
   "enum": [
    "corpus_allocation",
    "money_obligation",
    "declaratory"
   ],
   "type": "string",
   "description": "Requested remedy shape."
  },
  "claimantType": {
   "enum": [
    "human",
    "organization",
    "ai_agent"
   ],
   "type": "string",
   "description": "Claimant party category."
  },
  "respondentType": {
   "enum": [
    "human",
    "organization",
    "ai_agent"
   ],
   "type": "string",
   "description": "Respondent party category."
  },
  "settlementRail": {
   "enum": [
    "none",
    "x402r",
    "bilateral_escrow",
    "acp",
    "stripe_connect",
    "partner_executes"
   ],
   "type": "string",
   "description": "Existing or proposed settlement rail."
  },
  "corpusAmountUsd": {
   "oneOf": [
    {
     "type": "number",
     "maximum": 10000000,
     "minimum": 0
    },
    {
     "type": "null"
    }
   ],
   "description": "Bound external corpus in USD, or null when no corpus exists."
  },
  "amountInDisputeUsd": {
   "type": "number",
   "maximum": 10000000,
   "minimum": 0,
   "description": "Amount in dispute in USD."
  },
  "escrowWindowEndsAt": {
   "type": "string",
   "format": "date-time",
   "description": "Optional settlement deadline in ISO 8601 form."
  },
  "fastTrackClaimClass": {
   "oneOf": [
    {
     "enum": [
      "payment_not_settled",
      "refund_window_expired",
      "non_delivery",
      "double_charge",
      "escrowed_refund_request",
      "acp_evaluation"
     ],
     "type": "string"
    },
    {
     "type": "null"
    }
   ],
   "description": "Protocol-derived fast-track class, or null for an ordinary claim."
  },
  "claimantEvidenceReady": {
   "type": "boolean",
   "description": "Whether claimant evidence is ready for filing."
  },
  "mutualConsentReported": {
   "type": "boolean",
   "description": "Whether bilateral arbitration consent is reported."
  },
  "authorityToBindReported": {
   "type": "boolean",
   "description": "Whether signers report authority to bind their principals."
  },
  "respondentEvidenceReady": {
   "type": "boolean",
   "description": "Whether respondent evidence is expected to be available."
  },
  "microClaimsTierConsentReported": {
   "type": "boolean",
   "description": "Whether both parties report consent to the micro-claims tier."
  },
  "remedialJurisdictionOptInReported": {
   "type": "boolean",
   "description": "Whether both parties report consent to relief beyond a held corpus."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "lane": "agent",
  "timing": {
   "warning": null,
   "escrowWindowEndsAt": "2026-07-25T12:00:00.000Z"
  },
  "filingFee": {
   "tier": "micro",
   "percent": 5,
   "currency": "USD",
   "floorUsd": 0.01,
   "amountUsd": 1,
   "collectionNote": "This published filing-fee quote is separate from the $0.01 price paid for this readiness report.",
   "panelSurchargeUsd": 0
  },
  "composition": {
   "value": "memorandum",
   "reason": "eligible_micro_claim"
  },
  "disclaimers": {
   "caseFiled": false,
   "statement": "This automated report checks structured technical readiness only. It does not file a case, verify the reported facts, assess the merits, or provide legal advice.",
   "legalAdvice": false,
   "meritsAssessed": false,
   "reportedFactsVerified": false
  },
  "readyToFile": true,
  "requirements": [
   {
    "code": "bilateral_consent",
    "detail": "Both parties must provide case-bound consent under the published Rules before merits review.",
    "satisfied": true
   },
   {
    "code": "authority_to_bind",
    "detail": "Each person or agent acting for a principal must establish authority to bind that principal.",
    "satisfied": true
   },
   {
    "code": "claimant_evidence",
    "detail": "The claimant must be able to identify and submit the evidence supporting the claim.",
    "satisfied": true
   },
   {
    "code": "respondent_process",
    "detail": "The respondent must receive process and an opportunity to answer and submit evidence.",
    "satisfied": true
   },
   {
    "code": "remedy_scope",
    "detail": "The requested relief is limited to the reported external corpus.",
    "satisfied": true
   }
  ],
  "supportedLane": true,
  "corpusCompatibility": {
   "detail": "The requested relief is limited to the reported external corpus.",
   "compatible": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/peoplescourt-ai-dispute-readiness-check-ae89890b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from peoplescourt.ai](https://www.zero.xyz/host/peoplescourt.ai/llms.txt)