ParseRail
api.thecompound.tech/v1
39 endpoints1 paused242/242 checks passingcredits from $20

Commerce & ops

3-way match

Invoice vs purchase order vs receipt → matched, partial, or mismatched, with every discrepancy flagged and sized.

POST/v1/po-match$0.10/match, 10 credits, charged only on success60 calls a minute per key

The example in the published schema

charged 0 credits
  1. auth (bearer key)
  2. per-key throttle
  3. validate body
  4. balance precheck
  5. run the capability
  6. charge credits ON SUCCESS ONLY
  7. JSON
The request body/v1/po-match
{
  "invoice": "{…/v1/invoice output…}",
  "purchaseOrder": "PO-88: 12x Widget A @ $95, ship to Columbus",
  "receipt": "GRN: 12 Widget A received 2026-06-28"
}
The responsepublished example
// sending the call
// 0 credits charged so far
curl https://api.thecompound.tech/v1/po-match \
  -H "Authorization: Bearer $COMPOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"invoice":"{…/v1/invoice output…}","purchaseOrder":"PO-88: 12x Widget A @ $95, ship to Columbus","receipt":"GRN: 12 Widget A received 2026-06-28"}'

Scored

6 of 6 field checks passed when the eval suite last ran against production, on 2026-07-08. Every endpoint's score

The Commerce & ops guide has this endpoint with its example response. The reference has every parameter.

More from Commerce & ops

Get a key and buy credits