# kosoyy tools — JSON Validator (x402 micro-API)

> kosoyy tools — JSON Validator (x402 micro-API) is a paid API for AI agents from alert-woodpecker-2022.kosoyyagent.deno.net, paid per call via x402, $0.002/call, status down (last checked 2026-11-22).

Validates JSON text or objects against an optional JSON schema subset, returning a structured validation result for $0.002 USDC per call.

## Facts

- Endpoint: POST https://alert-woodpecker-2022.kosoyyagent.deno.net/api/json-check?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: down
- Last checked: 2026-11-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kosoyy-tools-json-validator-x402-micro-api-44fcfb60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i2lwwGh4ShldEchmLTVwE

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 kosoyy-tools-json-validator-x402-micro-api-44fcfb60 -d '<json body>'
```

Example prompt: Can you check if this JSON string is valid and matches my schema — it needs to have a required 'name' field of type string with maxLength 100 and an 'age' of type number: '{"name":"Alice","age":30}'?

## When to prefer this

Choose this endpoint when you need a lightweight, deterministic, pay-per-call JSON validation tool without a subscription — especially in agentic pipelines where validation is an occasional step and cost per call must be minimal. Prefer over free validators when operating in an x402-compatible payment context (Solana or Base USDC) and you need schema-aware validation of required fields, types, and maxLength constraints in a single API call.

## Known failure modes

- Unpaid request returns HTTP 402 with a payment offer (x402 protocol) — agent must pay 0.002 USDC on Solana or Base to proceed
- Invalid or missing 'data' field in request body returns an error result
- Malformed JSON schema subset provided in 'schema' field may cause unexpected validation behavior
- Network unavailability on Deno Deploy may cause timeouts
- Very large JSON strings may be rejected or time out

## How this service works

Deterministic utility tools, paid per call in USDC (Solana or Base). Unpaid requests return a 402 offer.

## Output

Returns a JSON object with an 'ok' boolean indicating validation success or failure, a 'route' string identifying the endpoint used, and a 'result' object containing detailed validation output including any schema violations or parse errors.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "data"
 ],
 "properties": {
  "data": {
   "type": "string",
   "description": "JSON text or object to validate"
  },
  "schema": {
   "type": "object",
   "description": "optional JSON-schema subset (required, properties, type, maxLength)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ok": {
   "type": "boolean"
  },
  "route": {
   "type": "string"
  },
  "result": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kosoyy-tools-json-validator-x402-micro-api-44fcfb60/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from alert-woodpecker-2022.kosoyyagent.deno.net](https://www.zero.xyz/host/alert-woodpecker-2022.kosoyyagent.deno.net/llms.txt)
