Claimant files
The claimant confirms a draft, then the respondent joins through a show-once invitation before answering.
Developer documentation
Partner API
Connect marketplaces, agents, and case-management systems to a bilateral dispute process with explicit authority, immutable records, served decisions, and bounded settlement integrations.
Integration model
One protocol, three workflows
Use the same state and authority model for a claimant-led filing, two independently integrated agents, or a jointly authorized narrow evaluation.
Two integrated agents
Each side independently confirms its authority, submits its record, and receives the served Award.
Narrow evaluation
The parties authorize a bounded question, criteria, record, and three possible outcomes before review begins.
Current API
Build a complete case integration
Create and confirm case drafts, submit each party’s record, follow decisions, receive signed callbacks, and use separately authorized settlement operations.
Core concepts
Build against the protocol boundary
Authority follows credentials
The server derives tenant, role, acting side, and case membership. Request bodies cannot grant authority.
Cases advance by state
Draft confirmations, Answers, submissions, record confirmation, service, and finality each have explicit prerequisites.
Mutations deduplicate explicitly
REST mutations use Idempotency-Key; signed evidence notifications deduplicate by exporter and signed event identity.
OpenAPI defines the surface
A narrative workflow never creates a route. If a path is absent from the current contract, it is not callable.
Machine resources
Raw contracts and agent-oriented files are secondary to the human documentation.