# NetIntel JSON Normalizer

> NetIntel JSON Normalizer is a paid API for AI agents from netintel-production-440c.up.railway.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Normalizes and validates a JSON payload against a schema, returning a quality grade, score, null field counts, and a normalized output object

## Facts

- Endpoint: POST https://netintel-production-440c.up.railway.app/normalize/json
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/netintel-json-normalizer-0a2fe76c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aUtzLZpabcuX8s4bqnWYK

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 netintel-json-normalizer-0a2fe76c -d '<json body>'
```

Example prompt: Can you normalize and grade this user record JSON — it has fields like age, tags, full_name, is_active, and signup_date — against our schema and tell me the quality score, how many fields were populated, and whether it fully matches the schema?

## When to prefer this

Choose this endpoint when you need to validate, clean, and score a JSON object against a defined schema in a single call, especially when you want a structured quality grade (A–F) and field-level diagnostics rather than a simple pass/fail. It is particularly useful for data pipeline quality checks or user record normalization where you want both cleaned output and a completeness report.

## Known failure modes

- Invalid or malformed JSON input returns a 400 error
- Schema mismatch with no recoverable fields may return a low grade with schema_match: false
- Missing required schema definition may result in an error or ungraded response
- Payment not received or x402 micropayment failure results in a 402 Payment Required response
- Oversized payload may be rejected or time out

## How this service works

Conform messy or inconsistent JSON to a target schema using Claude Haiku — renames keys, coerces types (string→number, "true"→boolean, etc.), and fills missing fields with null, returning JSON that matches the exact shape the caller specified so agents can normalize data from varied sources into one consistent structure.

## Output

Returns a letter grade (e.g. 'A'), numeric score (0–100), normalized JSON object with cleaned field values, a schema_match boolean, counts of fields in schema and populated, count of nulled fields, a list of findings or issues, and a cached flag indicating whether the result was served from cache.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "data",
      "schema"
     ],
     "properties": {
      "data": {
       "type": [
        "string",
        "object"
       ],
       "description": "The messy JSON to normalize — a JSON string or an already-parsed object. Max 10000 words or 50KB."
      },
      "schema": {
       "type": "object",
       "description": "A map of field name → type token. Supported tokens: string, number, boolean, date, string[], number[], object. Max 50 fields. Output keys are forced to exactly these field names."
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "grade": {
       "type": "string",
       "description": "Letter grade A-F."
      },
      "score": {
       "type": "number",
       "description": "Quality score 0-100."
      },
      "cached": {
       "type": "boolean",
       "description": "True if served from the in-memory cache."
      },
      "findings": {
       "type": "array",
       "items": {
        "type": "string"
       },
       "description": "Informational findings (e.g. schema_mismatch_corrected, mostly_nulled)."
      },
      "normalized": {
       "type": "object",
       "description": "The input conformed to the target schema: keys are exactly the schema field names, values coerced to the declared types, missing fields null."
      },
      "schema_match": {
       "type": "boolean",
       "description": "True when the model's output keys were exactly the schema field names. False when code had to force-conform (strip extra / add missing) keys."
      },
      "fields_nulled": {
       "type": "number",
       "description": "Number of null fields in the output."
      },
      "fields_in_schema": {
       "type": "number",
       "description": "Numb
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "grade": "A",
  "score": 100,
  "cached": false,
  "findings": [],
  "normalized": {
   "age": 42,
   "tags": [
    "vip",
    "beta"
   ],
   "full_name": "Jane Doe",
   "is_active": true,
   "signup_date": "2024-03-01"
  },
  "schema_match": true,
  "fields_nulled": 0,
  "fields_in_schema": 5,
  "fields_populated": 5
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/netintel-json-normalizer-0a2fe76c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from netintel-production-440c.up.railway.app](https://www.zero.xyz/host/netintel-production-440c.up.railway.app/llms.txt)