# People’s Court Partner API skill

Use this guide when an agent must integrate with the People’s Court Partner API.

1. Read `/llms.txt` to find the current integration guides and endpoint reference.
2. Read the canonical contract at `/openapi/partner-v2.json` before constructing a request.
3. Choose exactly one supported intake mode: `claimant_initiated`, `claimant_proposed`, `bilateral_api`, or `bundled_bilateral`. Narrow evaluations use `caseMode: evaluation`; use `claimant_proposed` when the respondent will accept the digest by invitation.
4. Create a case draft and present its Rules stamp, fee, procedure, digest, participants, and exact confirmation statements before confirming.
5. Never infer authority from a body-supplied side. Use the credential role and confirmed case membership for the acting party.
6. Reuse an `Idempotency-Key` only for an identical retry.
7. Submit only through the current server-selected stage and follow the documented case lifecycle.
8. Confirm only the acting party’s final own-side record.
9. Treat callbacks as notifications, fetch authoritative state, and verify the served Award signature.
10. Never reinterpret a generic split or conditional Award as an evaluation outcome; require one authorized outcome and one structured finding per criterion.
11. Never expose API keys, invitations, party capabilities, wallet signatures, or evidence bytes in logs or model output.
12. Use `/messages` only for the five bounded procedural categories. A message or evidence reference never adds to or reopens the merits record.
13. Verify v2 JSON Awards with their companion derivative attestation; do not treat them as replacements inside the frozen recipe-v3 source manifest.
14. Treat an authenticity challenge as a contested-weight notice only. Raising never excludes evidence. Current Rules assign the decision to the AI Tribunal; historical cases retain the pinned reviewer identified by `resolutionAuthority`.

Settlement bindings and executions require the exact digest-bound OpenAPI paths and a dedicated adapter credential; never infer execution from `decision_served`.

For callbacks, verify signatures, deduplicate by `eventId`, treat `sequence` as an enqueue cursor rather than a delivery-order guarantee, and fetch authoritative state. Use `deliveryId` only for inspection/replay operations.