Formatting is not the same as schema validation
The tool parses your input as JSON and displays it with two-space indentation. It accepts valid JSON values, including an object, array, string, number, boolean, or null. An invalid value produces a parser error rather than stale formatted output.
Syntax checking cannot tell whether an API expects a particular field or type. For example, {"count":1} is valid JSON, but an API may require count to be a string. Use a schema-aware validator when you need contract validation.
Common errors to fix
JSON property names and string values require double quotes. Trailing commas and JavaScript comments are not valid JSON. If parsing fails, read the reported error and inspect the nearby punctuation or quote marks.
The formatter changes whitespace, not the meaning of the parsed data. Still, review large numbers and duplicate property names: a standard parser may not preserve every textual detail exactly as entered.
Keep sensitive data out of shared examples
Formatting runs in your browser without uploading the pasted input to ToolVerse. If you copy the result into a bug report or chat, remove access tokens, passwords, and personal data first.