Api Endpoint

NetIntel

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.

Open interactive test console

Offering

Provider
netintel.dev
Method
POST
Offering type
Api Endpoint
Transport type
http
Category
Data
Delivery
Not provided
Pricing model
Not provided
x402 version
2

Endpoint context

URL
https://netintel.dev/normalize/json
MIME type
Not provided
First seen
2026-10-16T01:50:14.534Z
Last seen
Tags
json normalization, data cleaning, schema mapping, text to json, LLM

Payment pricing

x402 payment terms are the authoritative price for calling this endpoint.

Payment option 1
0.05 USDC
Atomic price: 50000 · Network: eip155:8453 · Asset: USDC · Scheme: exact
Payment option 2
0.05 USDC
Atomic price: 50000 · Network: solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp · Asset: USDC · Scheme: exact
Raw x402 terms
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "50000",
    "payTo": "0xdaDc335482AD545296Fd7b28518A251fFCbEb9Df"
  },
  {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "50000",
    "payTo": "8FVeybWnB4dYrxTuPK7WzFZNAiEcFVaDLFnKpRwVGr5s"
  }
]

Observed health

Status
Healthy
Latest latency
104 ms
Average latency
220 ms
HTTP status
204
Last checked
Reachability
100% over 13 checks

Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.

Input schema

{
  "additionalProperties": false,
  "properties": {
    "body": {
      "properties": {
        "data": {
          "description": "The messy JSON to normalize — a JSON string or an already-parsed object. Max 10000 words or 50KB.",
          "type": [
            "string",
            "object"
          ]
        },
        "schema": {
          "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": "object"
        }
      },
      "required": [
        "data",
        "schema"
      ],
      "type": "object"
    },
    "bodyType": {
      "enum": [
        "json",
        "form-data",
        "text"
      ],
      "type": "string"
    },
    "method": {
      "enum": [
        "POST"
      ],
      "type": "string"
    },
    "type": {
      "const": "http",
      "type": "string"
    }
  },
  "required": [
    "type",
    "method",
    "bodyType",
    "body"
  ],
  "type": "object"
}

Output schema

{
  "properties": {
    "example": {
      "properties": {
        "cached": {
          "description": "True if served from the in-memory cache.",
          "type": "boolean"
        },
        "fields_in_schema": {
          "description": "Number of fields in the target schema.",
          "type": "number"
        },
        "fields_nulled": {
          "description": "Number of null fields in the output.",
          "type": "number"
        },
        "fields_populated": {
          "description": "Number of non-null fields in the output.",
          "type": "number"
        },
        "findings": {
          "description": "Informational findings (e.g. schema_mismatch_corrected, mostly_nulled).",
          "items": {
            "type": "string"
          },
          "type": "array"
        },
        "grade": {
          "description": "Letter grade A-F.",
          "type": "string"
        },
        "normalized": {
          "description": "The input conformed to the target schema: keys are exactly the schema field names, values coerced to the declared types, missing fields null.",
          "type": "object"
        },
        "schema_match": {
          "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.",
          "type": "boolean"
        },
        "score": {
          "description": "Quality score 0-100.",
          "type": "number"
        }
      },
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}