Correction, 29 September 2026. We removed a statement that API keys are stored hashed (they are stored as issued) and an unchecked description of the cache as fail-closed.
Methodology, sources, and the team behind the API
ALETHEIA is a chemical safety API. It aggregates hazard classifications from major government agencies and authoritative databases worldwide into a single statistical reference layer — with the disagreement between sources preserved, not hidden.
The platform is built and operated by Holistic Quality LLC. Coverage today spans 1,887 distinct compounds, 1,287 consumer products across eight product tiers, and 959 raw materials. Every response includes the underlying source positions, per-source weights, and confidence intervals so downstream systems can audit the math.
Regulatory bodies routinely disagree on the same compound. IARC may classify glyphosate as “probably carcinogenic” while EPA and EFSA reach the opposite conclusion. All three are working from solid methodology and extensive evidence — they simply weigh it differently.
Most safety datasets collapse that disagreement to a single “score,” quietly making editorial decisions about which agencies to trust. ALETHEIA does the opposite: it surfaces the distribution and lets the consumer of the data make the call. That makes the API a defensible input for product safety reviews, supplier screening, and consumer-facing tools where the audit trail matters.
Each compound query returns the full statistical shape across sources — mean, standard deviation, 95% confidence interval, and the underlying per-source positions. Where consensus exists we say so; where it doesn’t, we expose the disagreement.
Source weights are computed from three inputs, by fixed rules:
The weight applied to each source is included in the response payload. These weights and thresholds are ALETHEIA conventions under review, not regulatory standards.
The API never asserts “safe.” It returns context-scoped risk profiles (“low risk at typical adult dermal exposure,” for example), each citing the sources behind it, with explicit gaps where data is thin.
The aggregation is weighted statistics in a five-dimensional space. No neural networks, no proprietary scoring, no opaque pipelines. The dimensions and thresholds are documented below; the code is reviewable.
Every regulatory classification is projected into five normalized dimensions, each bounded to [0, 1]:
Live demo · prototype
Three compounds, two contexts. Same five lenses, same coordinate system — the shape changes with the (compound, context) pair. Click any cell to open the live Looking Glass at that state.
Read across the rows: Theobromine transforms (mild → severe), Glyphosate stays contested in both contexts (dashed borders on Magnitude), Lead reads severe regardless of context. That's the methodology — same coordinate system, different epistemological situation, different shape.
Severity of the hazard. Each agency’s classification system is mapped to a numeric scale — IARC Group 2A → 0.700, EPA “not likely” → 0.150, and so on. The full mapping is not published on this page; it is an ALETHEIA convention, not a regulatory standard.
How well-supported the classification is, based on sample size, methodology rigor, peer review status, and independent replication. High confidence is not a claim of correctness; it is a claim that the position is well-supported by available evidence.
Time-weighted relevance on an exponential curve, exp(−t/5) for a study t years old: 0.368 at 5 years and 0.135 at 10. For sources labelled exactly IARC, US EPA, EPA, EFSA, NTP, CalEPA or ECHA the value is floored at 0.500. Older data is included but discounted.
Study design quality, drawn from the evidence-based-medicine hierarchy: anecdotal (0.10) → case report (0.25) → case series (0.40) → case-control (0.55) → cohort (0.70) → RCT (0.85) → meta-analysis (0.95) → systematic review (1.00).
How closely the source population matches the query context. A study on mammals applied to a dog-context query is weighted lower than a study on the same breed; broad extrapolation carries a cost in the final aggregation.
Consensus is reported as true when all of the following
hold:
Consensus strength is reported on a 0–1 scale (1.0 = perfect agreement). When consensus does not exist, the API does not manufacture a false majority — it returns the actual distribution.
Coverage. ALETHEIA holds records for the compounds listed in its index. They were added in 2026, and no selection rule was recorded, so the set is not a sample of any defined group of substances. A compound with no record here has not been assessed by us: no record is not the same as no concern.
Hazard classifications and supporting evidence are drawn from authoritative regulatory bodies and reference databases:
The underlying compound, material, and product corpus is maintained in the HQ Safety Database, which is open for inspection.
ALETHEIA is operated by Holistic Quality LLC, founded by Levi Robey. The company builds safety and quality infrastructure with the explicit goal of being usable by technical teams that need an audit trail, not just a marketing score.
Development is conducted with extensive human-AI collaboration. The methodology, the source list, the weighting rules, and the per-call response payloads are all designed so that an external reviewer can verify the math without trusting the operator.
The name “ALETHEIA” comes from the Greek ἀλήθεια — unconcealment. The thesis the project is built on: the full shape of what is known is more useful, and more honest, than a single number.
Evaluating ALETHEIA for a commercial deployment, a regulated workflow, or a custom integration? Reach the team directly at levi@holisticquality.io. Bug reports and security disclosures: safety@holisticquality.io (see also our security.txt).