# Validate AnyWork Automation Configuration

> Validate AnyWork Automation Configuration 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-18).

Validates a JSON document against the pinned SchemaStore definition for AnyWork Automation Configuration, reporting rule violations and JSON pointer paths.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-anywork-automation-configu-6eccf802-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/validate-anywork-automation-configuration-336c3d05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7pNmk_FY0U3pgM4O4bf8O

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-anywork-automation-configuration-336c3d05 -d '<json body>'
```

Example prompt: Can you validate this AnyWork Automation Configuration JSON for me and tell me which fields are invalid or missing: {"version":"1.0","tasks":[{"id":"step1","action":"notify"}]}?

## When to prefer this

Use this endpoint when you need to validate a JSON document specifically against the AnyWork Automation Configuration schema using a pinned SchemaStore definition. Prefer this over generic JSON validators when you need AnyWork-specific rule checking with JSON pointer–level error reporting. Not suitable for YAML/TOML configs or for validating other automation platform schemas.

## Known failure modes

- Document exceeds 100 KB size limit — rejected without validation
- JSON is not parseable (malformed syntax) — parse error returned before schema validation
- Document nesting exceeds 32 levels — rejected
- YAML or TOML format submitted instead of JSON — not supported
- Schema definition unavailable or pinned version mismatch — validation may fail unexpectedly

## How this service works

Validate AnyWork Automation Configuration: Validate a JSON document for AnyWork Automation Configuration. 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 is compliant with the AnyWork Automation Configuration schema, including JSON pointer paths to any violations and descriptions of each rule that was broken.

## 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-anywork-automation-configuration-336c3d05/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)