# KEVAREMESH JSON Validation

> KEVAREMESH JSON Validation is a paid API for AI agents from kevaremesh-web.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-03).

Validates, parses, and pretty-prints a JSON string, returning whether it is valid JSON along with normalized and formatted representations.

## Facts

- Endpoint: POST https://kevaremesh-web.vercel.app/api/x402/json-validation-cdp-json-validation?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kevaremesh-json-validation-0d313514
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M28gfJBIO089Q0Gyopig_

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 kevaremesh-json-validation-0d313514 -d '<json body>'
```

Example prompt: Can you check if this string is valid JSON and give me a pretty-printed version of it: '{"name":"Alice","age":30,"active":true}'?

## When to prefer this

Choose this endpoint when you need a fast, cheap ($0.001 USDC), programmatic JSON validation step inside an AI agent pipeline — especially when the JSON comes from untrusted sources like LLM outputs, user inputs, or external APIs. It is ideal when you want both validity checking and a normalized or human-readable form in a single call, without spinning up a local parser. Prefer it over generic code execution for lightweight, stateless JSON checks.

## Known failure modes

- Input exceeds 256 KiB limit — service will reject with a limitation error
- Input is not a string (e.g. already-parsed object passed instead of text) — may return unexpected behavior
- Completely empty input — may return invalid=true with a parse error
- Malformed UTF-8 or binary data — parsing error returned in the error field
- Payment failure via x402 protocol — request rejected before processing

## How this service works

Buyer-first MCP procurement gateway that discovers, compares and routes live x402 APIs without making the buyer choose a provider.

## Output

Returns an object containing: a boolean indicating whether the input is valid JSON, an error string if parsing failed (null if valid), a pretty-printed version of the JSON with indentation, and a compact normalized JSON string. Also includes service metadata such as product name, tool name, and a timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "maxLength": 262144
  },
  "pretty": {
   "type": "boolean",
   "default": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "type": "object",
   "error": null,
   "valid": true,
   "pretty_json": "{\n  \"a\": 1\n}",
   "normalized_json": "{\"a\":1}"
  },
  "product": "kevaremesh_json_validation_cdp_json_validation_v2",
  "service": "KEVAREMESH",
  "tool_name": "kevaremesh_json_validate",
  "limitations": [
   "Maximum input 256 KiB"
  ],
  "generated_at": "2026-09-18T00:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kevaremesh-json-validation-0d313514/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kevaremesh-web.vercel.app](https://www.zero.xyz/host/kevaremesh-web.vercel.app/llms.txt)