# UOS Genesis Machine – JSON Sort Keys

> UOS Genesis Machine – JSON Sort Keys 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-10-02).

Recursively sorts all keys of a JSON object into deterministic lexical order for canonical serialization, hashing, and comparison.

## Facts

- Endpoint: POST https://genesis.palsus2023.workers.dev/v1/json_sort_keys?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/uos-genesis-machine-json-sort-keys-fdd26251
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BLikqyY895taw6TQxRIKx

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-machine-json-sort-keys-fdd26251 -d '<json body>'
```

Example prompt: Sort all the keys in this JSON object recursively into alphabetical order so I get a stable, canonical payload I can hash or sign: {"z":1,"a":{"m":2,"b":3}}.

## When to prefer this

Choose this endpoint when you need a cheap, stateless, pay-per-call micropayment service to recursively sort JSON keys for canonical serialization, signature generation, hashing, caching, or deduplication — especially in autonomous agent pipelines that already use x402/Base USDC payment flows.

## Known failure modes

- Missing or malformed 'input' field returns an error response
- Non-JSON body type causes a parse failure
- Payment failure via x402 blocks the request before processing
- Deeply nested circular structures may cause processing errors
- Network timeout on the Cloudflare Worker edge node

## How this service works

Autonomous paid machine utilities using x402 and Base USDC.

## Output

Returns a JSON object with a 'result' field containing the input JSON with all keys (including nested ones) sorted into deterministic lexical order, plus 'service' set to 'json_sort_keys' and 'success' true.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {
      "input": {
       "type": "string",
       "description": "Sort JSON object keys recursively into deterministic lexical order. Useful for stable JSON serialization, canonical payloads, repeatable hashing, signatures, caching, comparison, deduplication, and agent preflight."
      }
     },
     "additionalProperties": true
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object"
  }
 },
 "additionalProperties": true
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "GENESIS* machine-readable service result",
  "service": "json_sort_keys",
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/uos-genesis-machine-json-sort-keys-fdd26251/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)