# Jekyll JSON Change Audit

> Jekyll JSON Change Audit 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 before/after JSON document pairs against the pinned Jekyll SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-jekyll-937fbff1-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/jekyll-json-change-audit-b095b363
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Cb021Zki8x6TjuBt2Ihhx

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 jekyll-json-change-audit-b095b363 -d '<json body>'
```

Example prompt: Can you audit my Jekyll config change and tell me which JSON paths were added, removed, or changed and whether any new schema errors were introduced or old ones resolved? Here's the before and after JSON.

## When to prefer this

Choose this endpoint when you need to validate a Jekyll site's JSON configuration change against the official SchemaStore Jekyll schema definition, specifically to understand the diff in terms of added/removed/changed paths and whether schema errors were introduced or resolved. Prefer this over generic JSON diff tools when Jekyll-specific schema compliance and error tracking across a change are both required.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is YAML or TOML instead of JSON — not supported, no parsing performed
- Malformed JSON submitted — parse error returned
- Payment not received — 402 response, audit not performed

## How this service works

Change audit: Jekyll: Audit JSON changes and validate before/after for Jekyll. 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

A structured audit report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations introduced or resolved relative to the pinned Jekyll SchemaStore definition, covering documents up to 100 KB and 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/jekyll-json-change-audit-b095b363/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)