Help Centre
Getting started, common questions, and known limitations — everything you need to use Parseproof effectively.
Getting started
Parseproof has two modes. There is no account, no signup, and no data collection.
- Open the tool at /app.
- Choose a mode: click the “Paste JSON” tab to validate text you already have, or “Fetch URL” to inspect a live API response.
- Paste mode: drop your JSON into the text area and press Ctrl+Enter (or click the button). Parsing happens in your browser — nothing is sent to any server.
- Fetch mode: enter a URL and click the button. The tool fetches the URL server-side and returns the HTTP status, response headers, and full body. The URL is not stored or logged.
-
Read the output: if the JSON is valid, you see it pretty-printed. If it is not, Parseproof marks the exact line and column with a caret (
^) and explains what went wrong in plain language.
Frequently asked questions
Real questions from developers using Parseproof.
Parseproof translates that opaque byte offset into a line and column number, draws a caret (^) diagram pointing at the exact problem character, and explains what was expected there in plain language. For example, instead of “unexpected token at position 42” you might see:
Line 3, column 14
{"name": "Alice",, "age": 30}
^
Expected a property name (string), but found a comma.
A surprisingly common problem: many servers return an HTML error page (a 404, 503, or 500 with human-readable HTML) but send a 200 OK status and label it Content-Type: application/json. Parseproof shows you the actual response headers including the real Content-Type, so you can see the mismatch. If the body starts with <!DOCTYPE html> but the Content-Type says JSON, Parseproof flags that discrepancy.
No. Parseproof fetches URLs through a Cloudflare Worker, and Cloudflare blocks Worker-to-Worker requests. If the target API is behind Cloudflare, you will see a “This host is behind Cloudflare and cannot be reached from this tool” message rather than a misleading connection error. In this case, try pasting the raw JSON response body directly instead of fetching via URL.
No. When you paste JSON text, parsing happens entirely in your browser using JavaScript’s built-in JSON.parse(). Your content never leaves your machine. URL fetches are proxied through the Parseproof Worker, but the URL and response are not stored, logged, or written to any persistent storage. See the Privacy Policy for full details.
If the server responds with a status outside the 200-299 range (e.g. 301, 400, 403, 500), Parseproof reports the actual status code and marks every derived verdict as not established. It will not attempt to parse an error page as valid JSON or report false positives about your JSON structure. Check the status code and response body — the problem is likely at the server, not in your JSON.
Parseproof checks JSON syntax only. It does not validate schema (whether the right fields are present with the right types), check authentication headers, test business logic, or verify that your request matches the API’s contract. If the JSON parses correctly, the issue is elsewhere in your integration — check endpoint paths, HTTP method, authentication, and the expected request format in the API documentation.
Known limitations
These are honest descriptions of what Parseproof does not yet do, or cannot do because of the infrastructure it runs on.
- Cloudflare-hosted targets: Any URL behind Cloudflare cannot be fetched through the Parseproof Worker. This is a Cloudflare platform restriction, not a bug.
- No email or notifications: Parseproof cannot send alerts, digests, reminders, or scheduled re-checks. There is no email sender connected to this fleet, and we do not promise one.
- No accounts or history: Parseproof has no user accounts, no session storage, and no way to save or revisit past diagnostics. Each session is ephemeral.
- No schema validation: Parseproof validates JSON syntax only. It cannot check that the JSON matches a specific schema, has the right data types, or contains required fields.
- No batch URL checking: You can only fetch one URL at a time. Batch processing is planned for a future Pro tier but is not available yet.
- Pro plan not yet purchasable: The Pro plan is announced on the pricing page as coming soon, but no payment processor is connected. Subscriptions cannot be purchased today.
- No legal entity registered: The operator has not registered a company or established a jurisdiction. This does not affect the tool’s functionality but means there is no legal address or governing law on record.
Contact us
Support is not yet reachable by email or phone. The operator of Parseproof has not registered a company, established a contact address, or connected a mailbox to this domain.