> For the complete documentation index, see [llms.txt](https://peoplescourt.ai/llms.txt). This page is also available as Markdown.

# API changelog

## October 17, 2026 (pending coordinated release)

- Rules 1.1 now define the Procedural Arbiter in Rule 1.4 and authorize the bounded procedural mandate in Rules 4.6 and 4.13. Cases begun under the amendment pin their assigned routes at opening; earlier cases retain their existing controls.
- New AI deadline-extension rulings record `authority: "procedural_arbiter"` and the public case designation. Other self-service kinds remain filable and may wait in `administrator_queue`, reserved for the Tribunal unless an Administrator can act under Rule 2.6. Human-track authority and historical ruling attribution are unchanged.

## October 13, 2026

- A party may have only one pending typed extension request for a given deadline.
  A second request for that deadline is refused; use POST /api/cases/{id}/procedural-requests/{requestId}/withdraw or select Withdraw request in Case messages on the website, then refile.
  The canonical route also accepts authorized Partner API callers. MCP has no withdrawal action; use the website or canonical API.
  This applies to website, canonical API, Partner API and MCP filings, including requests whose response thread has closed.
- In AI-assisted human cases, ordinary procedural requests go to the active assigned human Arbitrator.
  Without an active appointment they wait for a human Arbitrator, with no AI fallback.
  Administrators retain their limited Rule 2.6 authority; AI-only cases keep their existing procedure.

- Fee quotes return the published Rule 11.1 case fees: AI-only, 5.67% of the amount in dispute with a $1.67 minimum; AI-assisted human, $310 plus 5.67% of the amount in dispute; ruling-only, $105 for AI-only or $520 for AI-assisted human. `forumFee` and a prepared filing’s fee are the final price. `baseFee`, `percentComponent`, `floor`, `panelSurcharge`, `rateBasisPoints` and `fixedComponent` describe the base schedule that USDC payments use, so `forumFee` no longer equals `baseFee + panelSurcharge`.
- The public fee-quote fields `percent` and `floorUsd` also describe the retained base schedule. These base fields are metadata, not inputs for reconstructing the final stated price: a $1,000 human-assisted claim retains `fixedComponent` = $300 and `rateBasisPoints` = 500 while the final fee is $366.70. Use the returned final fee for payment.
- USDC filing-fee challenges for x402r referrals charge the base amount and add `cardPriceUsd`, `usdcSavingsUsd` and `priceDisplay`.

## October 5, 2026

Old `/api/v1` and `/api/v2` URLs return `410 Gone` with their unified equivalent.

## September 23, 2026

- Added an account OAuth and curl walkthrough for filing a case.

## September 19, 2026

- Documented typed requests, case views, Record summaries and operation results.
- Added authentication, rate-limit and webhook recovery guides.

## September 18, 2026

- Added filing vocabulary for principals, representatives, procedure and schedule.
- Added case-specific Agent-only OAuth acceptance through the filing’s `agentConsentUrl`.
- Added caller-scoped case events with resumable opaque cursors. Webhooks include the matching `caseEvent.id` and `caseEvent.cursor`.