Terminals state numbers. QuantLogix shows its work.
Every material figure on this platform carries a receipt: the primary source it came from, the timestamp
we fetched it, the method that verified it, and a link to check it yourself. Hover the
ⓘ
chip beside a number anywhere on QuantLogix to see its receipt.
Live coverage
Receipts issued
—
material figures with full lineage
Companies receipted
—
of — tracked private companies
Registry-verified
—
name-verified against a public registry
Freshness
—
last registry sweep
The four words on every receipt
Registry-verified
Name-verified against an authoritative public registry at fetch time — USASpending.gov, ClinicalTrials.gov, Hugging Face. The strongest claim we make, and the one competitors can't: their numbers don't cite.
As reported
Disclosed by the company or credible press. We carry it as reported and say so — we don't launder disclosure into fact.
QL model
A QuantLogix estimate, like blended secondary marks. Our number, our documented method, labeled as ours — never dressed up as a disclosure.
Unverified
No confirmable source on file. We show the gap instead of filling it — an honest absence beats invented precision.
Anatomy of a receipt
Anduril Industries — Federal obligations (36 mo):
$2.2B+← click the chip
Each receipt answers four questions: where (the primary source and what kind of authority it is), when (the fetch timestamp — not "recently"), how (the verification method, including its limits), and check it (a link to the source, so you never have to take our word for it).
Sources we receipt against
For developers & AI agents
Receipts are machine-readable. GET /api/provenance?entity=anduril returns every receipt for a company; GET /api/provenance?stats=1 returns platform coverage. Grounded facts with lineage — built for the agent era, where an uncited number is a hallucination waiting to happen. See the API docs and MCP server.
Receipts describe data lineage, not investment advice. QuantLogix is not a registered investment advisor. Registry data reflects the registry's own publication lag; "as of" is our fetch time, not the underlying event time.