# Change Audit: Jasmine Schema Validator

> Change Audit: Jasmine 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-24).

Audits JSON document changes against the Jasmine SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors between before and after versions.

## Facts

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

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-jasmine-schema-validator-5395d50b -d '<json body>'
```

Example prompt: Can you audit the changes I made to my jasmine.json — here's the before version and the updated after version — and tell me which JSON paths were added, removed, or changed, and whether any new schema violations were introduced?

## When to prefer this

Choose this endpoint when you need to validate JSON configuration changes specifically against the Jasmine schema definition and want a detailed diff of changed paths alongside introduced or resolved validation errors. It is purpose-built for Jasmine config auditing using a pinned SchemaStore definition, making it more reliable than a generic JSON differ or schema validator when Jasmine-specific rules matter.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing refused
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML input submitted — not supported, only JSON accepted
- Network or payment processing failure — no result returned

## How this service works

Change audit: Jasmine: Audit JSON changes and validate before/after for Jasmine. 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 pointer paths that were added, removed, or modified between the before and after documents, along with any schema rule violations that were introduced or resolved, based on a pinned Jasmine 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-jasmine-schema-validator-5395d50b/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)