The vendor directory is a section of Amino Axiom, a free research information platform, that lists suppliers of research compounds as individual profiles. Each profile collects a small set of visible attributes in one place: the payment rails a vendor accepts, how many compounds the vendor lists, and a rating. The directory lives at the Amino Axiom vendor directory.
For a researcher working through supplier vetting, the value is organizational. Supplier information is normally scattered across storefronts, forums and ad hoc notes. A directory puts the same fields next to each other for every vendor, so comparison becomes a matter of reading columns rather than reconstructing a spreadsheet from memory. This FAQ walks through what those fields show and how a person in a sourcing role would read them. It describes what the feature displays and nothing beyond that.
What does a vendor profile show?
Three things are visible on a profile, and each answers a different question.
Payment rails answer a logistics question: which payment methods does this vendor accept. Rails matter for sourcing because they constrain which vendors are practical for a given institution or budget process, and because a narrow set of rails can limit how a refund or dispute is handled later.
Compound count answers a catalog question: how many compounds does this vendor list. A count is a measure of breadth only. It says nothing about the quality of any individual listing.
Ratings answer a reputational question: how has this vendor been scored. A rating is an aggregate, and an aggregate hides the distribution behind it. A rating built from a handful of scores is a weaker signal than one built from many, and a researcher reading it should look for how much underlying data sits behind the number whenever the directory exposes that.
How should compound counts be read?
A large catalog is not evidence of depth, and a small catalog is not evidence of weakness. Counts are most useful as a filter in one direction: they identify vendors who list a compound a researcher needs at all. A vendor with four hundred listings may carry a compound only as a rarely stocked item, while a vendor with forty listings may focus on a narrow lane and document it well.
A more informative use is to take one compound and ask which vendors list it. Consider BPC-157, a 15-residue synthetic peptide. Onward Aminos lists it with CAS 137525-51-0, molecular weight 1419.56 g/mol and formula C62H98N16O22. Those three identifiers are the reference a researcher can hold any vendor's listing against. If a listing for the same compound shows a different molecular weight or formula, that discrepancy is a question to resolve before anything else about the vendor matters. The directory narrows the field of vendors to examine, and the identifiers then test each listing.
What does a rating not tell a researcher?
A rating does not verify analytical quality. It cannot confirm that a specific batch met its stated purity, that identity was confirmed by mass spectrometry, or that the certificate of analysis corresponds to the material that shipped. Those are batch-level facts, and a vendor-level score is too coarse an instrument to carry them.
Supplier vetting therefore has two layers. The first layer is vendor-level screening, where the directory is useful: rails, breadth, and the reputational signal. The second layer is batch-level verification, where documentation is the evidence. Our guide to COA recordkeeping covers how to retain and organize that documentation, and the explanation of HPLC purity testing covers what a chromatographic purity figure does and does not establish.
A high rating combined with a missing or vague certificate of analysis is a mixed signal, and the missing documentation should weigh more. A modest rating combined with complete, batch-specific documentation deserves a closer look rather than a dismissal. The two layers answer different questions and should not be traded against each other.
How does a payment-rail field figure in vetting?
Rails are easy to overlook and worth reading carefully. Three points apply to a research sourcing workflow.
First, rails shape traceability. A payment method that produces a clear record supports the paper trail a lab needs for its own recordkeeping, and that record is part of showing where material came from.
Second, rails shape reversibility. Some methods allow a dispute process and others do not. A vendor whose only accepted rail is irreversible places all the verification burden before payment, which argues for confirming documentation first.
Third, rails shape institutional fit. A researcher purchasing through an institution may be limited to specific methods, and the rails field lets that person exclude incompatible vendors immediately instead of discovering the mismatch at checkout.
None of this is a judgment about any rail. The point is that the field is a screening input, and it is most useful when a researcher has already written down which constraints apply to the purchase.
How can the directory be used to compare two vendors for one compound?
A worked comparison keeps the process concrete. Take Selank, listed by Onward Aminos with CAS 129954-34-3, molecular weight 751.86 g/mol and formula C33H57N9O15. A researcher wanting to source Selank could proceed in this order.
Use the directory to identify which vendors list the compound.
Read the profile fields for each: rails, breadth, rating.
Eliminate vendors whose rails do not fit the purchasing constraints.
Request or locate the batch documentation for each remaining vendor.
Compare the documented identifiers against the reference values above.
Record the outcome, including the rejected vendors and the reason.
Steps one through three are where a directory saves time. Steps four through six are the actual vetting, and they happen outside any directory. Writing down the rejected vendors matters more than it sounds: a sourcing decision that cannot be reconstructed later is hard to defend or repeat.
The same sequence works for TB500 or any other compound with published identifiers. The structure of the comparison does not change with the compound, which is why a fixed checklist is more reliable than case-by-case judgment.
What are the limits of a directory-based approach?
Three limits are worth stating plainly.
A directory reflects what it has been given. Profiles can lag behind a vendor's actual current catalog or accepted methods, so any field that drives a decision should be confirmed with the vendor directly before relying on it.
A directory is not an audit. Listing a vendor, rating a vendor and inspecting a vendor's facility are three different activities, and only the third speaks to manufacturing practice. The directory performs the first two functions as a visible display, and a researcher should not read more into it than that.
A directory does not replace the researcher's own acceptance criteria. Each project has its own tolerance for impurity, its own identity requirements and its own documentation standard. The directory can shorten the list of candidates, but the criteria belong to the project.
Amino Axiom describes itself as a research information and tracking platform, and its vendor directory should be treated in that spirit: a place to organize screening information, with verification still resting on batch documentation and on the researcher's own records. The platform's homepage is at Amino Axiom for readers who want the wider context of the site.
Summary
The vendor directory shows three visible fields per profile: payment rails, compound count and rating. Each supports a different part of supplier screening, and none of them verifies the analytical quality of a batch. The reliable pattern is to screen at the vendor level, then verify at the batch level against published identifiers, then record the reasoning. Used that way, a directory shortens the early work and leaves the evidence-gathering where it belongs, with the documentation.
This article is provided for informational and laboratory research purposes only. The compounds discussed are research chemicals intended for in vitro and laboratory use. They are not drugs, supplements or food, and are not intended to diagnose, treat, cure or prevent any disease. Onward Aminos does not sell products intended for human use. Researchers are responsible for compliance with all applicable local, state and federal regulations. Amino Axiom is an independent research information platform. For research purposes only.
Stay in the loop
New compounds, research updates & exclusive subscriber deals.
Skip to main content
