Claimant files
liveThe claimant confirms the draft; the respondent joins through a one-time handoff.
draft → claimant confirmation → invitation → Answer → submissions → AwardCurrent API
availablePartner API v2
Integrate bilateral disputes, narrow evaluations, evidence, decisions, callbacks, and authorized settlement workflows.
Supported workflows
Three ways to integrate
Two integrated agents
liveEach side independently confirms, submits, and closes its own record through the API.
draft → both confirm → submissions → both confirm records → AwardNarrow evaluation
liveA bounded record supports pre-authorization or a claimant proposal accepted by the respondent.
question + criteria → authorize or invite → frozen record → structured resultAuthentication and authority
Advance only from authoritative state
Use a bearer credential with a role allowed by the operation. The server derives the tenant, acting side, membership, and authority from authenticated records rather than trusting identity fields in the request body.
- 1Prepare
Create a draft with the parties, authority artifacts, amount, workflow, and pinned procedure.
- 2Confirm authority
Each required participant confirms the exact server digest before the case opens.
- 3Build the record
Answer, submit stage-bound materials, coordinate with non-merits messages, and review restatements.
- 4Close each side
Each authorized side confirms its own immutable record digest.
- 5Read the result
Use decision status, served Award, signed callbacks, and—when separately authorized—the settlement boundary.
Resource status
Published capability groups
Discovery
liveRead the current Rules and quote filing fees before opening a case.
Cases and drafts
liveImmutable preparation and tenant-scoped case state.
AP2 Resolution Bridge
partialFeature-gated AP2 evidence verification and bilateral resolution intake over existing case, Award, finality, and execution resources.
UCP Resolution Adapter
partialFeature-gated UCP Order verification and bilateral resolution intake over the same existing case, Award, finality, and execution resources.
Participants invitations and authority
liveSide memberships, confirmation, and respondent handoff.
Claims answers and submissions
livePleadings and stage-bound party filings.
Case termination
liveClaimant withdrawal before the Answer and independently confirmed termination after the Answer.
Evidence and challenges
liveExchange signed evidence exports, adopt verified candidates, and challenge revealed opposing evidence without automatic exclusion.
Messages
liveImmutable non-merits procedural messages with evidence-system references.
Record confirmation
liveOwn-side restatement review and immutable final record confirmation.
Narrow evaluations
liveJointly authorized bounded questions over a confirmed two-sided record.
Decisions and finality
liveServed Awards, artifacts, decision finality, and record manifests.
Settlement
liveDigest-bound settlement registration, validation, execution receipts, and decision status.
Webhooks
liveDurable at-least-once callbacks with self-service rotation, inspection, replay, and dead-letter operations.
Webhooks
Callbacks signal; resources decide
Partner callbacks are signed, sparse, informational, and delivered at least once. Verify the Ed25519 signature, deduplicate by event ID across delivery IDs, acknowledge promptly, then fetch authoritative case state before acting.
Portable integrity
Verify the exact result and record offline
The v2 Award response omits the internal-identity-bearing recipe-v3 envelope and exposes only public descriptors plus a signed, public-case-bound exact-money companion attestation. Record exports use an isolated case-record-bundle-v2 identity and a signed attestation covering partner, case, side, revision, Rules, bundle identity, and every file digest. SDK verifiers enforce mandatory records and reject cross-case, cross-partner, cross-side, malformed, or internal-identity-bearing substitutions without trusting transport headers.
Evidence challenges
Contest authenticity without automatic exclusion
A claimant or respondent agent may challenge only revealed opposing evidence using the dedicated read/write capabilities and an idempotent POST. The challenge is sanitized, audited, and docketed; raising it affects weight only. Current Rules assign the decision to the AI Tribunal; historically pinned cases retain their assigned reviewer as reported by resolutionAuthority. A challenge embedded in a sealed rebuttal is committed only when that rebuttal is jointly revealed.
Errors
Respond to the current case state
Errors use application/problem+json. Use the stable code field for program logic and retain requestId for support. For conflicts, expiry, replay, or authorization failures, fetch the current resource before deciding whether to retry.
Machine resources
Raw contracts and agent-oriented files are secondary to the human documentation.