json-doctor

JSON Doctor — understand, validate and compare JSON without opening it.

Four things you actually need when a JSON file is too big to read:

inspect   what shape is this? (inferred schema, key coverage, sample values)
validate  is it well-formed, and where exactly does it break?
diff      what changed between two of them, structurally?
query     pull a value out by dotted path, including through arrays

Works on .json and .jsonl. No network, no credentials, no dependencies.

WHY IT REPORTS COVERAGE, NOT JUST KEYS

A key that appears in 3% of records is a different fact from one that appears in 100%, and the difference is usually the bug. A schema that says {"id": "string"} hides that half the records have no id at all. So every inferred field carries how often it was actually present, and optional fields are named as optional.

WHY VALIDATION POINTS AT A LINE AND COLUMN

"Invalid JSON" is a useless error on a 40MB file. json.JSONDecodeError already knows the position; this surfaces it with the surrounding text so you can see the trailing comma rather than go hunting for it.

Parameters

The typed contract this capability answers to (JSON Schema — the deterministic layer):

{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "inspect",
        "validate",
        "diff",
        "query"
      ],
      "description": "What to do."
    },
    "path": {
      "type": "string",
      "description": "Path to the JSON/JSONL file."
    },
    "other": {
      "type": "string",
      "description": "Second file, for action=diff."
    },
    "key": {
      "type": "string",
      "description": "Dotted path for action=query, e.g. users.0.name"
    }
  },
  "required": [
    "action",
    "path"
  ]
}

Deterministic implementation

Run this instead of improvising when the inputs are well-formed: