Valuation calculators
What this is warning you about first. a single model is not a price target. The calculator returns a fair-value range with an explicit exclusion reason when an input combination is structurally invalid (e.g. negative terminal FCFF, missing WACC, archetype mismatch). Read the range, the exclusion notes, and the reliability score, not the midpoint in isolation.
status: computed | excluded | failed and an explicit reason for non-computed runs. Read the range and the exclusion notes, not the midpoint alone.Dedicated calculator URLs
Each calculator has its own canonical URL for analysts, search, API docs, and LLM tool references. This all-model workbook remains the quick switching surface.
The calculator is stateless. Nothing you enter is persisted on this public surface. Authenticated workbooks can layer save/load and premium ticker prefill on the same kernel.
Programmatic access lives in the developer documentation at /developers. Every response is stamped with methodology_version = valuation-calculators.v1.
Frequently asked questions
- Do these models replace the published per-stock reports?
- No. The reports apply the same kernel to assembled financials with archetype calibration, six-factor scoring, and the bear-case-first narrative. The calculator is the stateless math surface: useful for stress-testing one assumption, not for substituting the analysis.
- Why does my run return `excluded` instead of a fair value?
- Each model declares the inputs and archetype combinations it can compute against. If WACC is missing for an FCFF DCF, or the archetype is not REIT for the NAV/AFFO model, the kernel returns `status: excluded` with an explicit `exclusionReason` (e.g. `wacc_ebit_or_shares_missing`, `archetype_not_reit`). That is the contract, not an error.
- Are sensitivities computed by scaling the mid-point?
- No. Each cell of the sensitivity matrix re-runs the full calculator pipeline with the offset assumption applied. There is no synthesis-output scaling. The whitelisted axes are declared per model in the catalog response.
- How do I supply growth as a percent vs a decimal?
- Rates default to decimals (0.10 = 10%). To send display percent (10 instead of 0.10), set `display_percent: true` on the relevant bag. The kernel normalises both shapes. PEG growth is always integer percent (20 for 20%) by convention.