Machine readable

The catalog, as data

Every compound, every variant, every documented lot and every measured purity figure, published as plain JSON at a stable URL. No API key, no signup, no rate limit, no scraping required. If you want to pull our lot records into your own inventory system or check a purity figure programmatically, the data is already there.

Endpoints

Four files, all public

Static JSON, regenerated whenever the catalog changes. Each file is self-describing: it carries its own name, description, licence and research-use notice, so a consumer who finds one in isolation still knows what it is.

Shape

What a record looks like

Live excerpts, pulled from the actual endpoints when this page loads. If they render, the endpoints work.

A catalog product 
Loading...
A lot record 
Loading...
Using it

Worked examples

Check a lot's purity from the command line

curl -s https://exactamino.com/api/lots.json \
  | jq '.lots[] | select(.lot=="YPB.243")'

List every compound with more than two documented lots

curl -s https://exactamino.com/api/catalog.json \
  | jq '.products[] | select(.documentation.lots_on_file > 2) | .name'

Subscribe to new lot releases

https://exactamino.com/feed.xml

RSS 2.0, the forty most recent lots, each linking to its verification page. Add it to any reader.

Add the catalog to your browser's search bar

https://exactamino.com/opensearch.xml

An OpenSearch descriptor. Most browsers offer to add it automatically after a visit.

You may

  • Pull the endpoints into inventory, procurement or lab-management software.
  • Cite a documented purity figure, with the lot number and date attached.
  • Mirror or cache the data, provided the research-use notice travels with it.
  • Build comparison or verification tooling on top of it.

You may not

  • Present a purity figure as applying to any lot other than the one stated.
  • Republish the data stripped of its research-use framing.
  • Represent these analytical records as safety or efficacy evidence.
  • Use the data to imply an endorsement or a supply relationship that does not exist.
Why publish this at all. A supplier that keeps its lot records behind a contact form is asking to be taken on trust. Ours are a static file anyone can diff against last month's. That is a harder promise to make and a much harder one to fake, which is precisely the point. Full terms on the terms page.
catalog.json lots.json RSS feed Verify a lot