Home › Peptides › Knowledge Base › Data export
The Peptide Knowledge Base, as data
Every record we publish, in JSON and CSV, free to reuse with attribution. If you want to cite what a peptide is, what the evidence shows, what the FDA rule says today, and whether a patient can actually get it — take the file rather than the page.
What this is
A reference record per molecule. Each one carries a plain-English description, the mechanism, what it does and what it does not do, the documented unknowns, drug class, who should not take it, WADA status, sources, an evidence grade — and two separate status signals. It is the same record that renders the monograph pages, generated from it at build time, so the file and the page cannot disagree.
What this is not
- Not a protocol. There is no dose, range, ratio, frequency, titration or reconstitution field in either format. Not omitted from this page — absent from the data.
- Not a product catalogue. No price, no offer, nothing transactable. A record's presence here says nothing about whether we supply it.
- Not medical advice, and not a substitute for a clinician who knows your history.
- Not an FDA approval list. Compounded medications are not FDA-approved. A PCAC recommendation is advisory: it leads to rulemaking, not to authorization to compound, and not to availability.
Two signals. Never merge them.
regulatory_status is what the FDA rule currently says about the molecule. availability_verdict is whether a patient can actually obtain it today. They are independent: a molecule can be legally compoundable and unavailable, or removed from a restricted category and still unavailable, and neither value is ever derived from the other.
They are separate keys in the JSON and separate columns in the CSV, deliberately. Collapsing them into a single status field misrepresents the data — it asserts that the rule and the access are one fact, which is the most consequential error available in this category. If your schema has one status column, use two, or use regulatory_status alone and say so.
Field dictionary
Column order below is the CSV's column order. Inside a CSV cell, list values are separated by semicolons.
| Field | Type | What it holds |
|---|---|---|
| slug | string | Stable identifier. Also the last segment of the monograph URL. |
| name | string | The molecule's display name. |
| record_type | string | monograph or regulatory_only. See "The regulatory-only records" below. |
| common_names | list | Other names it is sold or discussed under. Empty where none are recorded — never inferred. |
| class | string | Drug or compound class. |
| mechanism_family | string | Its role in a mechanism family (anchor, companion, bridge, escalation). |
| mechanism | string | How it works, in plain language. |
| what_it_does | string | What the evidence supports. Prose, not a claim list. |
| what_it_does_not_do | string | The limits, stated explicitly. Read this before quoting the row. |
| who_should_not | string | Contraindications and populations who should not take it. The record holds one field for this; it is not duplicated under a second name. |
| known_unknowns | string · null | What is still genuinely unresolved. null where none has been written — never a fabricated sentence. |
| evidence_grade | string · null | A to E, human evidence only. One field in the record, not the record's purpose. Method: how we grade. |
| evidence_grade_rationale | string · null | Why that grade. null rather than an invented justification. |
| regulatory_status | string · null | Signal 1. What the FDA rule says today. null means no regulatory record exists — not "unrestricted". |
| availability_verdict | string · null | Signal 2. Whether a patient can obtain it: green available, amber not available today, red education only. null means no availability record — never read as red. |
| wada_status | string | World Anti-Doping Agency status, for competing athletes. |
| approved_product_reference | string · key omitted | The branded FDA-approved product, where one is recorded. The key is omitted entirely where none is recorded — never null, never empty. An empty value would read as "no approved product exists", which for several molecules is false. In the CSV an empty cell means NOT RECORDED, not "none exists"; the JSON is authoritative for this field. |
| sources | list | Citations the record is read from. |
| monograph_url | string | Canonical URL of the human page. Monograph records only. |
| tracker_url | string | Canonical URL on the FDA Tracker. Regulatory-only records only. |
| last_reviewed | date | ISO date this record was last reviewed. Per record, not a site-wide stamp. |
| compounding_status | string | Present on every record: "Compounded medications are not FDA-approved." |
The regulatory-only records
Five records carry record_type: "regulatory_only". They have a regulatory record and no monograph — we track the rule but have not published an explanation. They are included because dropping them would remove the only machine record of their status, and they carry no editorial fields at all: no mechanism, no what-it-does, no grade. Not empty strings, not nulls. If a molecule is not explained, this export does not pretend otherwise.
Licence
Free to use, including commercially, under CC BY 4.0. Attribute Peptós.LIFE and link to the Knowledge Base. No key, no rate limit, no registration. If you build something with it we would like to see it, but you owe us nothing beyond the attribution.
Attribution string, copy and paste:
Peptós.LIFE Peptide Knowledge Base. CC BY 4.0. https://peptos.life/knowledge-baseCiting a single molecule
Every monograph carries its own "Cite this page" block with a per-page string and its review date. Cite the specific page rather than the whole base when you are making a claim about one molecule — the review dates differ per record, and the page states which one applies.
Staying current
Both files regenerate on every deploy from the same record the pages render. generated_at is the newest per-record review date in the export, not a build clock — so an unchanged date means nothing was reviewed, not that the build did not run. For regulatory movement specifically, the FDA Tracker is the live surface and has its own dataset at /fda-tracker.json.
The Peptide Knowledge Base · How we grade · FDA Tracker · How we medically review · Embed a molecule card
Not medical advice. Compounded medications are not FDA-approved.