# Validate All Contributors Configuration File

> Validate All Contributors Configuration File 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 All Contributors configuration file schema using a pinned SchemaStore definition, reporting any rule violations and JSON pointer paths.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-all-contributors-configura-b13b23b9-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-all-contributors-configuration-file-a68b7559
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_a1hNjVNPNXTPHWdr0HYpK

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-all-contributors-configuration-file-a68b7559 -d '<json body>'
```

Example prompt: Can you validate this JSON for me — it's my .all-contributorsrc config file and I want to make sure it's valid before I commit it to the repo?

## When to prefer this

Choose this endpoint when you specifically need to validate a JSON document against the All Contributors (.all-contributorsrc) configuration schema. It uses a pinned SchemaStore definition for deterministic, reproducible results. Prefer this over generic JSON validators when you need All Contributors-specific schema rules and JSON pointer error reporting rather than just syntactic JSON checking.

## Known failure modes

- Document exceeds 100 KB limit — rejected without validation
- JSON nesting exceeds 32 levels — rejected
- Malformed JSON submitted (not parseable) — parse error returned
- Network timeout or service unavailability — HTTP 5xx error
- Payment not processed — HTTP 402 returned

## How this service works

Validate All Contributors configuration file: Validate a JSON document for All Contributors configuration file. 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 indicating whether the submitted JSON document conforms to the All Contributors configuration file schema. On failure, includes JSON pointer paths to each violation and a description of the rule that was broken. On success, confirms the document is valid. Maximum document size is 100 KB.

## 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-all-contributors-configuration-file-a68b7559/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)