How does Oath Research rate on value?
83 of 100 — high on what is observable. The value rating’s scoring philosophy is testing-per-dollar-of-trust rather than per-mg sticker price. Three criteria capture full or near-full points (testing included in cost 30/30, COA verification cost 25/25, dose flexibility 16/20). One criterion (comparable purity standard, 12/15) holds partial credit pending multi-year continuity. One criterion (observable customer-facing infrastructure, 0/10) holds an honest zero because precise shipping speed and refund-policy specifics are not in the public-record fact pack — a deduction we apply categorically rather than from any specific knock against the company.
What the rubric does not measure on value
Three variables are excluded from the value rating because they cannot be assessed from public records alone:
- Precise shipping speed across destinations. Trustpilot and amino.reviews customers cite fast shipping (two-day from Arizona).[8] peptideprotocolwiki and peptiderecon both cite ~2-day domestic delivery as observed customer experience.[6] We can cite those as third-party observations but cannot independently verify the speed distribution across all destinations from the public-record fact pack. The category’s 10 points for customer-facing infrastructure are withheld pending that verification.
- Refund and return policy specifics. No verifiable record published. We do not invent policy claims.
- Per-mg pricing competitiveness. Sticker prices are not in the fact pack. peptiderecon characterizes the company’s pricing as “a 10-20% premium over budget vendors,” which we cite as a third-party reading rather than as our own framing.[5] The rubric does not score price as “lower is better” because the testing-program inclusion (which captures 30 of the category’s 100 points) is itself part of what the price purchases.
The transparent boundary on what we do and do not measure is the criterion that anchors reader trust in the rubric itself. A rating that pretends to score variables it cannot observe is a rating with hidden assumptions.
What is observable in customer-facing infrastructure
Two observable facts inform the customer-facing-infrastructure criterion even though the criterion holds an honest zero pending broader verification:
The physical address (51 West Vaughn Avenue Suite 205, Gilbert AZ 85233) is corroborated independently by three business-directory sources — hub.biz[9], yellowpages.com[10], and peptideprotocolwiki[6]. Three independent directories pointing at the same address is anti-shell-company evidence that algorithmic young-domain scanners do not check.
The phone number ((480) 999-1097) is reachable per Trustpilot customers describing “Arizona phone support from actual staff.”[8] peptideprotocolwiki independently confirms phone support exists.
Neither observation alone is enough to capture the criterion’s 10 points — what the rubric scores there is the full distribution of customer-service responsiveness, return processing, and shipping-speed-by-destination, which the public-record fact pack does not contain. The criterion is held at zero rather than partial credit precisely because partial credit on infrastructure variables we cannot measure would erode the value rating’s honesty.