# Cinnamon Spice Metadata JSON Change Audit

> Cinnamon Spice Metadata 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-14).

Audits JSON changes between before/after documents for Cinnamon spice metadata, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-metadata-for-a-cinnamon-sp-ace4c392-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/cinnamon-spice-metadata-json-change-audit-dfda3ba7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NDsqw6ic6gOpT0T09za2A

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 cinnamon-spice-metadata-json-change-audit-dfda3ba7 -d '<json body>'
```

Example prompt: Can you audit the change I made to my Cinnamon spice metadata JSON — here's the before and after document — and tell me which fields were added, removed, or changed, and whether any schema rules were violated?

## When to prefer this

Choose this endpoint when you need to audit changes specifically to Cinnamon spice metadata JSON documents against a pinned SchemaStore definition, particularly to detect schema regressions, track field-level diffs, and surface rule violations introduced or resolved between two document versions. It is not a general-purpose JSON differ and is scoped to this specific spice metadata schema.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing refused
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML input submitted instead of JSON — not supported
- Payment not completed — request not processed

## How this service works

Change audit: Metadata for a Cinnamon spice: Audit JSON changes and validate before/after for Metadata for a Cinnamon spice. 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 containing JSON pointers to changed locations, lists of added/removed/changed paths, rule violations (introduced and resolved), and a comparison of schema compliance between the before and after documents. Up to 100 KB per document with a maximum nesting depth of 32 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/cinnamon-spice-metadata-json-change-audit-dfda3ba7/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)