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

How to ask many questions of one indexed annual report with Jev Doc Search

Uploads a report once, then reuses its doc_id to answer each new question.

  • Research
  • Intermediate
  • 45 minutes
  • From the README
  • Any agent

Credentials. The stored doc_id gives access to the indexed document in your PageIndex account, so treat it like a private reference.

Who it is forA researcher or finance analyst who will ask several questions of the same annual report and wants to avoid uploading it every time.

The problemRe-uploading the same long PDF for each question is slow and repeats the indexing work.

The outcomeAfter one upload, each new question returns the kept pages for that question, using the same stored doc_id.

What you need first

  • Python with pip available
  • A TypeSafe API key from the TypeSafe console
  • A PageIndex API key from the PageIndex dashboard
  • The PDF you want to search

Steps

  1. Run pip install -r requirements.txt in the repo folder.
  2. Run export TYPESAFE_API_KEY="..." and export PAGEINDEX_API_KEY="..." with your own keys.
  3. Run python tree_search.py NVIDIA_10K.pdf "What was NVIDIA's gross margin for fiscal year 2026?" once, and copy the printed doc_id. (inferred, check the README)
  4. Run python tree_search.py pi-... "What was NVIDIA's total revenue for fiscal year 2026?" with the copied doc_id for each new question. (inferred, check the README)

Prompt for your agent

Using the repo VectifyAI/jev-doc-search, upload <path-to-pdf> once with tree_search.py, then run it with the returned doc_id for each question in <question-list>. Output the kept pages per question. Verify that the doc_id stays the same across runs and that each answer page matches the question's topic.

Caveat. The README shows doc_id reuse for one document only, so confirm the reused doc_id still returns sensible pages before asking many questions.

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