Siemens lists 152 APIs on the network. It publishes five machine-readable contracts.
That gap is the entire profile. It scores 46.0, a developing band, with 30.6 on agent readiness — the lowest of this week’s seven.
What the five contracts are
Alarms, Equipment, Points, Schedules, Trends. Five OpenAPI specifications covering building-automation telemetry, and all five are 100% callable as published. Contract quality scores 71.3, the second-highest facet on the card.
The five specs Siemens publishes are good. There are five of them.
What the other 147 are
The remaining entries are descriptive: an Airport Vertical API, an Asset Vertical API, a Baggage Vertical API, and a long tail of similarly-named capability listings, each with a paragraph of prose and no contract behind it.
Read one and the shape is clear — Siemens Baggage Vertical API is a sophisticated software interface that allows airport operators to seamlessly integrate with their baggage handling systems — describing a capability that certainly exists inside a Siemens deployment somewhere, and that no external developer can call, generate a client for, or discover the operations of.
These are not fake. They are product capabilities that appear in a catalog as APIs because that is how Siemens describes them commercially. They are simply not APIs in the sense that anything can consume.
The facets confirm it
| Facet | Score |
|---|---|
| Contract quality | 71.3 |
| Discoverability | 59.3 |
| Governance | 58.3 |
| Developer ergonomics | 30.4 |
| Commercial clarity | 28.9 |
| Operational transparency | 26.3 |
The three high facets measure the five real specs. The three low ones measure what it is like to be a developer trying to use any of this: how you get access, what it costs, whether you can see it running.
Commercial clarity at 28.9 for an enterprise-priced provider with self-serve signup listed is the honest summary — the pricing path exists on paper and does not resolve into anything a developer can act on.
Ten agentic operations
10 operations, 2 acting, 0 human-in-the-loop.
Across a company with 152 listed APIs, the machine-readable surface an agent can actually see is ten operations, of which two change anything.
This is not a criticism of Siemens’ engineering, which runs a meaningful share of the world’s industrial infrastructure. It is a statement about the distance between operating that infrastructure and publishing it. Industrial vendors sell through field engineers, systems integrators and multi-year contracts. Nothing in that model has ever rewarded a public OpenAPI.
Why it matters anyway
The industrial vertical on the network indexes 137 providers publishing 272 APIs — small numbers for the sector that owns physical production. Siemens is the pattern, not the exception.
As industrial operations become things agents are asked to observe and optimise, “we have 152 APIs” and “we publish five contracts” stop being the same claim. The first is a sales sheet. The second is what an agent can reach.
Takeaway
Five callable contracts, 71.3 contract quality on the ones that exist, and 147 capability listings that read like APIs and cannot be called. Siemens describes its surface the way it sells it — and the catalog is where the difference shows up.
See the full profile at apis.io/providers/siemens/.