0saas

Job ticket 757758 · consumer · reading room · no subscription

Question eleven costs US$12 a month. The reading was always free.

Consensus caps Free at 10 Pro messages and 3 Deep reviews a month; unlimited asking starts at US$12 a month billed annually (US$144 up front — the monthly price was not printed in the captured view). This job ticket hands the reading to prompts you own: paste paper excerpts and the drawer files each as a strength-stamped catalog card with its quote; paste a claim beside an excerpt and the check stamps SUPPORTED, PARTIAL or UNSUPPORTED. The 200-million-paper index stays Consensus's.

Consensus is a trademark of its owner. This is an independent, unaffiliated comparison built on Consensus's own published pricing material, linked below and re-read every thirty days.

Paste the excerpts, press file the drawer, and the reading room answers with one card per paper — finding, study type, strength stamp, and the evidence line quoted verbatim. — rendered in this browser

Source: noneRendered: 0Uploaded to 0saas: nothing

Sample data is illustrative, not a claim about Consensus. Every Consensus figure on this page comes from the linked pricing page, read 2026-09-27.

The prompt pack

Two prompts, each mapped one-to-one onto a Consensus feature you are currently rationed on. Run them from this page with a free key, or copy them into any free chat model — the text is identical either way, and it is printed in full at the bottom of this section so it survives this site.

Loading the pack from tools.json… If this fails, the full prompt text is still readable below.

One-time unlocks only, never a subscription. If a price ever appears here it was read from Stripe in that request, not typed by hand. An unlock is client-side gating, not secure payment verification: it is stored in this browser and cannot prove payment to anyone else.

What Consensus's own pricing page says

Read from consensus.app/pricing/ on 2026-09-27. Fields we could not read are marked unconfirmed rather than filled in with a plausible number.

What Consensus meters — read from consensus.app/pricing on 2026-09-27 — vs this job ticket. — verified 2026-09-27
The jobConsensus FreeThis pageThis page + a free-tier model
Monthly allowance10 Pro messages · 3 Deep reviewsUnlimited pastes, free-tier modelsundefined
Findings with citationsMetered per messageCatalog cards with verbatim quotes, US$0undefined
Claim verificationInside Pro at US$12/mo (annual)Claim check with the decisive quoteundefined
Paper index of 200M+The actual productNot displaced — you paste the excerptsundefined

What this replaces, and what it does not

A displacement claim you cannot substantiate is a lie with good typography. This is the whole scope, including the parts where Consensus wins.

Findings filed per paper

One card each: finding, study type, strength stamp, verbatim quote

Claim-vs-excerpt verdicts

SUPPORTED / PARTIAL / UNSUPPORTED with the decisive line

A drawer you keep

Markdown downloads of every card, citable line by line

No paper search

The page reads what you paste; finding papers stays your job

No stored library

Each visit starts empty; your drawer lives in your files

No auto-synthesis across databases

Cross-paper synthesis beyond a pasted set is labelled missing scope

The prompts, in full, as text

Copy these into any model. They are the product; the page around them is convenience. Each block is the exact system prompt the interactive runner sends, plus the user-message template.

Prompt 01 — 1. File the evidence drawer · consensus-evidence-drawer v1.0.0 · best ally: OpenRouter — :free model variants · openai/gpt-oss-120b

Replaces: The Pro search reading: your pasted abstracts filed as catalog cards — one finding per card, each stamped for evidence strength, each quoting the line that supports it.

Why this model: Extracting one claim per abstract with a calibrated strength stamp and a verbatim quote is disciplined close reading repeated across several texts; a free long-context model keeps the calibration consistent across the drawer. Fallback ally: Google Gemini API — Free usage tier.

System prompt (1549 chars):

You run the reading room: the reader pastes excerpts from research papers (abstracts or sections) and names their question. You file one catalog card per paper — the finding most relevant to the question, a strength stamp, the supporting quote, and the study type as declared in the text. A card never asserts what its excerpt does not say.

Return ONLY one JSON object. No markdown fences, no commentary, no preamble.

{
  "kicker": string (max 8 words),
  "title": string (max 8 words),
  "subhead": string (max 20 words),
  "items": [
    { "title": string (the paper's lead author or title as given; body: the finding in one plain sentence, the study type (RCT / cohort / review / in-vitro / not stated), the strength stamp with a <= 10 word reason, then the supporting quote verbatim), "tag": string (one of CARD), "body": string }
  ],
  "notes": [ string (one short footnote per run-wide decision) ]
}

Hard rules:
1. Strength stamps: HIGH (randomized or replicated direct evidence), MID (observational or single study), LOW (in-vitro, animal, or hypothesis) — every stamp names its reason.
2. Effect sizes and numbers are quoted verbatim from the excerpt, never computed or rounded.
3. If the excerpt does not address the question, the card says NOT-RELEVANT instead of inventing a finding.
4. One card per pasted paper; nothing aggregated unless a SYNTHESIS item is explicitly requested.
5. Quotes include hedges as written (suggests, may) — strength is the reader's call, evidence is yours.
6. Write in the language of the pasted excerpts.

User message template:

File these excerpts against my question. My question: {{question}} Pasted excerpts (label each with its source): {{excerpts}}

Variables:

  • {{question}} — Your research question (max 200 chars) sample data shipped with the tool
  • {{excerpts}} — Pasted excerpts (max 6000 chars) sample data shipped with the tool

Output schema (the answer must match this exactly):

{ "type": "object", "required": [ "items" ], "properties": { "kicker": { "type": "string" }, "title": { "type": "string" }, "subhead": { "type": "string" }, "items": { "type": "array", "minItems": 1, "maxItems": 60 }, "notes": { "type": "array" } } }

Decoding: temperature 0.2 · max 2400 output tokens · responseMimeType application/json · budget ~1,400 in / ~1,000 out for three papers · cost per run: 1 request against the free OpenRouter daily pool; the relay floor needs no key at all.

Prompt 02 — 2. Claim-vs-excerpt check · consensus-claim-check v1.0.0 · best ally: Google Gemini API — Free usage tier · gemini-2.5-flash

Replaces: The discipline the meter rations: pasting one claim next to one excerpt and getting a stamped verdict — supported, partially, or unsupported — with the decisive quote.

Why this model: Comparing a specific claim against a specific excerpt is precise entailment reading with a quoted verdict; a free Flash model at low temperature stays literal where summarizers drift. Fallback ally: OpenRouter — :free model variants.

System prompt (1397 chars):

You are the reading room's fact checker: the reader pastes one claim and one research excerpt. You stamp the claim SUPPORTED, PARTIAL or UNSUPPORTED against exactly that excerpt, quote the decisive line, and name what would be needed to raise the stamp. You do not bring outside knowledge; the excerpt is the whole world.

Return ONLY one JSON object. No markdown fences, no commentary, no preamble.

{
  "kicker": string (max 8 words),
  "title": string (max 8 words),
  "subhead": string (max 20 words),
  "items": [
    { "title": string (VERDICT: the stamp and one plain sentence. QUOTE: the decisive excerpt line verbatim. MISSING: what the excerpt would need to contain to raise the stamp), "tag": string (one of VERDICT | QUOTE | MISSING), "body": string }
  ],
  "notes": [ string (one short footnote per run-wide decision) ]
}

Hard rules:
1. SUPPORTED requires the excerpt to state the claim's scope (population, dose, outcome) — narrowed scope demotes to PARTIAL.
2. Numbers in the claim must match the excerpt verbatim; a changed number is UNSUPPORTED even when the direction agrees.
3. QUOTE is copied character-for-character; no paraphrase passes as a quote.
4. MISSING names the missing evidence, not opinions.
5. If the excerpt never mentions the claim's topic, the verdict is UNSUPPORTED with an empty QUOTE cell marked 'topic absent'.
6. Write in the language of the pasted text.

User message template:

Check this claim against this excerpt. The claim: {{claim}} The excerpt: {{excerpt}}

Variables:

  • {{claim}} — The claim to check (max 300 chars) sample data shipped with the tool
  • {{excerpt}} — The excerpt (paste) (max 3000 chars) sample data shipped with the tool

Output schema (the answer must match this exactly):

{ "type": "object", "required": [ "items" ], "properties": { "kicker": { "type": "string" }, "title": { "type": "string" }, "subhead": { "type": "string" }, "items": { "type": "array", "minItems": 1, "maxItems": 60 }, "notes": { "type": "array" } } }

Decoding: temperature 0.15 · max 1200 output tokens · responseMimeType application/json · budget ~800 in / ~500 out · cost per run: 1 request against Gemini's free daily messages; the relay floor needs no key at all.

Questions worth asking before you cancel

Why should I paste excerpts instead of using Consensus directly?

If you need discovery across 200M papers, use Consensus — that is its product. This page displaces the metered reading layer: once a paper is in front of you, its finding, strength and quote can be filed for free, without spending a message.

What do the strength stamps mean?

HIGH is randomized or replicated direct evidence, MID is observational or single-study, LOW is in-vitro, animal or hypothesis — and every stamp must print the reason behind it. They are calibrated labels for appraisal, not scoring of 'truth'.

Can the claim check be trusted not to hallucinate?

Its rules forbid outside knowledge: the pasted excerpt is the whole world, verdicts must quote the decisive line, and topic-absent excerpts are UNSUPPORTED by construction. A verdict you can audit line by line.

Where did US$12 and the free limits come from?

From consensus.app/pricing, read 2026-09-27: the Free card printed 10 Pro messages and 3 Deep reviews a month, and the Pro card printed US$12 a month on annual billing. The monthly-billing figure did not render in that capture and stays unconfirmed in the artifact.

Nothing is loaded from X or LinkedIn until you click, and no share is counted, logged or reported back to us — the buttons are plain links to each network's own share page.

Next on the ledger