Data sources
Public databases used to populate this directory
All chemical, literature, trial, and protein data is sourced from public biomedical databases. None require an API key to access at the request volumes we use.
| Source | What we fetch | Docs |
|---|---|---|
| PubChem PUG REST | CID, molecular formula, weight, InChIKey, SMILES, IUPAC name, synonyms | docs |
| NCBI E-utilities (PubMed) | PMIDs, titles, authors, journal, year, DOIs | docs |
| Europe PMC | Abstracts, open-access URLs, PMC IDs | docs |
| ClinicalTrials.gov API v2 | NCT IDs, status, phase, conditions, sponsor, enrollment | docs |
| UniProt REST | Protein sequences, amino acid counts for endogenous peptides | docs |
How records stay current
Each peptide entry is refreshed from the public databases listed above on a regular cadence by the site's curators. Chemical identifiers come from PubChem and UniProt, peer-reviewed literature is pulled from PubMed and Europe PMC, and trial records come from ClinicalTrials.gov. Placeholder rows on a peptide page indicate that a live search link is shown until a full record has been ingested.
Caching and rate limiting
All importers use Laravel's HTTP client with retries, exponential backoff via Laravel's retry(), and cache responses (PubChem 7 days, PubMed/Europe PMC/ClinicalTrials 24 hours, UniProt 30 days). Each service sleeps between requests to honour the published rate limits — none of the public endpoints we hit require authentication for the volumes we use.