Errors you can actually find
Browsers report broken JSON in different words, and some give no position at all. This validator reads the text itself, so it always says where it stopped and why: "Expected a comma (,) or } but found "b"" at line 2, column 3, with the line shown and a marker under the problem.
Readable, or small
Format with two spaces, four spaces or tabs; minify for transport; sort keys for stable output. The tree view folds objects and arrays so a large response can be explored a level at a time.
Related: decode a token with the JWT decoder, or compare two JSON files with text compare (format both with sorted keys first).