# Validate httpmockrc

> Validate httpmockrc 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 httpmockrc schema definition from SchemaStore, reporting JSON pointer violations and rule errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-httpmockrc-a7daa1e0-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-httpmockrc-910404f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T7VhTTGnftnZexFhc3Z_l

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-httpmockrc-910404f3 -d '<json body>'
```

Example prompt: Can you check if my httpmockrc config is valid? Here's the JSON: {"routes": [{"path": "/api/test", "method": "GET", "response": {"status": 200}}]}

## When to prefer this

Choose this endpoint when you specifically need to validate a JSON document against the httpmockrc schema using a pinned SchemaStore definition. It is purpose-built for httpmockrc configuration files and reports precise JSON pointer locations for each violation, making it ideal for CI pipelines, pre-commit hooks, or debugging httpmockrc configs. Prefer it over generic JSON Schema validators when you want SchemaStore's authoritative httpmockrc rules without managing schema downloads yourself.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing refused
- Malformed JSON submitted (not parseable) — error returned
- Schema unavailable or pinned definition mismatch — validation may fail unexpectedly
- Empty or missing document field — no validation performed

## How this service works

Validate httpmockrc: Validate a JSON document for httpmockrc. 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 httpmockrc schema, including any JSON pointer paths and specific rule violations found. If valid, confirms compliance; if invalid, lists each error location and the violated constraint.

## 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-httpmockrc-910404f3/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)