# Validate Enonic XP Form Fragment Descriptor

> Validate 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-16).

Validates a JSON document against the Enonic XP Form Fragment descriptor schema using a pinned SchemaStore definition

## Facts

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

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

Example prompt: Can you validate this Enonic XP Form Fragment descriptor JSON for me and tell me if there are any schema violations or JSON pointer errors? Here's the document: {"name":"myFragment","form":[{"input":{"name":"title","type":"TextLine"}}]}

## When to prefer this

Choose this endpoint when you specifically need to validate a JSON document against the Enonic XP Form Fragment descriptor schema using the SchemaStore-pinned definition. Prefer it over generic JSON Schema validators when you want Enonic-specific rule enforcement and precise JSON pointer error reporting without setting up local tooling.

## Known failure modes

- Document exceeds 100 KB limit — validation refused
- Nesting depth exceeds 32 levels — validation refused
- Malformed JSON submitted — parse error returned
- Schema definition unavailable or outdated on host machine — may produce unexpected results
- Non-JSON formats (YAML, TOML) not supported — parsing errors returned

## How this service works

Validate Enonic XP Form Fragment descriptor: Validate a JSON document for Enonic XP Form Fragment 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 JSON document conforms to the Enonic XP Form Fragment descriptor schema. On failure, includes JSON pointers to the exact locations of violations and descriptions of the rule(s) broken. On success, confirms the document is valid. Limited to documents up to 100 KB and 32 nesting levels.

## 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-form-fragment-descriptor-c6ce9434/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)