Engineering
Providers using this tag (163)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Developing 12 Usable, with meaningful gaps to close
Thin 17 Limited public surface area
Emerging 53 Early or largely undocumented
Minimal 75 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (8)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Thin 3 Limited public surface area
Emerging 2 Early or largely undocumented
Minimal 3 Almost no public developer surface
Companies reaching this through an API (5)
These companies publish an API, specification or operation carrying “Engineering” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Markets provisional
Kin Score markets whose measured providers carry this tag. Share is the fraction of the market's measured providers that carry it — it describes the market, not this tag.
| Market | Share of the market's providers |
|---|---|
| Engineering CAD, CAE and PLM | 34% |
Cohort brief
Auto-generatedThe 131 providers in the APIs.io catalog tagged Engineering, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Discoverability | 56.4 | 59.1 | -2.7 | 131 |
| Contract Governance | 6.6 | 9.7 | -3.1 | 131 |
| Operational Transparency | 9.5 | 13.2 | -3.7 | 131 |
| Access Clarity | 24.7 | 30 | -5.3 | 131 |
| Developer Ergonomics | 18.2 | 24.5 | -6.3 | 131 |
| Contract Quality | 11.1 | 18.6 | -7.5 | 131 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 10% | 18% | -8 |
| MCP server (first-party) | 8% | 16% | -8 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 13% | +1 |
| Security | 98% | 99% | -1 |
| Arazzo workflows | 1% | 1% | 0 |
| Governance rules | 24% | 36% | -12 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Autodesk 72.9
- 2 Autodesk Construction Cloud 69
- 3 MATLAB 68.8
- 4 ARCNM 63.7
- 5 Onshape 62.7
- 6 Cogram 50.3
- 7 Violetlabs 49
- 8 Ask Marcel 48.3
- 9 Delft University of Technology 47.8
- 10 Acrux Core 46.9
- 1 ADRO 49.6
- 2 Autodesk 46.9
- 3 ARCNM 46.6
- 4 Autodesk Construction Cloud 41.2
- 5 Ask Marcel 40.7
- 6 SLB 38.1
- 7 Onshape 35.1
- 8 Newforma 34.1
- 9 HVAC Builder 33.9
- 10 APIs.io Engineering Platform 33.6
Coverage caveat. 116 of 131 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.