# Data Toolkit – JSON Diff

> Data Toolkit – JSON Diff is a paid API for AI agents from data.openverbs.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Computes a structured diff between two JSON documents, showing what changed from source to target.

## Facts

- Endpoint: POST https://data.openverbs.com/v1/diff
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/data-toolkit-json-diff-c670e062
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VQUEQR7Wfp8EaAJYdRKxT

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 data-toolkit-json-diff-c670e062 -d '<json body>'
```

Example prompt: Compare these two JSON objects and tell me exactly what changed — here's the original: {"name":"Alice","age":30} and the updated version: {"name":"Alice","age":31,"city":"NYC"}.

## When to prefer this

Choose this endpoint when you need a programmatic, structured diff between two JSON documents — especially in automation pipelines, CI/CD change detection, API response comparison, or data migration validation. Prefer it over text-based diff tools when your data is structured JSON and you need machine-readable output about what changed.

## Known failure modes

- Missing 'source' or 'target' fields returns a validation error
- Non-JSON or malformed body fields cause parsing failures
- Very deeply nested or extremely large JSON documents may time out or hit size limits
- Passing non-object JSON types (arrays, primitives) at the root may produce unexpected results
- Network or payment authorization failure returns a 402 or 5xx error

## How this service works

Compute the RFC 6902 JSON Patch that transforms `source` into `target`. The patch is a minimal array of add/remove/replace operations.

## Output

A structured representation of the differences between the source and target JSON documents, including which fields were added, removed, or modified, expressed as a JSON diff or patch object.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "source",
      "target"
     ],
     "properties": {
      "source": {
       "description": "The original JSON document."
      },
      "target": {
       "description": "The desired JSON document."
      }
     },
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-toolkit-json-diff-c670e062/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from data.openverbs.com](https://www.zero.xyz/host/data.openverbs.com/llms.txt)
