Pimavanserin

Limits on what this shows

• Key negative/null findings: No clinical mitochondrial marker (e.g. lactate, creatine kinase) has been reported for pimavanserin in any source reviewed. The breast-cancer apoptosis finding is itself evidence against a generalized "mitochondrial protection" framing, underscoring that the effect is cell-type dependent rather than a uniform drug property.
• At-risk subgroups: None identified; not applicable given preclinical-only evidence in non-target tissue (rat neurons, human cancer cell lines) rather than in treated patients.
• Counter-evidence on record: The two available findings partially counter each other in direction (protective in neurons versus pro-apoptotic in cancer cells), which is itself why this is graded yellow, mechanistic plausibility only, rather than any higher tier or a confident single-direction claim.

Regulatory status

Not addressed in the FDA label; no mitochondrial toxicity signal appears in the Boxed Warning, Warnings and Precautions, or Adverse Reactions sections.

Population evidence

None in humans. Two Tier B in vitro studies, both drug-specific: (1) Lavigne EG, Buttigieg D, Steinschneider R, Burstein ES. "Pimavanserin Promotes Trophic Factor Release and Protects Cultured Primary Dopaminergic Neurons Exposed to MPP+ in a GDNF-Dependent Manner." 2021, PMID 34032411. Primary rat dopaminergic neuron cultures exposed to the parkinsonism-inducing toxin MPP+; pimavanserin (and comparator M100907) signaled through ERK1/2, restored mitochondrial function, and reduced oxidative stress, with the effect blocked by anti-GDNF but not anti-TrkB antibodies. Exact concentrations were not available in the retrieved abstract text. (2) Zhang Y, Huang Q, Xu Q, Jia C, Xia Y. "Pimavanserin tartrate induces apoptosis and cytoprotective autophagy and synergizes with chemotherapy on triple negative breast cancer." Biomedicine & Pharmacotherapy, 2023, PMID 37832400, DOI 10.1016/j.biopha.2023.115665. Triple-negative breast-cancer cell lines; pimavanserin tartrate induced mitochondria-dependent intrinsic apoptosis and cytoprotective autophagy, and synergized with doxorubicin. This is an experimental oncology-repurposing study at research-stage, non-oral concentrations, not a toxicity finding relevant to a patient taking labeled oral doses for Parkinson's disease psychosis.

Mechanism

Named only at the preclinical level: GDNF/ERK1/2-mediated trophic signaling (protective, neurons) and an intrinsic (mitochondria-dependent) apoptosis pathway (cancer cells). No mechanism has been characterized in intact human mitochondria at therapeutic oral dosing in any source located.

Counter-evidence held on record

Preclinical, cell-type-dependent findings only. Nothing here supports a mitochondrial-support supplement (for example coenzyme Q10 or L-carnitine) for a person taking pimavanserin, and no dosing recommendation is made. See Overlap map: this entry and Oxidative stress share the Lavigne 2021 source.

Limits on what this shows

• Key negative/null findings: No human redox-marker study for pimavanserin was located. PubMed "pimavanserin oxidative stress" (3 results total) surfaced only the Lavigne 2021 study, the Luptak 2021 non-drug-specific review, and an unrelated analytical-chemistry method-validation paper (Radic I, Runje M, Babic S, 2021, PMID 33964725, concerning oxidative degradation products of the pimavanserin molecule itself during assay development, not a biological oxidative-stress finding).
• At-risk subgroups: None identified.
• Counter-evidence on record: None found contradicting the single available study; the finding itself runs opposite to a depletion framing (protective, not depleting).

Regulatory status

Not addressed in the FDA label.

Population evidence

