# Change Audit: pgap_yaml_input_reader Schema Validator

> Change Audit: pgap_yaml_input_reader 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-12).

Audits JSON changes for pgap_yaml_input_reader by comparing before/after documents against a pinned SchemaStore definition, reporting added/removed/changed paths, JSON pointer violations, and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-pgap-yaml-input-reader-6b0d980d-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-pgap-yaml-input-reader-schema-validator-5cb5bbd6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qQYfbIW7iiw5Vk8RVWY3Z

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-pgap-yaml-input-reader-schema-validator-5cb5bbd6 -d '<json body>'
```

Example prompt: Can you audit my pgap_yaml_input_reader config change — here's the before document and my updated after document — and tell me what paths changed, what new schema violations were introduced, and what errors were resolved?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to a pgap_yaml_input_reader JSON configuration against its pinned SchemaStore definition. It is purpose-built for this schema and reports precise JSON pointer-level diffs with introduced and resolved errors — ideal for CI checks, PR reviews, or pre-deployment validation of pgap_yaml_input_reader configs. Not suitable for YAML/TOML input, other schema types, or security/deployment guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation fails
- YAML or TOML input provided instead of JSON — not supported
- Malformed JSON in before or after field — parse error returned
- Schema definition unavailable or stale on the pinned PC — may produce inaccurate results

## How this service works

Change audit: pgap_yaml_input_reader: Audit JSON changes and validate before/after for pgap_yaml_input_reader. 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 change report including JSON pointers to added, removed, and modified paths between the before and after documents, rule violations against the pinned pgap_yaml_input_reader SchemaStore definition, and a list of introduced and resolved validation errors. Limited to documents up to 100 KB each with up to 32 nesting levels.

## 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-pgap-yaml-input-reader-schema-validator-5cb5bbd6/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)