# netintel.dev JSON Normalizer

> netintel.dev JSON Normalizer is a paid API for AI agents from netintel.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Normalizes a JSON object against a schema, scores data quality, and returns cleaned/typed fields with a grade and match report

## Facts

- Endpoint: POST https://netintel.dev/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-dev-json-normalizer-8b9849f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nOBLayFOFSEk_mkDiZa4x

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-dev-json-normalizer-8b9849f5 -d '<json body>'
```

Example prompt: Can you normalize and quality-check this JSON record against my schema — it has fields like age, tags, full_name, is_active, and signup_date — and tell me the grade, score, which fields are populated, and whether it matches the schema?

## When to prefer this

Use this endpoint when you need to both normalize JSON field types/values AND get a structured quality assessment with a letter grade and score in a single call. Prefer it over manual validation when you want human-readable findings, a completeness score, and cleaned output in one response. Especially useful for pipelines ingesting variable user-submitted data that must conform to a known schema.

## Known failure modes

- Malformed or unparseable JSON input returns an error
- Schema mismatch with no recoverable fields results in low score and findings
- Missing required fields causes fields_nulled count to increase and grade to drop
- Invalid schema definition may return a 400-level error
- Payment failure via x402 blocks the call before processing

## 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 grade (e.g. 'A'), numeric quality score (0-100), normalized field values with corrected types, a schema_match boolean, counts of fields in schema vs populated vs nulled, a cached flag, and a findings array listing any data quality issues detected.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "type": "string",
     "enum": [
      "json",
      "form-data",
      "text"
     ]
    },
    "body": {
     "type": "object",
     "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."
      }
     },
     "required": [
      "data",
      "schema"
     ]
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "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."
      },
      "fields_in_schema": {
       "type": "number",
       "description": "Number of fields in the target schema."
      },
      "fields_populated": {
       "type": "number",
       "description": "Number of non-null fields in the output."
      },
      "fields_nulled": {
       "type": "number",
       "description": "Number of null fields in the output."
      },
      "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."
      },
      "cached": {
       "type": "boolean",
       "description": "True if served from the in-memory cache."
      },
      "score": {
       "type": "number",
       "description": "Quality score 0-100."
      },
      "grade": {
       "type": "string",
       "description": "Letter grade A-F."
      },
      "findings": {
       "type": "array",
       "items": {
        "type": "string"
      
… (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-dev-json-normalizer-8b9849f5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from netintel.dev](https://www.zero.xyz/host/netintel.dev/llms.txt)