Tier B: Lavigne et al. 2021, PMID 34032411 (see Mitochondrial burden entry for full citation). In the same MPP+-stressed primary rat dopaminergic neuron culture, pimavanserin reduced oxidative stress concurrently with restoring mitochondrial function, via GDNF-dependent ERK1/2 signaling. A separate narrative review, Luptak M, Michalickova D, Fisar Z, Kitzlerova E, Hroudova J, "Novel approaches in schizophrenia, from risk factors and hypotheses to novel drug targets," 2021, PMID 34327122, discusses oxidative stress broadly across schizophrenia pharmacotherapy hypotheses and names pimavanserin only in a general list of agents under investigation; it provides no pimavanserin-specific oxidative-stress data and is Tier C/D for this purpose, not used to support the grade.

Mechanism

GDNF/ERK1/2-mediated trophic signaling in a neurotoxin-injury model, as named in the source. No redox-cofactor or antioxidant-vitamin mechanism is identified, and no oxidative-stress-inducing mechanism for pimavanserin was found in any channel searched.

Counter-evidence held on record

This is a protective, not a depleting, signal from a single preclinical study. It does not support antioxidant supplementation and is not a basis for any consumer-facing deficiency claim. Shares its entire evidentiary basis with Mitochondrial burden above (see Overlap map); do not count as a second, independent confirmation.

Limits on what this shows

• Why no grade: Both sides of the dual-condition test point to ungraded: no Tier B or C evidence supports even a yellow grade for pimavanserin and copper, and no circulating claim pairing pimavanserin with copper was located. NUPLAZID's adverse-reaction table names no trace-mineral term at any frequency. No class extrapolation was attempted: pimavanserin's distinct 5-HT2A-only mechanism, with no appreciable dopamine D2 affinity, fails the Hard Rule 6 cohort test against any copper literature rooted in dopamine-receptor-blocking antipsychotics.

Channels tried

Original pass: PubMed search-listing query "pimavanserin AND copper" completed successfully and returned a clean zero-results page; Europe PMC REST API was blocked by organization-level network policy (HTTP 403). Repair pass (this revision): PubMed "pimavanserin AND ceruloplasmin" completed successfully, clean zero results; "5-HT2A inverse agonist copper" was rejected with an HTTP 429 rate limit before returning content; Europe PMC REST API was again rejected with an HTTP 429 at the proxy; the Crossref API (query.bibliographic=pimavanserin+copper) returned valid JSON, and of the five most relevant indexed works for pimavanserin none discussed copper or trace minerals. The FDA/DailyMed label was re-checked this pass for "copper," "ceruloplasmin," and "ferritin" and none appear anywhere in the label. A general web search for consumer nutrient-depletion content naming pimavanserin and copper remains untested: this session's WebSearch budget was exhausted before either pass began.

Genuine gap vs tooling limited

Leans toward a genuine gap for the academic literature: across two passes, every completed query (PubMed twice, Crossref once) returned a clean negative, no block ever returned a positive or ambiguous result, and the Tier A label itself names no copper-related term. The weaker part of the test remains the consumer-claim side, which still could not be run due to the WebSearch exhaustion disclosed above, and the Europe PMC channel remains unreachable in both passes. A future revision with WebSearch access should re-run the consumer-claim side before treating this category as fully closed.

Limits on what this shows

• Why no grade: Both sides of the dual-condition test point to ungraded: no Tier B or C evidence supports even a yellow grade for pimavanserin and iron, and no circulating claim pairing pimavanserin with iron was located. No class extrapolation was attempted for the same cohort-test reason given under Copper.

Channels tried

Original pass: two PubMed phrasings, "pimavanserin AND iron" and "pimavanserin iron metabolism," both completed successfully with clean zero-results pages; Europe PMC blocked by organization-level network policy on every attempt. Repair pass (this revision): "5-HT2A inverse agonist iron homeostasis" on PubMed was rejected with an HTTP 429 rate limit before returning content; the Semantic Scholar graph API reached its target server (api.semanticscholar.org) rather than being blocked at the gateway, but the target itself returned an HTTP 429 rate limit; the Crossref API (query=pimavanserin+iron) returned valid JSON with none of the top matches discussing iron, and a second, more targeted Crossref bibliographic query likewise surfaced no pimavanserin-iron overlap. The FDA/DailyMed label was re-checked this pass for "iron," "ferritin," and "anemia" and none appear anywhere in the label. Consumer circulating-claim search remains untested due to the disclosed WebSearch exhaustion in both passes.

