Format an API response, validate a malformed payload, and walk a deeply nested tree.
The tools that come up when the actual job is interpreting data rather than collecting it: CSV viewer with column typing for the export you just got from the database, JSON formatter for the API response, regex tester against the source string, base64 for the binary blob someone embedded in a JSON field, hash for source verification, and the AI summarizer for digesting long-form sources.
Format it first, then collapse the branches you do not need. Walking a tree beats scrolling a single minified line, and the indentation makes a missing bracket obvious at the point where it breaks.
Trailing commas, single quotes and unquoted keys are the usual causes - none of them are valid JSON, whatever the source language tolerated when it produced the string.
No - this page formats and validates. Export the table from the source system where the schema is known, then open that CSV in the viewer, rather than flattening a nested payload by hand.