Help Centre
Last updated: September 12, 2026
Getting started
Parsehint is a JSON parse diagnostic tool. It tells you exactly where a JSON blob is broken and what the parser expected there — in plain language, not byte offsets. For URLs it also shows what the server actually sent.
Paste JSON
Open the tool, switch to the Paste JSON tab, paste your JSON blob, and click Check JSON. The parsing happens entirely in your browser — the text you paste never leaves your machine. The result shows the line, column, and a human-readable explanation of what went wrong.
Check a URL
Switch to the URL tab, enter the full URL (including
https://), and click Fetch & Check. Parsehint
fetches exactly that URL — no crawling, no following redirects — and reports the
status code, content-type, whether the body is JSON, and the parse verdict.
Copy the result
One click copies the full diagnostic — verdict, line/column details, and server metadata — so you can paste it into a ticket, a PR, or a message without retyping.
Frequently asked questions
Does Parsehint store the JSON I paste?
No. Pasted JSON is parsed in your browser with JSON.parse() and
never leaves your machine. There is no server-side storage, no database, and no
logging of pasted content. The page states this next to the paste area. Only
URL-mode requests reach the server, and only the URL you typed is included in
that request — the response body is inspected once and then discarded.
My URL returns a 200 but Parsehint says it's not JSON. What happened?
This is the most common scenario Parsehint was built to diagnose. Many servers
return an HTML error page or a plain-text message with a 200 status and a
Content-Type: application/json header. Nothing in your fetch client
makes that visible — only reading the actual bytes does. Parsehint checks whether
the body actually parses as JSON, and if it doesn't, it says so and shows you
the content-type the server claimed as well as the one that matches the body.
Parsehint can't reach my URL. Why?
Several reasons: (1) If the host is behind Cloudflare, the Cloudflare Worker platform refuses a socket back into its own network — paste the response body directly instead. (2) If the URL returns a non-2xx status, Parsehint reports the status and marks every derived verdict as "not established". (3) The URL validation rejects loopback addresses (127.0.0.1, localhost), private IP ranges, embedded credentials (user:pass), and control characters by design. (4) URL fetches time out after 15 seconds.
What do the error messages mean? I see "Line X, Column Y"
Standard JSON.parse error messages give you a byte position — for
example "unexpected token at position 4471". Parsehint translates that position
into the line and column in your original document (1-indexed, like an editor)
and writes a plain-language explanation of what was expected there. For example:
"Line 3, column 17 — expected a comma after property name." The raw error is
also shown for reference.
What is the Pro plan and how do I subscribe?
Pro ($12/month or $120/year) adds saved parse history (local), CSV/JSON export of results, batch URL checking, and custom error-message rules. Caveat: no payment processor is connected yet — the checkout page on the Pricing page is a demonstration form. Real subscriptions are not available until the operator connects a payment gateway. For billing inquiries, email parsehint@agen2ic.ai.
Can I use Parsehint to check internal / private APIs?
URL mode deliberately rejects loopback addresses, private IP ranges, and embedded credentials for security — these are blocked by URL validation before any fetch is attempted. For a private API, paste a sample of the response body directly into Paste mode instead. The tool cannot reach servers on your local network or behind a VPN.
Known limitations
Parsehint is a diagnostic tool with a deliberately narrow scope. The following are honest gaps — features that are mocked, not yet built, or blocked by the infrastructure this fleet provides.
- Email sender There is no email sender in this infrastructure. No alerts, no digests, no scheduled re-checks, no "we'll email you" notifications. If a parse result matters tomorrow, copy it today.
- Payment processor The Pro subscription flow on the Pricing page is a demonstration form only. No real payments are taken, no subscriptions are created, and no payment processor is connected. The operator must connect Stripe before real purchases work.
- Accounts & login There are no user accounts on the free tier. The Pro tier would require server-side accounts, which are not built yet. There is no login, no registration, no session persistence.
- Storage Parsehint stores nothing server-side. Pasted text stays in your browser. URL results are returned and forgotten. Pro's "saved history" and "export" features are client-side only (browser storage).
- Cloudflare block A host behind Cloudflare cannot be reached from a Cloudflare Worker. If a URL appears unreachable, paste the response body directly instead.
- Legal entity No legal entity has been registered yet. The operator must supply the entity name, address and jurisdiction. Until then, the service is provided as-is with no formal contract.
- Crawling Parsehint fetches exactly one URL — the one you type. It never follows redirects, never crawls, and never retries a different endpoint.
Contact us
For help, questions, bug reports, or billing inquiries, email
parsehint@agen2ic.ai.
All email sent to @agen2ic.ai reaches a human and is routed
by the local part — parsehint identifies this product.
Before you email, check the tool itself — most questions are answered by trying it. The FAQs above cover the common issues. If you are reporting a bug, please include the JSON or URL you were using (if safe to share) and what result you expected.
Response time: not guaranteed — this is a small team. We aim to reply within 2 business days.