Genuine gap vs tooling limited

Leans toward a genuine gap for the academic literature: across two passes, every completed query (PubMed twice, Crossref twice) returned a clean negative and the Tier A label names no iron-related term; the two blocks this pass (a PubMed 429 and a Semantic Scholar target-side 429) are disclosed but did not prevent a reasonably thorough multi-host attempt. The consumer-claim side remains untested due to the disclosed WebSearch exhaustion. Flagged for re-attempt on that side in a future revision.

Limits on what this shows

• Why no grade: Both sides of the dual-condition test point to ungraded on the evidence actually obtained: no Tier B or C evidence was retrieved, and no circulating claim was located. Class-level evidence was also checked and found wanting: a PubMed search for "5-HT2A receptor antagonist gut microbiota," broad enough to catch any class-level signal that might support a yellow grade by extrapolation, returned a clean zero, so even the weaker Tier C path is closed, not merely unattempted.

Channels tried

Original pass: three PubMed phrasings ("pimavanserin AND microbiome," "pimavanserin AND gut microbiota," "pimavanserin gut bacteria") were all blocked, by a proxy 429 and two bot-verification pages respectively, and the Europe PMC REST API was blocked by organization-level network policy. Repair pass (this revision): "pimavanserin AND microbiome" on PubMed was rejected again with an HTTP 429, and the Europe PMC REST API was rejected again with an HTTP 429 at the proxy; a broader class-level PubMed query, "5-HT2A receptor antagonist gut microbiota," did complete and returned a clean zero-results page with no drug named; the Crossref API (query.bibliographic=pimavanserin+gut+microbiota) returned valid JSON, and its most relevant matches were generic gut-microbiome research (appetite-regulation metabolites, the microbiota-gut-brain axis, an animal microbiota study) with no pimavanserin connection in any of them. The FDA/DailyMed label was re-checked this pass: it lists nausea (7% vs 4% placebo) and constipation (4% vs 3% placebo) as common adverse reactions, which are gastrointestinal motility effects, not a measured microbiome composition or diversity change, so per Hard Rule 2 they are not carried into this entry as a microbiome finding. Consumer circulating-claim search remains untested due to the disclosed WebSearch exhaustion in both passes.

Genuine gap vs tooling limited

Still a mix of both, but less tooling-limited than the original pass: PubMed and Europe PMC remain blocked for the direct drug-plus-microbiome query in every attempt across two passes, which keeps a real access gap on the record. Against that, two channels did complete cleanly this pass, a broader class-level PubMed search and a Crossref bibliographic search, and both came back negative rather than blocked, which is new evidence the first pass lacked. A future reviewer should keep retrying "pimavanserin" combined with "microbiome," "microbiota," and "gut bacteria" against PubMed and Europe PMC once those two specific hosts are reachable, since they are the only channels that have never once completed for this exact drug-plus-category pairing.

Limits on what this shows

• Why no grade: Both sides of the dual-condition test point to ungraded. NUPLAZID's adverse-reaction table was checked explicitly for anemia, hemoglobin, and hematocrit terms; none appear under the common (≥5% and ≥2x placebo) adverse reactions, the postmarketing list, or the pediatric trial adverse-reaction list. The label's QT-prolongation precaution names pre-existing hypokalemia and hypomagnesemia as risk factors to avoid before combining pimavanserin with other QT-prolonging drugs; this describes a caution about patients who already have those electrolyte states, not a documented effect of pimavanserin itself on electrolyte status or oxygen delivery, and is excluded from grading on that basis per Hard Rule 2.

Channels tried

