# Change Audit: Drupal Migration JSON Schema Validator

> Change Audit: Drupal Migration JSON Schema Validator is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Audits JSON before/after document pairs against a pinned Drupal Migration SchemaStore definition, reporting added, removed, and changed paths plus introduced and resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-drupal-migration-0235ed9c-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-drupal-migration-json-schema-validator-b92c9ff5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cfoWKtIL8e7KDlIAmghTT

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 change-audit-drupal-migration-json-schema-validator-b92c9ff5 -d '<json body>'
```

Example prompt: Can you audit my Drupal Migration config changes and tell me which JSON paths were added, removed, or changed, and whether any new schema violations were introduced or old ones resolved? Here's the before document and the updated after document.

## When to prefer this

Choose this endpoint when you specifically need to validate JSON changes against the pinned Drupal Migration SchemaStore definition and want a structured diff of compliance changes (introduced/resolved errors and path-level changes). It is purpose-built for Drupal migration configuration auditing, not general-purpose JSON diffing or YAML/TOML validation.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON provided in before or after field — parse error returned
- Payment of 0.01 USDC not completed — request not processed
- SchemaStore definition unavailable or pinned version mismatch — validation may fail silently

## How this service works

Change audit: Drupal Migration: Audit JSON changes and validate before/after for Drupal Migration. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations, added/removed/changed paths and introduced/resolved errors. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one two-document change audit.

## Output

Returns a structured report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any SchemaStore rule violations that were introduced or resolved, giving a clear picture of schema compliance changes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "default": {
    "agent_market_example": true
   },
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  },
  "before": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/change-audit-drupal-migration-json-schema-validator-b92c9ff5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)