# Validate Embrace Config

> Validate Embrace Config 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 pinned SchemaStore definition for Embrace Config, reporting JSON pointer paths and rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-embrace-config-23b51aaa-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-embrace-config-9d5bcba0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zIT539LvhmeEkZRl8tZaM

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-embrace-config-9d5bcba0 -d '<json body>'
```

Example prompt: Can you validate this Embrace Config JSON for me and tell me exactly which fields are wrong or missing — here's the document: {"appId": "abc123", "apiToken": "", "sdkConfig": {"networking": true}}

## When to prefer this

Use this endpoint when you specifically need to validate a JSON document against the Embrace Config schema using a pinned SchemaStore definition. It is purpose-built for Embrace SDK configuration files and returns precise JSON pointer locations for violations, making it ideal for CI pipelines, pre-deployment checks, and debugging malformed Embrace configs. Prefer it over generic JSON schema validators when you want Embrace-specific schema enforcement without setting up local tooling.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — validation refused
- Malformed JSON submitted (not parseable) — parse error returned
- YAML or TOML format submitted instead of JSON — not supported
- Network timeout or service unavailability — HTTP error response

## How this service works

Validate Embrace Config: Validate a JSON document for Embrace Config. 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 result indicating whether the JSON document conforms to the pinned SchemaStore Embrace Config schema, along with a list of 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-embrace-config-9d5bcba0/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)