# Change Audit: pgrls Schema Validator

> Change Audit: pgrls 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-19).

Audits JSON changes before and after for pgrls schema compliance, reporting added/removed/changed paths and introduced/resolved validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-pgrls-0df61e87-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-pgrls-schema-validator-9b9e2a2b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GdCNKUmovQN04NXMilCQR

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-pgrls-schema-validator-9b9e2a2b -d '<json body>'
```

Example prompt: I just updated my pgrls config — can you compare the old and new JSON versions and tell me if any new schema violations were introduced, which paths changed, and whether any existing errors were resolved?

## When to prefer this

Use this endpoint when you specifically need schema-aware change auditing for pgrls JSON documents using the pinned SchemaStore definition. It is ideal for CI/CD pipelines, pre-deploy reviews, or debugging configuration regressions where you need to know not just what changed structurally but whether those changes introduced or resolved schema rule violations. Prefer this over generic JSON diff tools when pgrls schema compliance is the concern.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is not valid JSON (e.g. YAML or TOML submitted) — parsing error returned
- Payment of 0.01 USDC not provided or fails — 402 response
- Empty or missing 'after' field — may return empty diff

## How this service works

Change audit: pgrls: Audit JSON changes and validate before/after for pgrls. 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 pointers for all added, removed, and changed paths between the before and after documents, along with a list of newly introduced validation rule violations and any previously existing errors that were resolved, based on the pinned pgrls 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-pgrls-schema-validator-9b9e2a2b/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)