# BRAINIAC Contract Change Impact Analyzer

> BRAINIAC Contract Change Impact Analyzer is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.06/call, status unknown (last checked 2026-11-17).

Compares a base and revised contract (or document) and identifies the legal impact of each change, such as altered dates, periods, added/removed clauses, and potential risks.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/contract-operations/change-impact?utm_source=zero.xyz
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-contract-change-impact-analyzer-b79edbd0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2HXrapKr5G4l-n92WoGXM

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-contract-change-impact-analyzer-b79edbd0 -d '<json body>'
```

Example prompt: Compare these two versions of our supplier agreement — the original and the amended one — and tell me exactly what changed: any dates, delivery periods, or new clauses that were added or removed, and flag anything that looks like a potential legal risk.

## When to prefer this

Choose this endpoint when you need to programmatically detect and classify the legal impact of changes between two versions of a contract or legal document, especially when you want structured output per changed clause (dates, periods, additions, removals, risks). It is particularly well-suited for agent workflows that need to flag material contract changes without requiring a human to manually redline. Prefer this over generic diff tools when you need legally-contextualized impact labels (e.g. 'period changed', 'clause added') rather than raw text diffs. It supports both PDF and plain text input and structured clause arrays, making it flexible for various document ingestion pipelines.

## Known failure modes

- Both base and revised inputs missing — request will fail or return empty results
- Document too large — fileBase64 maxLength is 12MB; oversized files will be rejected
- Unsupported media type — only application/pdf and text/plain are accepted
- Malformed base64 encoding — invalid encoded file content causes parse errors
- No meaningful differences detected — returns status with empty impacts array
- Clause array exceeds 80 items — requests with more clauses will be rejected

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with a list of impacts, each describing the kind of change (e.g. period changed, date changed, clause added), the affected clause heading, excerpts from both the base and revised text, and a detail explanation. Also includes a status field, a checkedAt timestamp, and a limitations array reminding that this is not legal advice and no legal compliance determination is made.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "base": {
   "type": "object",
   "properties": {
    "file": {
     "type": "object",
     "required": [
      "mediaType",
      "fileBase64"
     ],
     "properties": {
      "filename": {
       "type": "string",
       "maxLength": 180,
       "minLength": 1
      },
      "mediaType": {
       "enum": [
        "application/pdf",
        "text/plain"
       ],
       "type": "string"
      },
      "fileBase64": {
       "type": "string",
       "maxLength": 12000000,
       "minLength": 1
      }
     },
     "additionalProperties": false
    },
    "text": {
     "type": "string",
     "maxLength": 200000,
     "minLength": 1
    },
    "clauses": {
     "type": "array",
     "items": {
      "type": "object",
      "required": [
       "heading",
       "text"
      ],
      "properties": {
       "text": {
        "type": "string",
        "maxLength": 20000,
        "minLength": 1
       },
       "number": {
        "type": "string",
        "maxLength": 40,
        "minLength": 1
       },
       "heading": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       }
      },
      "additionalProperties": false
     },
     "maxItems": 80
    }
   },
   "additionalProperties": false
  },
  "revised": {
   "type": "object",
   "properties": {
    "file": {
     "type": "object",
     "required": [
      "mediaType",
      "fileBase64"
     ],
     "properties": {
      "filename": {
       "type": "string",
       "maxLength": 180,
       "minLength": 1
      },
      "mediaType": {
       "enum": [
        "application/pdf",
        "text/plain"
       ],
       "type": "string"
      },
      "fileBase64": {
       "type": "string",
       "maxLength": 12000000,
       "minLength": 1
      }
     },
     "additionalProperties": false
    },
    "text": {
     "type": "string",
     "maxLength": 200000,
     "minLength": 1
    },
    "clauses": {
     "type": "array",
     "items": {
      "type": "object",
      "required": [
       "heading",
       "text"
      ],
      "properties": {
       "text": {
        "type": "string",
        "maxLength": 20000,
        "minLength": 1
       },
       "number": {
        "type": "string",
        "maxLength": 40,
        "minLength": 1
       },
       "heading": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       }
      },
      "additionalProperties": false
     },
     "maxItems": 80
    }
   },
 
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "changes_found",
  "impacts": [
   {
    "kind": "extracted",
    "aspect": "period",
    "change": "changed",
    "detail": "A stated period in the clause changed.",
    "heading": "Supply",
    "baseExcerpt": "1. Supply The Seller shall deliver the Goods within 14 days after each order.",
    "revisedExcerpt": "1. Supply The Seller shall deliver the Goods within 30 days after each order."
   },
   {
    "kind": "extracted",
    "aspect": "date",
    "change": "changed",
    "detail": "A calendar date in the clause changed.",
    "heading": "Term",
    "baseExcerpt": "2. Term This Agreement expires on 1 November 2027.",
    "revisedExcerpt": "2. Term This Agreement expires on 1 November 2028."
   },
   {
    "kind": "potential_risk",
    "aspect": "clause_added",
    "change": "added",
    "detail": "A clause is present only in the revised text. The legal effect was not determined.",
    "heading": "Confidentiality",
    "baseExcerpt": "",
    "revisedExcerpt": "3. Confidentiality The Seller shall keep the Buyer's information confidential."
   }
  ],
  "findings": [],
  "checkedAt": "2026-11-02T19:00:00.000Z",
  "legalAdvice": false,
  "limitations": [
   "This output is not legal advice.",
   "A checklist match is not a determination of legal compliance.",
   "Clauses, deadlines, obligations, and missing provisions are not invented.",
   "Missing provisions are reported only against a checklist or standard provisions supplied in the request.",
   "An impact names the kind of text that changed. It does not decide whether the change is favorable or enforceable."
  ],
  "complianceDetermined": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-contract-change-impact-analyzer-b79edbd0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
