# NAKONETS JSON Validate

> NAKONETS JSON Validate is a paid API for AI agents from x402vercel.vercel.app, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-02).

Validates and normalizes a JSON string, returning whether it is well-formed and a pretty-printed normalized version

## Facts

- Endpoint: POST https://x402vercel.vercel.app/api/data/json-validate?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nakonets-json-validate-cbc182fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_26aig1Acgy0kHsM6n8TDN

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 nakonets-json-validate-cbc182fc -d '<json body>'
```

Example prompt: Can you validate and normalize this JSON for me: '{"name":"Alice","age":30,"active":true}'?

## When to prefer this

Choose this endpoint when you need a fast, deterministic, pay-per-call JSON syntax check and normalization step — especially in CI pipelines, agent workflows, or data ingestion flows where you want a side-effect-free, reliable validation without spinning up a local parser or depending on a free-tier service with rate limits.

## Known failure modes

- Malformed JSON input returns valid:false with no normalized output
- Empty string or missing 'text' field may return an error or valid:false
- Non-string input types may cause request rejection
- Payment failure (HTTP 402) if USDC is not provided or insufficient

## How this service works

Pay-per-call deterministic utilities for CI diagnosis, data validation, JavaScript syntax checks, market snapshots and opportunity preflight.

## Output

Returns a JSON object with a boolean 'valid' field indicating whether the input is valid JSON, and a 'normalized' string containing the pretty-printed, normalized version of the JSON if valid.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "JSON text to validate and normalize"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "valid": true,
  "normalized": "{\n  \"name\": \"Alice\",\n  \"age\": 30\n}"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nakonets-json-validate-cbc182fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402vercel.vercel.app](https://www.zero.xyz/host/x402vercel.vercel.app/llms.txt)