# Validate replacement-transformer.yaml

> Validate replacement-transformer.yaml 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-12).

Validates a JSON document against the pinned SchemaStore definition for replacement-transformer.yaml, reporting JSON pointer violations and rule errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-replacement-transformer-ya-aa4223ef-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/validate-replacement-transformer-yaml-99ffc98d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5Cj7wisAunyp2M1FP2Kwr

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-replacement-transformer-yaml-99ffc98d -d '<json body>'
```

Example prompt: Can you validate this replacement-transformer.yaml config for me — here's the JSON: {"source": "field_a", "target": "field_b"} — check it against the SchemaStore schema and tell me any rule violations or JSON pointer errors.

## When to prefer this

Use this endpoint when you specifically need to validate a JSON document against the replacement-transformer.yaml SchemaStore schema. Prefer this over generic JSON Schema validators when you want pinned, deterministic validation tied to the exact replacement-transformer.yaml spec without managing schema files yourself.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — validation refused
- Malformed JSON input — parse error returned
- Schema definition unavailable or pinned version mismatch — validation may be incomplete
- No violations found — clean pass returned (not an error, but may be unexpected)

## How this service works

Validate replacement-transformer.yaml: Validate a JSON document for replacement-transformer.yaml. 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 result indicating whether the submitted JSON document conforms to the replacement-transformer.yaml SchemaStore schema, including 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-replacement-transformer-yaml-99ffc98d/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)