# Validate Enonic XP API Descriptor

> Validate Enonic XP API 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 a JSON document against the Enonic XP API descriptor schema using a pinned SchemaStore definition, reporting any JSON pointer violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-enonic-xp-api-descriptor-b74c253d-validate?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/validate-enonic-xp-api-descriptor-574a289c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aly6EbUCQDMYmU5KK-a3E

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 validate-enonic-xp-api-descriptor-574a289c -d '<json body>'
```

Example prompt: Can you validate this Enonic XP API descriptor JSON for me and tell me if it has any schema violations or JSON pointer errors? Here's the document: {"api":"com.enonic.app.myapp:myapi","version":"1.0","operations":{"get":{"description":"Fetch resource"}}}

## When to prefer this

Choose this endpoint when you need to validate a JSON document specifically against the Enonic XP API descriptor schema. It uses a pinned SchemaStore definition, making it suitable for deterministic, reproducible validation results without relying on live schema fetches. Prefer it over generic JSON Schema validators when Enonic XP-specific rule enforcement and JSON pointer reporting are required.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- Document nesting exceeds 32 levels — rejected
- Invalid JSON submitted (not parseable) — parse error returned
- Schema definition mismatch if submitted document uses unsupported Enonic XP version fields
- Network or service timeout for large documents near size limit

## How this service works

Validate Enonic XP API descriptor: Validate a JSON document for Enonic XP API descriptor. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one JSON document validation.

## Output

Returns a validation report indicating whether the submitted JSON document conforms to the Enonic XP API descriptor schema, including specific JSON pointer paths and descriptions of any rule violations found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "document": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/validate-enonic-xp-api-descriptor-574a289c/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)