DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to compare two web pages and cite each claim with Jevry

Ask Jevry to read two or more pages and return a comparison with citations to the pages it read.

  • Top pick
  • Research
  • Intermediate
  • 60 minutes
  • From the README
  • Any agent

Who it is forA researcher or analyst who must compare policies, terms, or specs across several sites and needs cited answers quickly.

The problemReading several pages side by side and copying exact wording into a summary is slow and easy to get wrong.

The outcomeA comparison answer with citations to the source pages, which you can check against the visible browser tabs.

What you need first

  • Node.js 22.12 or newer with npm
  • A TypeSafe Jev API key from the official quickstart
  • A separate text-model connection: a locally authenticated Codex or Claude Code CLI, or an OpenAI-compatible or Anthropic API key
  • Budget for model usage, which can cost money and has no fixed per-task cost

Steps

  1. Run git clone https://github.com/michaelswissa/jevry.git and then cd jevry.
  2. Run npm ci, then run npm run dev to open the Electron desktop app.
  3. Enter your TypeSafe Jev API key and connect a text model in the app setup.
  4. Open the first source page, then ask Jevry to compare it with the second page and cite both.

Prompt for your agent

Use the repo michaelswissa/jevry: after starting it with npm run dev, ask the desktop app to compare the cancellation policies at <url-1> and <url-2> and cite each claim. Expect a comparison with citations; verify each cited sentence appears on the matching visible page.

Caveat. The README describes research and citation as a live fixed-corpus study, so check every citation yourself before relying on it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page