Amino Axiom is a free research information platform in the same network as Amino Foundry. Its compound library is a structured reference covering 79 research compounds, with each entry organized around sourced mechanism, structure and regulatory-status sections. The library is available at the Amino Axiom compound library, and it works as a lookup layer: a place to confirm what a compound is, what a compound is reported to act on, and how it is classified, before any bench work is planned.
For mechanism research the useful property is consistency. Each entry follows the same layout, so a researcher comparing two compounds is comparing like with like instead of reconciling two differently structured sources. That consistency is what this walkthrough focuses on.
How is a compound entry organized?
An entry is built from a small number of repeating blocks. The identity block lists the compound name, aliases, and class. The structure block describes the molecule: whether it is a short linear peptide, a cyclic or modified peptide, a small molecule, or a nucleotide cofactor, and what that implies for its chemistry. The mechanism block summarizes the biological targets or pathways the published literature associates with the compound. The regulatory block records how the compound is classified in the jurisdictions the library tracks.
Reading these blocks in order is a reasonable habit. Identity first, because naming confusion is common in this field and a single compound can circulate under several names. Structure second, because structure constrains what mechanisms are plausible. Mechanism third, with attention to how each statement is sourced. Regulatory status last, because it determines what kinds of laboratory work and sourcing a project can rely on.
How should a researcher read the mechanism section?
The mechanism section is a summary of published findings, not a verdict. A careful reader separates three kinds of statements: what a compound binds or interacts with in vitro, what pathway activity is reported in cell or animal models, and what is only hypothesized. Entries that cite sources for each statement make this separation easier, and the library's sourced format is built for it.
A practical reading routine is to extract each claim, note the model system behind it, and note whether the finding is a direct measurement or an inference. A receptor-binding result in a purified system carries different weight than a pathway readout in whole tissue. Treating those as separate rows in a personal notes table keeps downstream experimental design honest.
Two worked examples from the Amino Foundry catalog show how this plays out.
What does a small-molecule cofactor entry look like?
NAD+ is a useful first example because it is not a peptide at all. It is a dinucleotide cofactor with the molecular formula C21H27N7O14P2 and a molecular weight of 663.43 g/mol (anhydrous free acid), catalogued under CAS 53-84-9. A library entry for a molecule like this would reasonably place its structure block around the nicotinamide and adenine moieties linked through a pyrophosphate bridge, and its mechanism block around its role as a redox cofactor and as a substrate for several enzyme families.
The lesson for a mechanism researcher is that the library's entries are not limited to a single molecular class. Reading the structure block first tells you immediately whether the compound should be handled in a peptide-receptor framework or an enzymology framework. Applying a receptor-agonist mindset to a cofactor would send a project in the wrong direction, and the structure block is where that mismatch becomes visible early.
What does a short-peptide entry look like?
BPC-157 is a contrasting example. It is a synthetic pentadecapeptide with the formula C62H98N16O22, a molecular weight of 1419.56 g/mol and CAS 137525-51-0 in the Amino Foundry catalog. Its mechanism literature is largely preclinical, which is itself an important property for a reader to register. A sourced entry lets a researcher see at a glance how much of the mechanism section rests on animal and cell models versus other evidence.
Comparing the NAD+ entry and the BPC-157 entry side by side shows the library's value for mechanism work. The two compounds differ in class, size, chemistry and the kind of evidence behind their mechanism sections. A reader who goes through both blocks in order ends up with a clear picture of which experimental frameworks are appropriate for each, and which are not.
How can the library help with comparing two compounds?
When a project needs to choose between two candidate compounds, the library's uniform layout supports a structured comparison. A simple method is to build a four-column table, one column per block, and fill it for each candidate: identity, structure, mechanism, regulatory status. Differences in structure often explain differences in reported mechanism. A larger molecule with multiple modifications has a different stability and handling profile in a laboratory setting than a short linear sequence, and the structure block makes that visible.
A third catalog compound, MOTS-c, illustrates the point. MOTS-c is a mitochondrial-derived peptide with formula C100H152N28O22S2, molecular weight 2174.59 g/mol and CAS 1627580-64-6 in the catalog. Its origin in the mitochondrial genome is a structural and biological distinction that a comparison table would flag immediately next to a nuclear-encoded peptide or a small-molecule cofactor.
How does the library connect to sourcing and verification?
The library describes compounds; it does not verify a particular batch. Verification is a separate step and belongs to analytical documentation. When a project moves from literature review to bench work, the identity facts recorded in the library, such as the molecular weight and formula, become the targets that a Certificate of Analysis should be checked against. For guidance on that step, see the Amino Foundry article on how to read a Certificate of Analysis.
This division of labor is worth keeping explicit. A reference library answers what a compound is and what the literature reports. Analytical documentation answers whether a specific lot matches that description. Mixing the two leads to errors such as assuming a lot is correct because the reference entry is.
What are the limits of using a reference library?
A library entry is a summary and inherits the limits of summaries. It compresses a body of literature into a few paragraphs, so nuance about model systems, concentrations in vitro and conflicting results can be lost. The sourced format mitigates this by pointing back to underlying work, and a researcher should follow those sources for any claim that drives a design decision.
The library also does not replace a project's own review of primary literature, and it makes no claims beyond what each entry shows. It is best used as a first-pass orientation tool and as a consistent place to record how a compound is classified, with the primary sources doing the evidentiary work. Researchers who want to look at the broader network can start from the Amino Axiom homepage, and those who want to review Amino Foundry's own catalog can browse all compounds.
This article is for informational and laboratory research purposes only. The compounds discussed are research chemicals, not drugs, supplements, or food, and are not intended for human consumption. Amino Foundry does not sell products intended for human use. Researchers are responsible for compliance with all applicable local, state, and federal regulations.
Stay in the loop
New compounds, research updates & exclusive subscriber deals.
