Open data. No key, no login.
Everything we publish about a lot, the certificate, the lab, the purity result, the fingerprint of the certificate file, is readable by machines as well as people. If you want to check us with a script instead of a browser, this page is for you.
We put certificates in front of the checkout button because we think that is where they belong. Publishing the same data as open endpoints is the next step: it lets a researcher, a lab, a reviewer or a competitor pull our records straight from the source and check them without trusting our web page to tell the truth. Nothing here needs an account. Nothing here is rate-limited in any way you will notice.
1. Certificate feed
A static JSON snapshot of every released lot with a published certificate. Regenerated when lots are released. Best for archiving, indexing, or a quick look.
# one line, no headers
curl -s https://vaelith.co/coa/index.json | jq '.lots[] | {compound, lot, hplc_purity, lab, test_date}'
| compound | Product name as sold |
| lot | Lot number printed on the vial and encoded in its QR code |
| content | Measured net content, in milligrams |
| hplc_purity | Purity by HPLC, as reported by the lab |
| identity | Identity confirmation method (mass spectrometry) |
| lab · test_date | Independent laboratory and the date on its report |
| coa_page · coa_pdf · lab_verify | Our certificate page, the original report file, and the lab's own verification link |
| cas · formula · mw | Compound identifiers where known |
2. Live lot ledger
The same database our verify page reads, exposed read-only through PostgREST. Row-level security means the public key can see released lots and nothing else. Add the public key as an apikey header; it is the same key that ships in our page source, so there is nothing to protect.
# every released lot with its certificate fingerprint curl -s 'https://idsqbxhjnieveegasowy.supabase.co/rest/v1/lots?select=lot_no,strength,purity,tested_by,test_date,coa_img,coa_doc,lab_verify_url,coa_sha256,coa_sha256_at,products(name,peptide)&released=eq.true&order=test_date.desc' \ -H 'apikey: sb_publishable_SMNu5rDAesZwg5kIU7dZIw_YjrlOKHD' # one lot curl -s 'https://idsqbxhjnieveegasowy.supabase.co/rest/v1/lots?select=*,products(name)&lot_no=eq.VLT-BPC-10MG-001' \ -H 'apikey: sb_publishable_SMNu5rDAesZwg5kIU7dZIw_YjrlOKHD'
Filters follow PostgREST syntax: tested_by=eq.Kovera%20Labs, purity=gte.99, order=created_at.desc, and so on. The products table is public the same way: /rest/v1/products?select=id,name,peptide,stock,cas,formula,mw&active=eq.true.
| Compound | Lot | Purity | Lab | Tested | Fingerprint |
|---|---|---|---|---|---|
| Loading the public endpoint from your browser, right now. | |||||
3. Lot passports
The human-readable passport for a lot: its history, certificate, lab verification link, what the certificate covers and what it does not, a live fingerprint check, and the compound's 3D structure where we have a verified one. This is the URL every vial's QR code points to, so a scanned vial and a typed link land on exactly the same record.
4. Certificate fingerprints
When a certificate is published we record a SHA-256 hash of the file bytes: every certificate page concatenated in order, or the single report file when there are no page images. The passport recomputes that hash in your browser from the file you are looking at and compares the two. You can do the same from a terminal, without us in the loop:
# pages in the order listed in coa_img (comma-separated), or the single coa_doc file curl -s 'PAGE_1_URL' 'PAGE_2_URL' | sha256sum # compare the result with coa_sha256 for that lot
If a certificate is legitimately re-uploaded, the database clears the old fingerprint automatically and a new one is recorded, with coa_sha256_at showing when. A fingerprint can never silently outlive the file it describes.
5. Compound structures
MDL molfiles (V2000) for the compounds we have a verified published structure for: a single energy-minimized conformation computed with RDKit ETKDG and MMFF94 from the PubChem structure, with the PubChem CID stored in the file's properties. Useful for a viewer, a cheminformatics pipeline, or a sanity check that we know what we are selling. Slugs match the research pages, for example bpc-157, tb-500, semaglutide, tirzepatide, nad.
These are computed conformations, not measured structures, and we say so on every viewer. Blends, proteins without a defined small-molecule structure, and compounds we could not verify have no file rather than a guessed one.
Fair use
Use it, cache it, build on it, cite it. Attribution to Vaelith is appreciated but not required. Please do not hammer the live endpoint in a tight loop when the static feed would do, and please do not present our data as your own testing. Everything here describes materials supplied for laboratory research use only; nothing in these endpoints is dosing, medical, or human-use information, and none of it should be read as such.
Questions, a field you wish existed, or a discrepancy you found: [email protected]. If you catch something wrong we would rather hear it from you than anyone else.