That JSON parse error is hiding something.
Here is what came back on the wire.
Jsonlook fetches and inspects the actual server response — content-type, status, body — so you can tell whether the bug is in your code or theirs. Paste a URL or a blob of JSON and get a plain-language verdict, not "unexpected token at position 4471".
Two modes, one purpose
Parse JSON locally
Paste any JSON text and get instant validation. On failure, Jsonlook points at the exact line and column and tells you what was expected — never transmitted, parsed entirely in your browser.
Inspect a server response
Enter a URL. Jsonlook fetches it once, reports the status code, the actual Content-Type header, and whether the body is JSON. A surprising share of broken APIs are HTML error pages dressed with a JSON Content-Type and a 200 status.
How it works
Paste a JSON blob into the editor, or type a URL into the inspector. No account needed, nothing saved. The tool exists only when you use it.
Pastet text is parsed in your browser — zero network. A URL is fetched exactly once by the server; no following redirects, no crawling, no retries.
See the status, content-type, body preview, and a plain-language verdict. If the JSON is invalid, the exact position is marked. The verdict is matter-of-fact, not declarative — it lays the evidence out and lets you decide.
No email. Jsonlook has no email sender, no alerts, no digests, no scheduled re-checks. Every inspection is one-shot, synchronous, and stateless.