# Creatomic JSON Change Audit

> Creatomic 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-18).

Audits before/after JSON document pairs against the .creatomic schema, reporting added, removed, and changed JSON pointer paths along with introduced or resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-creatomic-6785f450-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/creatomic-json-change-audit-8054b16c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_764_yV3190Cdrx315sWQ_

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 creatomic-json-change-audit-8054b16c -d '<json body>'
```

Example prompt: Can you audit these two .creatomic JSON files for me — here's the before version and here's the after version — and tell me which paths changed, which were added or removed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you specifically need to validate and diff .creatomic JSON configuration files against the SchemaStore-pinned .creatomic schema definition. It is purpose-built for before/after change auditing of that schema type, providing both structural diff (added/removed/changed paths) and schema compliance delta (introduced/resolved errors) in one call. Prefer alternatives for general-purpose JSON diffing without schema validation, or for other schema types not covered by the .creatomic definition.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing rejected
- Malformed JSON in before or after field — validation cannot proceed
- Network or payment failure — endpoint unreachable
- Schema store definition unavailable — validation results may be incomplete

## How this service works

Change audit: .creatomic: Audit JSON changes and validate before/after for .creatomic. 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 changed between the before and after documents, along with any schema rule violations introduced or resolved by the change, based on the pinned SchemaStore .creatomic 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/creatomic-json-change-audit-8054b16c/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)