QuantConomy is in open-ended early access. There is no committed launch date, and we are not going to invent one for a countdown widget. That leaves a pre-launch data product with exactly one honest move: label the difference between what is running today, what is being built, and what is only an example. This post is a map of those labels, so you can hold us to them.
Three kinds of truth on a pre-launch site
Everything on this site falls into one of three buckets. Live data: things actually running, fed by the real pipeline. Roadmap: things being built, described in future tense with a status attached. Illustrative examples: sample outputs that show the shape of the product without pretending to be current. Most early-access sites blur these three, usually in the flattering direction. We try to keep the seams visible, because the seams are the truthful part.
What is live today
The homepage roadmap marks the public market feed as Live, and it is: the input layer of news moving into the signal surface, on the real pipeline. The insider trading tracker is also genuinely live. It shows SEC Form 4 insider trades by company, parsed from EDGAR filings and refreshed continuously, and every row links back to the filing it came from, so you do not have to take our word for it. If you want to see the product working before you believe anything else on this site, those are the two places to look. The demo shows the same surface in a guided form.
What is labeled beta, and why
The API and agents page carries an explicit “API & Agents · beta” badge, and below it a list of what we are still finalizing, quoted here in full: “Publish the stable API base URL and reference docs. Open beta account onboarding and API-key issuance. Settle usage limits and verify accounts end to end. Ship the installable MCP package and tool scopes. Finalize which datasets are available in the beta.” The signal engine and datasets already run behind the scenes; the beta work is about opening them up cleanly. Publishing the unfinished list costs us some polish and buys something better: when those items ship, you can verify the claim against the list.
Why example data is marked illustrative
The API page shows endpoint output so you can see what a signal looks like: type, direction, strength, reason, source, expiry. Those example lines are labeled as illustrative, not live data, and our machine-readable site description says the same thing: example data shown on the marketing site is illustrative, not live. We could quietly pipe real rows into the marketing page and let you assume everything you see is current. We would rather you learn the shape from a labeled example and see real data where it actually is live, on the tracker, than wonder later which parts of the site were dressed up.
Why this matters more for a data company
For most products, an overpromising landing page costs you a disappointed first session. For a data product, it poisons the core promise. Our whole pitch is that signals are source-linked so you can check them instead of trusting them. A company that fudges the line between live and illustrative on its own website is asking you to extend exactly the blind trust the product exists to remove. Labeling our own claims correctly is not a marketing choice. It is the product’s argument applied to itself. More on how we think about this on the about page.
Where to check for yourself
You do not need to take this post on faith either. The homepage roadmap carries the status labels: Live, Up next, In progress, Separate track. The API page carries the beta badge, the finalizing list, and the illustrative-data disclaimer. The tracker carries EDGAR links on real filings. If any of those labels ever stops matching reality, that is a bug, and we would want to hear about it.
Trust in a data product starts with the company labeling its own claims correctly.