# Change Audit: maturin JSON Schema Validator

> Change Audit: maturin 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-23).

Audits before/after JSON document pairs against the maturin schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-maturin-60fa2b01-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-maturin-json-schema-validator-7ec95937
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HYdPEa3JXhmrjEDrKmgkV

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-maturin-json-schema-validator-7ec95937 -d '<json body>'
```

Example prompt: Can you audit my maturin config change — here's the before and after JSON — and tell me which fields were added, removed, or changed, and whether the new version introduces or resolves any schema validation errors?

## When to prefer this

Choose this endpoint when you specifically need to validate changes to a maturin configuration file (pyproject.toml-style JSON) against the SchemaStore maturin schema, with a clear before/after diff of paths and errors. Prefer this over generic JSON diff tools when maturin schema compliance is required, and over general schema validators when you need combined diff + validation in one call.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML input format — not supported, must be JSON
- Schema unavailable or pinned definition mismatch — validation may be incomplete

## How this service works

Change audit: maturin: Audit JSON changes and validate before/after for maturin. 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 pointers to all added, removed, and changed paths between the before and after documents, plus which schema rule violations were introduced in or resolved from the after document, according to a pinned SchemaStore maturin schema definition.

## 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-maturin-json-schema-validator-7ec95937/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)