Skip to main content
POST
Reconcile several objects that describe the same thing — typically the outputs of repeated extractions over one document — into a single consensus object, with a likelihoods map giving the agreement score for every leaf path. Low-likelihood paths are the ones worth routing to review. Inputs are always aligned before the vote, so items in a list are matched across inputs by content rather than by position: a reordered or partially omitted array still reconciles correctly. Supply json_schema whenever you have one — it makes numeric fields reconcile by declared type (integer votes on the exact value, number clusters and averages) instead of inferring the kind from whichever values happen to be present.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
inputs
Inputs · object[] | null
required
include_alignment
boolean
json_schema
Json Schema · object

Response

Successful Response

alignment
ReconciliationAlignment · object
required
consensus
Consensus · object
required
fields
ReconciliationField · object[] | null
required
likelihoods
Likelihoods · object
required