# BRAINIAC Contract Compare — JSON Schema Diff & Breaking Change Detector

> BRAINIAC Contract Compare — JSON Schema Diff & Breaking Change Detector is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.05/call, status unknown (last checked 2026-11-17).

Compares two JSON schemas (or contract versions) to detect breaking and non-breaking changes, type mismatches, and required-field differences between API request or response shapes.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/api-integration/contract-compare?utm_source=zero.xyz
- Price: $0.05/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-compare-json-schema-diff-breaking-change-detector-0fb0dbc3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CeclFGXoskqIfu2wBRF9G

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-compare-json-schema-diff-breaking-change-detector-0fb0dbc3 -d '<json body>'
```

Example prompt: Compare these two JSON schemas and tell me which changes are breaking — the old response schema required `total` as a number, the new one requires it as an integer and also adds a `currency` field as required. I want to know what broke on the response side.

## When to prefer this

Use this endpoint when you need a deterministic, privacy-safe, no-external-call schema diff — it runs entirely in-process, invents no values, and executes no user code, making it safe for sensitive internal schemas. Prefer it over manual diff tools or LLM-based comparison when you need structured, machine-readable change records with breaking/non-breaking labels and a clear audit trail of what was checked. It is especially valuable in CI pipelines, API governance workflows, or agent-driven migration planning where $0.05 pay-per-call is acceptable and no standing subscription is needed.

## Known failure modes

- Malformed or invalid JSON schema input causes a parse error or empty change set
- Schema exceeds max size limits (file base64 up to 12MB, json up to 200KB)
- Unsupported JSON Schema keywords are reported but not evaluated — edge cases may be missed
- A field mapping heuristic may miss renames when path and name don't match
- Breaking/non-breaking labels are only returned when `side` is explicitly set to 'request' or 'response'; omitting it may yield unlabeled results
- mediaType must match actual content (application/json or text/plain); mismatch causes rejection

## How this service works

Pay-per-call APIs for software agents. No account. Pay the listed USDC amount on Base with x402, then receive the result.

## Output

Returns a JSON object with a `status` field ('compared'), a `side` field (request or response), a `changes` array where each entry has a `code` (e.g. 'type_changed', 'required_added'), a `path`, `before`/`after` values, a `detail` description, and an `effect` label ('breaking' or 'non-breaking'). Also includes a `checkedAt` timestamp, a `limitations` array describing what the engine does and does not cover, and boolean flags: `codeExecuted`, `externalCall`, `valuesInvented`, `schemaCompliance`.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "file": {
   "type": "object",
   "required": [
    "mediaType",
    "fileBase64"
   ],
   "properties": {
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "application/json",
      "text/plain"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "side": {
   "enum": [
    "request",
    "response"
   ],
   "type": "string"
  },
  "after": {
   "$ref": "#/$defs/__schema0"
  },
  "before": {
   "$ref": "#/$defs/__schema0"
  },
  "schema": {
   "$ref": "#/$defs/__schema0"
  },
  "source": {
   "$ref": "#/$defs/__schema0"
  },
  "target": {
   "$ref": "#/$defs/__schema0"
  },
  "example": {
   "$ref": "#/$defs/__schema0"
  },
  "payload": {
   "$ref": "#/$defs/__schema0"
  },
  "examples": {
   "type": "array",
   "items": {
    "$ref": "#/$defs/__schema0"
   },
   "maxItems": 20
  },
  "toVersion": {
   "type": "string",
   "maxLength": 40,
   "minLength": 1
  },
  "operations": {
   "type": "array",
   "items": {
    "oneOf": [
     {
      "type": "object",
      "required": [
       "op",
       "from",
       "to"
      ],
      "properties": {
       "op": {
        "type": "string",
        "const": "rename"
       },
       "to": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       },
       "from": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       }
      },
      "additionalProperties": false
     },
     {
      "type": "object",
      "required": [
       "op",
       "from",
       "to"
      ],
      "properties": {
       "op": {
        "type": "string",
        "const": "copy"
       },
       "to": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       },
       "from": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       }
      },
      "additionalProperties": false
     },
     {
      "type": "object",
      "required": [
       "op",
       "paths"
      ],
      "properties": {
       "op": {
        "type": "string",
        "const": "pick"
       },
       "paths": {
        "type": "array",
        "items": {
         "type": "string",
         "maxLength": 200,
         "minLength": 1
        },
        
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "side": "response",
  "issues": [],
  "status": "compared",
  "changes": [
   {
    "code": "required_added",
    "path": "/total",
    "after": "total",
    "before": "",
    "detail": "This property is newly required.",
    "effect": "breaking"
   },
   {
    "code": "type_changed",
    "path": "/total",
    "after": "integer",
    "before": "number",
    "detail": "The type allows fewer values.",
    "effect": "breaking"
   }
  ],
  "checkedAt": "2026-11-03T15:00:00.000Z",
  "limitations": [
   "No external API is called and no user-supplied code is executed.",
   "Validation covers type, properties, required, additionalProperties, items, enum, const, length, range, and the formats email, date, and date-time. Other JSON Schema keywords are reported and not applied.",
   "A generated schema uses only values present in the supplied examples. additionalProperties stays true.",
   "A field mapping is proposed only when the path matches or the field name matches one field on each side.",
   "Breaking and non-breaking labels are returned only when side is request or response.",
   "Transforms are rename, copy, pick, omit, cast, and default. A default is written only when the path is absent."
  ],
  "codeExecuted": false,
  "externalCall": false,
  "valuesInvented": false,
  "schemaCompliance": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-contract-compare-json-schema-diff-breaking-change-detector-0fb0dbc3/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)
