Getting started with Rawtell, answers to common questions, and known limitations of the forensic JSON debugging tool. If you are here because a parse error brought you — the tool itself is at /app →
Navigate to the App page, select the Inspect URL tab, paste a full
URL (including https://) into the input field, and click Inspect.
Rawtell fetche the URL and returns:
application/json header with an HTML body)Select the Parse text tab, paste your JSON blob into the text area, and click Parse. The entire parse happens in your browser — the text is never sent to any server. Rawtell highlights the exact location of any parse error and explains what was expected there in plain English.
JSON.parse in most browsers) are strict. Rawtell uses a strict parser and
will reject:
'value' instead of "value")content-type: application/json with a 200 OK status and an
HTML error page is a common misconfiguration. Rawtell flags the mismatch:
{ or [)content-type header claims127.0.0.1,
localhost, ::1), private IP ranges (10.x.x.x,
172.16-31.x.x, 192.168.x.x), and URLs containing embedded
credentials (https://user:pass@host/). This is a security measure — the
server-side fetcher should not access internal networks on your behalf. Use the
Parse text tab with a saved copy of the response body instead.
Because Rawtell runs on Cloudflare Workers, any target that is itself behind Cloudflare reports as unreachable. This is a platform restriction that cannot be worked around from within the Worker runtime. The limitation is noted next to the URL input on the App page.
Rawtell is a stateless, single-use tool. Each inspection is independent. There are no user accounts, no login, no saved-history feature, and no dashboard. Pro and Team plans (with planned saved history and API access) are described on the pricing page but are not yet available — no payment processor is connected yet.
Rawtell does not send email, alerts, reminders, or any form of notification. There is no email sender in this fleet. Any page or feature description implying email delivery (such as "email alerts on schedule changes" on the Pro plan) is a description of a planned capability, not an available feature.
The Pro ($8/month) and Team ($24/month) plan prices are stated as intended pricing.
No payment infrastructure is operational. The checkout form on the pricing page is a
demonstration only. See needs.md in the repository for what the owner needs
to do to connect Stripe.
The service has no registered company, registered address, or governing jurisdiction. The privacy policy and terms of service are published as statements of operational intent and are not yet legally binding contracts. This will be resolved when the owner registers the business.
There is a built-in feedback channel on the App page — scroll to the bottom of the page. Submissions go into a database that someone reviews.
In-app feedback form — scroll to the bottom of /app. Select the type (bug report, feature request, general), write your message, and optionally leave a contact handle. This is the only working channel.
Email, ticket system, Discord, X: none of these exist yet. There is no mailbox on any domain associated with this service. If you provide a contact handle in the feedback form, you may hear back — but the operator has no obligation or guaranteed response time, and no automated reply system exists.
For abuse reports or legal concerns: Because no legal entity is registered and no mailbox exists, there is currently no formal channel for legal correspondence. These are honest operational facts about this service, not evasions.