# Change Audit: modelparams.dev Model JSON Validator

> Change Audit: modelparams.dev Model JSON 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-18).

Audits before/after JSON documents for a modelparams.dev Model schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-modelparams-dev-model-d43b3955-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-modelparams-dev-model-json-validator-eba1baa5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-D_D9zdLRfMKEqUhq8_1x

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-modelparams-dev-model-json-validator-eba1baa5 -d '<json body>'
```

Example prompt: Can you audit the change I made to my modelparams.dev model config — here's the before JSON and the after JSON — and tell me what paths changed, what new validation errors appeared, and what errors got resolved?

## When to prefer this

Choose this endpoint when you specifically need to validate JSON documents against the modelparams.dev Model schema and want a diff-style audit of what changed between two versions. It is purpose-built for this schema (using a pinned SchemaStore definition) rather than a generic JSON differ, making it more accurate for modelparams.dev Model compliance checks. Prefer it over generic JSON diff tools when schema rule violations and error delta tracking matter.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing refused
- Invalid JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — no result returned

## How this service works

Change audit: modelparams.dev Model: Audit JSON changes and validate before/after for modelparams.dev Model. 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 including JSON pointers for all added, removed, and changed paths between the before and after documents, along with lists of validation errors introduced and resolved relative to the pinned modelparams.dev Model SchemaStore definition, and any rule violations found in either document.

## 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-modelparams-dev-model-json-validator-eba1baa5/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)