Say you work in compliance at a mid-sized manufacturer. Someone on your team has asked a simple question: can we pull supplier data straight into our systems instead of chasing PDFs and emails? You open apis.io, go to the chemicals industry page, and search for the big names you buy from.
The first number you see is a mismatch. Chemicals on apis.io indexes 110 providers but only 42 APIs. Eighty-eight of the 110 list no API at all. And no provider scores developing or above. The cohort breaks down as 5 thin, 24 emerging, 80 minimal, and one unscored.
You check the producers first, since they are who you actually buy from. Dow, Westlake, Albemarle, Eastman, Celanese, Huntsman, LyondellBasell, PPG, DuPont and Chemours all list zero APIs. All of them except Dow score minimal, and Chemours scores 0.2. Then you notice why. Their scores come from what their websites reveal, not from contracts. Selling chemicals happens over EDI, distributor portals and sales reps, and none of that shows up as a public developer surface. So the empty result does not necessarily mean nothing exists behind the scenes. It means nothing you can see or index.
So who is publishing? You look at the top of the table and find that all four of the highest scores belong to software vendors. Uncountable leads at 36.6 with 2 APIs, in R&D and lab informatics. Knowde, a marketplace and sourcing company, scores 35.4 with 2. Chemius scores 33.1 with 7 APIs, and AspenTech, in process engineering, scores 31.4 with 6. Those four sit above every company that makes a chemical. The highest-scoring manufacturer is Air Products, an industrial gas producer, at 26.7, and it has a single API. Tronox follows at 25.9 with one, and Sherwin-Williams, in coatings, scores 23.7 with two.
The pattern gets clearer when you look at what the industry actually has. It has the safety data sheet. Chemius publishes seven APIs, the most in the cohort, covering SDS, TDS, labels, ADR, PDF, ERP and web shop. SafetyDataSheetAPI, which scores 18.4 with one API, turns SDS PDFs into structured data. For your compliance work, that matters. The regulated document every chemical ships with is the one thing third-party vendors have made programmable. The producers that author those sheets have not.
Here is the part where the catalog turns on itself. The industry page defines chemicals broadly. It covers the producers and the coatings and polymers makers, and also the process-engineering, formulation, SDS-compliance and sourcing software sold into them. That second group is the one publishing APIs. So the headline figure of 110 companies flatters the picture. Some of the roster no longer exists as described. Ferro and Valspar are described in their own entries in the past tense, as companies that were acquired. Both remain in the cohort and count toward the 110, because tag-computed membership keeps a company after it stops trading under that name. The count you are reading includes entries the catalog itself describes as gone.
You now know how to answer your teammate. If the need is SDS and label automation, start with Chemius, then SafetyDataSheetAPI for extraction. For formulation and R&D data, look at Uncountable. For process simulation and optimization, AspenTech has six APIs. If you want to see neighbouring territory, the industrial and energy cohorts are linked from the page.
What you take away is a planning rule rather than a score. Chemicals is a 110-company industry with a 42-API catalog, and almost all of those APIs come from the software layer. If you need programmatic access to a producer, assume it does not exist publicly and plan on a vendor in between.
Read the original: https://apis.io/2026/11/13/chemicals-has-110-providers-and-88-of-them-list-no-api/