# Change Audit: Glamour Style JSON Schema Validator

> Change Audit: Glamour Style 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 Glamour style SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-glamour-style-9a02a020-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-glamour-style-json-schema-validator-4950ca94
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_U6cqT_UsZ-gauNpbebVaa

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-glamour-style-json-schema-validator-4950ca94 -d '<json body>'
```

Example prompt: Can you audit this JSON change for me? Here's the before: {} and after: {"theme": "glamour", "colors": ["gold", "black"]} — check it against the Glamour style schema and tell me what paths changed and whether any new validation errors were introduced.

## When to prefer this

Use this endpoint when you specifically need to validate JSON changes against the Glamour style SchemaStore definition — it is ideal for CI/CD checks, PR reviews, or debugging regressions in Glamour-style configuration files. Prefer it over generic JSON diff tools when schema rule compliance (not just structural diff) is required for Glamour style documents.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — 402 or 5xx response

## How this service works

Change audit: Glamour style: Audit JSON changes and validate before/after for Glamour style. 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 for all added, removed, and changed paths between the before and after documents, along with any schema rule violations introduced or resolved by the change, validated against the pinned Glamour style 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-glamour-style-json-schema-validator-4950ca94/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)