# Validate Enonic XP ID Provider Descriptor

> Validate Enonic XP ID Provider 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 ID Provider descriptor schema using a pinned SchemaStore definition

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-enonic-xp-id-provider-desc-7bd9e5a7-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-id-provider-descriptor-0e7aca16
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ATxsjBM5CjyNwfIaFWjkw

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-id-provider-descriptor-0e7aca16 -d '<json body>'
```

Example prompt: Can you validate this JSON against the Enonic XP ID Provider descriptor schema and tell me which fields are wrong or missing? Here's the document: {"idProvider":{"mode":"AUTO","applications":[]}}

## When to prefer this

Use this endpoint when you need to validate a JSON document specifically conforming to the Enonic XP ID Provider descriptor schema. It uses a pinned SchemaStore definition, making it ideal for deterministic, reproducible validation in CI pipelines or pre-deployment checks for Enonic XP identity provider configurations. It is not suitable for YAML/TOML inputs or for guaranteeing deployment or security compliance.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- Document nesting exceeds 32 levels — parsing refused
- Invalid JSON submitted (not parseable) — error returned
- Network timeout or service unavailability
- Schema definition mismatch if the pinned SchemaStore version differs from the target Enonic XP version

## How this service works

Validate Enonic XP ID Provider descriptor: Validate a JSON document for Enonic XP ID Provider 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 structured validation report identifying JSON pointer locations and specific rule violations found in the submitted Enonic XP ID Provider descriptor JSON document, or confirms the document is valid according to the pinned SchemaStore definition.

## 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-id-provider-descriptor-0e7aca16/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)