Review individual claims
Identify facts, quantities, units, dates, versions, and applicable populations.
Spark · English technical content review
Check the key facts in your AI draft before publishing.
Find applicable sources for technical articles, technology briefings, and product documentation. See the support scope and what still needs review.
The browser extension is in free public beta. Assisted review pilots accept enquiries; scope, pricing, and delivery dates are agreed separately.
Spark is moving to an English product experience. New development and assisted reviews focus on English technical content. Existing accounts, quotas, and privacy choices are unchanged by this interface update. Language transition details
Give each cited claim a reviewable basis
Find original sources
List public references and their support scope, preserving conflicts and evidence gaps.
Decide what comes next
Identify conditions to add, wording to revise, or issues for further human review.
Need your review findings organized into a deliverable?
An assisted pilot organizes original references, applicable conditions, suggested wording changes, and unresolved issues within an agreed scope. AI assistance and Spark results are identified separately. A named human review is included only when expressly agreed before the work starts. You review the original sources before citing.
- Describe the task and claim count
- Agree scope, pricing, and timing
- Provide authorized, non-confidential material
- Receive and check a claim-by-claim review record
The pilot covers English-language public technical facts, product documentation, and technology content. Medical, legal, investment advice and report certification are outside its scope. Missing sources are recorded; sufficient support for every claim cannot be guaranteed.
Three questions to ask when checking a claim
Does the source support this exact claim?
A source discussing the same topic may not support your quantity, relationship, or causal claim. Compare the specific claim with the original source.
Do the conditions match?
Check versions, dates, units, populations, and experimental conditions. Evidence for an older version or different conditions may not apply.
What remains unchecked?
Support for one claim does not cover an entire paragraph. Missing applicable support does not establish that a claim is false.
Open the original references and compare the claims
Public-source comparisons checked with AI assistance on 2026-10-04. These are illustrative examples, not customer cases or Spark verification runs, and have no independent human sign-off. They do not establish accuracy or time savings.
See a complete three-claim sample deliverable
Units: MB and MiB
Claim to check: 1 MiB = 1,048,576 bytes.
The NIST comparison table supports this MiB definition and lists MB as 1,000,000 bytes. Preserve the unit notation when citing; check product documentation when its notation differs.
NIST · Binary prefixesAPIs: HTTP errors and promises
Claim to check: fetch automatically rejects on HTTP 404.
The MDN guide explains that a 404 status alone does not reject the fetch promise. Check the response status; network failures, cancellation, and subsequent parsing errors require separate consideration.
MDN · Using the Fetch APIDescribe a task you need reviewed
Start with a task overview. Do not enter confidential text, sensitive personal information, passwords, or payment details. This page holds your draft temporarily; prepare an email, review it, and send it yourself.