Review a contract against supplied checks API

Combine clause, obligation, deadline, renewal, checklist, party, and risk checks. checklist_satisfied means the supplied phrases were found. It is not a legal compliance determination.

The Review a contract against supplied checks operation is part of the Contract Operations API on BRAINIAC.software. Combine clause, obligation, deadline, renewal, checklist, party, and risk checks. checklist_satisfied means the supplied phrases were found. It is not a legal compliance determination. It is exposed as POST /api/v1/contract-operations/compliance-review and priced at $0.12 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: The contract text or text-based PDF supplied in the request. A checklist or named standard whose provisions are included in the request. Limitations: Text is read from text-based PDFs and plain text. Scanned pages are not OCR-read. Missing provisions are checked only against the supplied checklist or standard provisions. Extracted wording, potential risks, and unavailable information are separate. The output is not legal advice and does not determine legal compliance. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Extract contract clauses, Extract contract obligations, Extract contract deadlines, Check renewal wording. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.12 USDC
/api/v1/contract-operations/compliance-review

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/contract-operations/compliance-review" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "text": "This Agreement is entered into between Northwind Paper Ltd (\"Buyer\") and Harbor Ink LLC (\"Seller\").\n\n4. Liability\nThe Seller shall indemnify the Buyer against third-party claims.\n",
  "checklist": [
    {
      "id": "liability",
      "name": "Liability"
    },
    {
      "id": "confidentiality",
      "name": "Confidentiality"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Contract Operations APIFull docsHow it works