# Change Audit: Enonic XP Form Fragment Descriptor

> Change Audit: Enonic XP Form Fragment 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-19).

Audits JSON changes between two versions of an Enonic XP Form Fragment descriptor, validating both before/after states and reporting added, removed, or changed paths along with introduced or resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-enonic-xp-form-fragment-de-59b1d78b-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-enonic-xp-form-fragment-descriptor-75c9c34f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BODzDxyRuw6amvP9MQgtb

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-form-fragment-descriptor-75c9c34f -d '<json body>'
```

Example prompt: Can you audit this change to my Enonic XP Form Fragment descriptor — here's the before JSON and the after JSON — and tell me what paths were added, removed, or changed, and whether any new schema violations were introduced?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to an Enonic XP Form Fragment descriptor JSON file, with schema validation against the pinned SchemaStore definition. It is purpose-built for before/after diffing with rule-violation tracking, making it ideal for CI pipelines, code review automation, or change documentation workflows where both structural diffs and schema compliance matter.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parsing error returned
- Schema definition unavailable or stale — validation may reflect pinned rather than current rules
- YAML or TOML input — not supported, must be valid JSON

## How this service works

Change audit: Enonic XP Form Fragment descriptor: Audit JSON changes and validate before/after for Enonic XP Form Fragment 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 containing JSON pointers for every added, removed, and changed path between the before and after documents, a list of schema rule violations present in each version, and a diff of introduced versus resolved errors based on the pinned Enonic XP Form Fragment 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-form-fragment-descriptor-75c9c34f/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)