# Change Audit: Enonic XP Layout Descriptor

> Change Audit: Enonic XP Layout Descriptor 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 diffs two JSON documents representing before/after states of an Enonic XP Layout descriptor, reporting changed paths, rule violations, and introduced or resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-enonic-xp-layout-descripto-1f1e3c18-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-enonic-xp-layout-descriptor-2426f38c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7CMMK7CACK5rMTUqcIpUC

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-enonic-xp-layout-descriptor-2426f38c -d '<json body>'
```

Example prompt: I updated our Enonic XP layout descriptor — can you compare the before and after JSON and tell me which paths changed, any rule violations that were introduced, and whether any existing errors got resolved?

## When to prefer this

Choose this endpoint when you need to specifically validate and diff Enonic XP Layout descriptor JSON documents against the pinned SchemaStore definition. It is purpose-built for this schema type rather than being a generic JSON diff tool, making it the right choice when Enonic XP CMS layout descriptor compliance and change tracking matter.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON submitted (non-parseable) — error returned
- Malformed request body — validation skipped
- Network or payment processing failure — no result returned

## How this service works

Change audit: Enonic XP Layout descriptor: Audit JSON changes and validate before/after for Enonic XP Layout descriptor. 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 any schema rule violations, newly introduced errors, and resolved errors based on the pinned Enonic XP Layout descriptor 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-enonic-xp-layout-descriptor-2426f38c/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)