# Enonic XP Task Descriptor Change Audit

> Enonic XP Task 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-19).

Audits JSON changes between before/after versions of an Enonic XP Task descriptor, validating both against a pinned SchemaStore definition and reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-enonic-xp-task-descriptor-86d3a829-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/enonic-xp-task-descriptor-change-audit-bfc318b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TQIaYZSnsbMqSo6N_-c1y

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-task-descriptor-change-audit-bfc318b0 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Enonic XP task descriptor — here's the before version and the after version — and tell me which JSON paths changed, any schema rule violations, and whether I introduced or resolved any errors?

## When to prefer this

Choose this endpoint when you need to specifically audit changes to an Enonic XP Task descriptor JSON file against SchemaStore rules, tracking which paths changed and whether schema errors were introduced or resolved. Prefer it over generic JSON diff tools when Enonic XP schema compliance matters, and over full deployment pipelines when you only need lightweight, schema-aware change validation without YAML support or deployment guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — validation fails
- Invalid JSON provided (YAML/TOML not supported) — parse error
- Schema definition unavailable or stale on the provider's pinned copy — incomplete validation
- Network timeout on large documents near the size limit

## How this service works

Change audit: Enonic XP Task descriptor: Audit JSON changes and validate before/after for Enonic XP Task 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 diff of the two Enonic XP Task descriptor JSON documents including: JSON pointer paths that were added, removed, or changed; schema rule violations in each version; errors introduced by the change; and errors resolved by the change — all validated against a pinned 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/enonic-xp-task-descriptor-change-audit-bfc318b0/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)