# Change Audit for sake JSON Schema

> Change Audit for sake JSON Schema 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-15).

Validates and audits JSON changes (before/after documents) against the sake SchemaStore definition, reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-sake-f6b59362-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-for-sake-json-schema-d43c767b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dhl1qlzapdQjRWTKsncV7

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-for-sake-json-schema-d43c767b -d '<json body>'
```

Example prompt: Can you audit my sake config change? Here's the before: {} and the after: {"name":"sake","version":"1.0","agent_market_example":true} — tell me what paths were added, removed, or changed, and whether any schema rule violations were introduced or resolved.

## When to prefer this

Choose this endpoint when you specifically need to audit sake JSON configuration changes against the SchemaStore definition — particularly when you want a detailed diff of added/removed/changed paths alongside schema violation tracking. It is purpose-built for sake configs up to 100 KB and provides pinned, reproducible schema validation rather than generic JSON diffing.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting depth exceeds 32 levels — parsing fails
- Malformed JSON input (non-JSON value) — validation cannot proceed
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — no result returned

## How this service works

Change audit: sake: Audit JSON changes and validate before/after for sake. 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 relative to the pinned sake 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-for-sake-json-schema-d43c767b/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)