# Enonic XP Service Descriptor Change Audit

> Enonic XP Service Descriptor 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 JSON changes between before/after versions of an Enonic XP Service descriptor, validating both against a pinned SchemaStore definition and reporting added/removed/changed paths plus introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-enonic-xp-service-descript-741708c8-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/enonic-xp-service-descriptor-change-audit-bc312f9d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1YBuilbZg4YltbdJ9-06k

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 enonic-xp-service-descriptor-change-audit-bc312f9d -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new Enonic XP service descriptor JSON files — show me what paths were added, removed, or changed, and flag any schema rule violations that were introduced or resolved?

## When to prefer this

Choose this endpoint when you need to audit a specific change to an Enonic XP Service descriptor JSON file against the pinned SchemaStore definition, particularly when you want both a structural diff (added/removed/changed paths) and a schema compliance diff (introduced/resolved errors) in a single call. It is distinct from generic JSON diff tools because it applies Enonic XP Service descriptor-specific schema rules.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing aborted
- Input is not valid JSON (YAML/TOML not supported) — parse error returned
- Malformed request body — validation failure returned
- Network or payment processing error — 402 or 5xx response

## How this service works

Change audit: Enonic XP Service descriptor: Audit JSON changes and validate before/after for Enonic XP Service 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

Returns a structured audit report listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations found in either version, and a summary of errors introduced or resolved by the change. Limited to documents up to 100 KB and 32 nesting 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/enonic-xp-service-descriptor-change-audit-bc312f9d/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)