Original pass: two PubMed phrasings completed successfully with clean zero-results pages, "pimavanserin AND anemia" and "pimavanserin AND hemoglobin"; a third, "pimavanserin AND hematocrit," was rejected with an HTTP 429 and could not be completed. Repair pass (this revision): "pimavanserin AND oxygen saturation" on PubMed completed and returned zero results; the Crossref API (query.bibliographic=pimavanserin+hemoglobin+hematocrit) returned valid JSON, and its top matches were unrelated hemoglobin/hematocrit assay and clinical-measurement papers with no pimavanserin connection in any of them; the OpenAlex works-search endpoint (api.openalex.org, query "pimavanserin hemoglobin") reached its target server rather than being blocked at the gateway, but the target itself returned an HTTP 429 rate limit before content could be read. The full NUPLAZID adverse-reaction table (Tier A) was re-read this pass specifically for hematologic and oxygen-delivery terms and confirmed to name none at any frequency.

Genuine gap vs tooling limited

Leans toward a genuine gap: the Tier A label is a complete, drug-specific document, re-confirmed this pass to name no hematologic or oxygen-delivery adverse reaction at any frequency, and across two passes every completed query (PubMed three times, Crossref once) returned a clean negative. The hematocrit PubMed phrasing (original pass) and the OpenAlex attempt (this pass) were both blocked rather than completed and remain disclosed gaps; the unavailable consumer-claim search is disclosed for completeness and should be re-attempted in a future revision.

Limits on what this shows

• Why no grade: Both sides of the dual-condition test point to ungraded. The two pimavanserin-specific mitochondrial studies located (Lavigne 2021, Zhang 2023, graded under Mitochondrial burden above) measured mitochondrial function/membrane effects, oxidative stress, and apoptosis, not ATP synthesis or output directly; per this project's standing rule keeping ATP production independent from Mitochondrial burden even when a source is shared, neither study is extended to carry this category on its own. NUPLAZID's adverse-reaction table lists no energy-metabolism or creatine-kinase term at any frequency.

Channels tried

Original pass: PubMed query "pimavanserin AND 'ATP'" returned 3 false-positive results (general safety/efficacy studies with no energy-metabolism content, matched only on the incidental letters "ATP") and were not cited as support; two further phrasings, "pimavanserin AND 'energy metabolism'" and "pimavanserin AND 'oxidative phosphorylation,'" both completed with clean zero-results pages. Repair pass (this revision): "pimavanserin AND oxidative phosphorylation ATP synthase" on PubMed completed and returned zero results; "pimavanserin AND mitochondrial ATP" on PubMed was rejected with an HTTP 429 before completing; the Crossref API (query.bibliographic=pimavanserin+ATP+mitochondrial+energy) returned valid JSON, and its top matches were generic mitochondrial-bioenergetics papers (ATP synthase structure, ATP/ROS quantification methodology, an unrelated drug rescuing mitochondrial energy dysfunction) with no pimavanserin connection in any of them. The FDA/DailyMed label was re-checked this pass for "ATP," "mitochondria," "oxidative phosphorylation," and "energy metabolism," and none appear; "fatigue" does appear as an adverse reaction leading to discontinuation at twice the placebo rate (1% vs 0%), but this is a clinical symptom, not a measured ATP or energy-metabolism marker, so per Hard Rule 2 it is not carried into this entry as an energy-metabolism finding, consistent with it also not appearing as a graded entry elsewhere in this dossier.

Genuine gap vs tooling limited

Leans toward a genuine gap: across two passes, every completed query (PubMed four times, Crossref once) returned either a clean zero or only false-positive keyword matches, none surfacing usable drug-specific ATP-production evidence, and the Tier A label names no energy-metabolism term. One phrasing this pass was blocked (mitochondrial ATP, HTTP 429) and is disclosed as not completed. The unavailable consumer-claim search is disclosed for completeness per the same WebSearch-exhaustion limitation noted throughout this review.