We keep coming back to the same little problems when we build financial tools. Which filing is the right one? Where did that number come from? Was it even public on the date we're asking about? And when an AI system gives a confident answer, does the cited material really support it?
We have to solve those problems for StockUp, but the solutions shouldn't all live inside StockUp. Other developers should be able to use the parts that help them, inspect how they work, and tell us when they fall short.
Four tools by the end of 2026
By December 31, 2026, StockUp will release at least four new open source finance tools that developers can use in their own projects. We will publish them on our GitHub organization.
We haven't settled on the four yet. Filing comparison, financial claim verification, calculation tracing, and point-in-time research are all on our minds. We want to hear what would be useful before we lock in the list. Naming four repositories now would be easy; making four tools people actually reach for is the harder part.
What you should expect from each tool
You should be able to pick one up and use it without a StockUp account. The code should be readable, the inputs and outputs should make sense, and there should be an example you can run. If we add a Quan integration, it will be optional.
We plan to include a clear open source license, setup instructions, examples, and tests. We also want to be direct about what each tool gets wrong or can't do yet. A missing filing or a stale figure is not a minor detail in financial research. Neither is a citation that looks convincing until you open it. Those are the cases we need to show, not hide.
We've already released a Quan MCP server. It was a start. The four tools in this pledge are additional releases, and some should be useful entirely apart from the StockUp API.
Tell us what you keep having to build
If you work with filings, market data, or finance AI, you probably have a small problem you've solved more than once. We'd like to hear about it through the StockUp GitHub organization. We'll put each repository there when it's ready, so you can see the code and hold us to the deadline.
We'll have to keep up with the work after release, too: answer issues, fix bugs, and improve the documentation. That's part of the pledge. The goal is to leave developers with tools they can depend on and financial research they can check for themselves.