# UOS Genesis normalize_json

> UOS Genesis normalize_json is a paid API for AI agents from genesis.palsus2023.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Normalizes a JSON payload into a canonical, consistently-structured format

## Facts

- Endpoint: POST https://genesis.palsus2023.workers.dev/v1/normalize_json
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/uos-genesis-normalize-json-cc8f4170
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LkeanthkJRFW8eoSybS7l

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 uos-genesis-normalize-json-cc8f4170 -d '<json body>'
```

Example prompt: Take this JSON blob and normalize it into a clean, canonical structure: {"Name":"Alice","AGE":30,"address":{"City":"Boston"}}

## When to prefer this

Choose this endpoint when you need to canonicalize JSON data from heterogeneous sources with inconsistent key casing, structure, or formatting before further processing, storage, or comparison. It is especially useful in data pipeline stages where consistency is required across multiple inputs. Prefer it over manual normalization or regex-based approaches for reliability and speed.

## Known failure modes

- Invalid or malformed JSON input returns an error response
- Empty payload may result in a 400 bad request
- Deeply nested or extremely large JSON may cause timeouts
- Non-JSON content type may be rejected
- Missing required fields in input body returns error

## How this service works

UOS Genesis machine utility: normalize_json

## Output

Returns a normalized JSON object with standardized key formatting, consistent structure, and canonical representation of the input data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "type": "string",
     "enum": [
      "json"
     ]
    },
    "body": {
     "type": "object"
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": true
  },
  "output": {
   "type": "object"
  }
 },
 "required": [
  "input"
 ],
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/uos-genesis-normalize-json-cc8f4170/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from genesis.palsus2023.workers.dev](https://www.zero.xyz/host/genesis.palsus2023.workers.dev/llms.txt)