# Vextorium JSON Diff

> Vextorium JSON Diff is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-15).

Performs a deep structural comparison of two JSON documents, returning added, removed, and changed values with their exact paths, optionally ignoring list order.

## Facts

- Endpoint: POST https://api.vextorium.com/v1/json-diff?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-json-diff-3e08a21a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wL4KA9FepF3y8QggWqary

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 vextorium-json-diff-3e08a21a -d '<json body>'
```

Example prompt: Compare these two JSON objects and tell me exactly what was added, removed, or changed — I want the full path for each difference: first JSON is {"price":10,"stock":false} and second is {"price":12,"stock":true,"discount":0.1}.

## When to prefer this

Choose this endpoint when you need precise, path-level diff output for two arbitrary JSON documents — especially for API response monitoring, config auditing, or data snapshot comparison. It is purpose-built for JSON (not YAML, XML, or text), supports optional list-order agnosticism, and returns structured change objects with JSONPath routes rather than a raw textual diff, making the output directly machine-consumable by agents.

## Known failure modes

- Missing 'a' or 'b' body fields returns a validation error
- Non-JSON values passed as documents may cause parsing errors
- Extremely large or deeply nested JSON may hit size or timeout limits
- Malformed JSON in either document returns an error response
- Invalid bodyType enum value causes a 400-level error

## How this service works

Deep comparison of two JSON documents: added, removed and changed values with their exact path, optionally ignoring list order. Detect changes in API responses, configs or data snapshots.

## Output

Returns an object with: an 'equal' boolean indicating whether the documents are identical; a 'changes' array where each item includes the change 'type' (added, removed, or changed), the 'route' (JSONPath to the changed field), and 'before'/'after' values where applicable; a 'summary' object with counts of added and changed items; and a 'total_changes' integer.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "a": {
   "description": "First JSON"
  },
  "b": {
   "description": "Second JSON"
  },
  "ignore_list_order": {
   "type": "boolean"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "equal": false,
  "changes": [
   {
    "type": "added",
    "after": true,
    "route": "$.stock"
   },
   {
    "type": "cambiado",
    "after": 12,
    "route": "$.price",
    "before": 10
   }
  ],
  "summary": {
   "added": 1,
   "changed": 2
  },
  "total_changes": 3
 }
}
```

## More

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