Testides
Peptide-testing platform with a genuine public report lookup: each COA carries a report code that resolves to the full certificate through the Testides public API.
This label reflects how the provider presents itself on its own site today, not a formal accreditation category.
Whether the site appears to invite direct sample submission from individuals rather than only business or institutional clients.
Whether the provider appears to offer public-facing report publishing, result browsing, or direct verification tooling.
This is our shorthand for how visible the provider's result or verification layer appears to be, ranging from none to searchable public verification.
Location details are kept conservative and only shown when clearly supported by the source page or the provider’s public materials.
What we can verify now
Testides runs a real public report lookup, which we confirmed during a vendor onboarding rather than inferring from its portal styling.
Vendor COAs that name Testides carry a report code that resolves to the full certificate through the Testides public report API (testides.com/api/reports/public/{code}). We verified this is genuine: a real code returns the report, while an invalid code 404s — so a reader holding a Testides-backed COA can independently confirm it.
Why it matters in the current ecosystem
That puts Testides in the provider-verifiable tier: a vendor whose COAs resolve against the Testides API is meaningfully more checkable than one that only hosts a static document. This is what moved Pepvida from a bare-storefront score into a materially higher one once the verification chain was followed.
What to watch for
The lookup confirms an individual report, not the vendor’s whole catalog, and Testides’ own intake flow and pricing are still thin on public detail. Treat it as a verification endpoint you can check a specific COA against, rather than a fully documented direct-to-consumer testing service.