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

How to answer factual questions from Wikipedia and web search with Jev Chat

Get sourced facts from Wikipedia and Brave Search, with no model writing the answer.

Who it is forA researcher or student who wants short factual answers pulled from a reference source and does not want a summary invented by a model.

The problemGeneral chatbots blend memory and guesses into answers, so users cannot tell which facts came from a source.

The outcomeFactual answers such as a mountain height or a podcast host, each built from Wikipedia or search tool data.

What you need first

  • Node 24 or later and pnpm 11 (run corepack enable to pick up the pinned version)
  • A TypeSafe API key in TYPESAFE_API_KEY, since Jev is a paid API and the app shows error replies without it
  • A terminal and a local browser on the same machine, because the API only listens on 127.0.0.1

Steps

  1. Run pnpm install in the repo folder.
  2. Run cp .env.example .env, set TYPESAFE_API_KEY, and add BRAVE_API_KEY if you want web search.
  3. Run pnpm dev and open http://localhost:5173.
  4. Type "How tall is Mount Rainier?" and "Who hosts the Syntax podcast?".
  5. Open the inspector pane for a reply to see which tool was called and what it returned.

Prompt for your agent

In the jev-chat repo, run pnpm dev with TYPESAFE_API_KEY set in .env, then send "How tall is Mount Rainier?" to the chat at http://localhost:5173. Report the reply and the tool named in the inspector. Verify that the height value appears in the tool result shown in the inspector.

Caveat. Without BRAVE_API_KEY, only the no-key servers such as Wikipedia answer, so web search questions will not return results.

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