# Change Audit: Grunt Base Task JSON Schema Validator

> Change Audit: Grunt Base Task 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-14).

Audits JSON changes between a before/after document pair against the Grunt base task schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-grunt-base-task-9fd2854a-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-grunt-base-task-json-schema-validator-73244c13
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_515ftcjdzkgTck90CKJj_

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-grunt-base-task-json-schema-validator-73244c13 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Grunt base task config? Here's the before state and the after state — tell me which paths were added or removed and whether any new schema violations were introduced.

## When to prefer this

Choose this endpoint when you need to validate Grunt base task configuration changes specifically against the pinned SchemaStore definition, and want a structured diff showing exactly which paths changed and which schema violations were introduced or resolved. It is purpose-built for Grunt base task schema auditing, not general-purpose JSON diffing or other config formats.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — validation cannot proceed
- YAML or TOML input not supported — must convert to JSON first
- Network or payment failure via x402 protocol

## How this service works

Change audit: Grunt base task: Audit JSON changes and validate before/after for Grunt base task. 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 diff report including JSON pointer paths for all added, removed, and changed properties between the before and after documents, plus a list of schema rule violations introduced or resolved by the change, based on the pinned Grunt base task SchemaStore 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-grunt-base-task-json-schema-validator-73244c13/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)