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

How to screen companies as they stood on a past date with Qanat

Run a metric threshold screen on SEC filings using only what was public on a chosen date.

  • Top pick
  • Money
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forAn investment researcher who wants to test a valuation rule without look-ahead bias, after reading that most screeners only show today's data.

The problemStandard screeners reflect current data, so a rule tested on past dates quietly uses figures that were published later.

The outcomeA list of companies that passed the rule on the chosen date, plus a count of how many could and could not be evaluated.

What you need first

  • Python 3.10 or newer
  • uv or pip to install qanat-fdtl
  • A contact email for the SEC_USER_AGENT setting, which the SEC uses to identify requests (no API key or account)
  • An MCP-capable agent client, only for the agent use case

Steps

  1. Install Qanat with uv tool install qanat-fdtl (or pip install qanat-fdtl).
  2. Set your contact address with export SEC_USER_AGENT="your name [email protected]".
  3. Create a demo project with qanat init my-research --demo && cd my-research.
  4. Validate the project file with qanat check.
  5. Run the screen with qanat screen --filter '[{"metric":"pe","op":"<","value":30}]' --as-of 2025-12-31.

Prompt for your agent

In the Qanat project at <project-folder>, run a screen for metric pe below 30 as of <date> using the qanat screen command. Return the companies that passed, the count evaluated, and the count that could not be evaluated. Verify that the list is shown together with the unevaluated count so no companies are silently dropped.

Caveat. Qanat screens only on what companies reported in filings, and the bundled demo has no prices, so it cannot yet show what a list did next.

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