# Operation 402 JSON Cleaner

> Operation 402 JSON Cleaner is a paid API for AI agents from operation-402-live.aeroworks.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-21).

Cleans and normalizes arbitrary JSON data, removing noise and standardizing structure for AI agent use

## Facts

- Endpoint: POST https://operation-402-live.aeroworks.workers.dev/api/json?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/operation-402-json-cleaner-3af55d58
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3QwRjVentXngGvlW7A9zC

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 operation-402-json-cleaner-3af55d58 -d '<json body>'
```

Example prompt: Can you clean up this messy JSON for me? Here it is: {"name":" Alice ","age":null,"tags":["a",,"b"],"extra":undefined} — just give me back a normalized, clean version.

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-use JSON cleaning and normalization step in an AI agent pipeline, especially when you want USDC micropayment billing on Base mainnet via x402 rather than a subscription. Best for ad-hoc or low-volume cleanup tasks where spinning up a dedicated parser is overkill.

## Known failure modes

- Completely unparseable input may return an error or empty result
- Deeply nested or very large JSON payloads may exceed processing limits
- Payment failure (x402) will block the call before processing begins
- Missing or empty 'data' field in request body may return a default or error response

## How this service works

Five paid data-processing APIs for AI agents. Payments use x402 v2 with USDC on Base mainnet.

## Output

A JSON object containing a 'result' field with the cleaned and normalized version of the input data, and a 'service' field confirming 'JSON Cleaner' was used. The result reflects a sanitized, structurally consistent form of the original input.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {}
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {},
  "service": "JSON Cleaner"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/operation-402-json-cleaner-3af55d58/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from operation-402-live.aeroworks.workers.dev](https://www.zero.xyz/host/operation-402-live.aeroworks.workers.dev/llms.txt)