niche · -1.0 market industry

CAD

Score 17.3 / 100 45 providers +2 via APIs 7 APIs Search apis.io →
Variants seen in the corpus: Computer-Aided DesignCAD

Providers using this tag (45)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Strong 3 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 12 Early or largely undocumented
Minimal 13 Almost no public developer surface

APIs with this tag (7)

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 →

Strong 1 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 3 Limited public surface area
Emerging 1 Early or largely undocumented

Companies reaching this through an API (2)

These companies publish an API, specification or operation carrying “CAD” 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.

NASA Velo3D

Score breakdown

Frequency
46.8
log-scaled weighted occurrences
Breadth
1.0
spread across providers
Quality lift
26.5
mean composite of providers using it
Cohesion
0.0
strength of nearest seed neighbor

Related tags

PLM 10 co-occurrences CAM 5 co-occurrences Engineering 13 co-occurrences BIM 6 co-occurrences Architecture 5 co-occurrences Design 7 co-occurrences 3D Printing 5 co-occurrences Issues 5 co-occurrences

Where this tag comes from

Provider tag46
Api tag7
Openapi tag2
Openapi op tag2

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.

MarketShare of the market's providers
Engineering CAD, CAE and PLM53%

Cohort brief

Auto-generated

The 43 providers in the APIs.io catalog tagged CAD, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
43
of 45 in the catalog
Mean Kin Score
26.4
+4.2 vs catalog 22.2
Mean Agent Readiness
11.4
-0.6 vs catalog 12
Spread
3.4–64.2
median 23.4 · σ 17.6
How the 43 split by band
Exemplar 0Strong 3Developing 8Thin 9Emerging 12Minimal 11
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Access Clarity 34.4 23.9 +10.5 43
Developer Ergonomics 28.4 23.2 +5.2 43
Discoverability 60.9 57.9 +3 43
Operational Transparency 15.1 13 +2.1 43
Contract Quality 18.1 17.2 +0.9 43
Contract Governance 5.1 6.5 -1.4 43

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.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 7% 13% -6
MCP server (first-party) 7% 12% -5
Agent Skills 0% 0% 0
OAuth scopes 23% 11% +12
Security 100% 98% +2
Arazzo workflows 5% 2% +3
Governance rules 19% 16% +3

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.

Top by Kin Score
  1. 1 Bentley Systems 64.2
  2. 2 Autodesk 60.3
  3. 3 Onshape 59.8
  4. 4 Suzanne 54.1
  5. 5 Flock Safety 51.5
  6. 6 3vjia Technology 51.3
  7. 7 Autodesk Construction Cloud 49.1
  8. 8 AutoCAD 47.7
  9. 9 PVcase 44.9
  10. 10 Siemens PLM 44.7
Top by Agent Readiness
  1. 1 Autodesk 43.1
  2. 2 Zamzar 38.4
  3. 3 Flock Safety 36.6
  4. 4 3vjia Technology 36.1
  5. 5 Suzanne 35.5
  6. 6 Onshape 35.1
  7. 7 Autodesk Fusion 33.9
  8. 8 Dassault Systèmes 30.9
  9. 9 Siemens PLM 30.2
  10. 10 Autodesk Construction Cloud 27.6
All 45 members of this roster resolve to a provider in the catalog; 43 carry a score (96%). The figures above describe the scored members only.
Coverage caveat. 38 of 43 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 24 October 2026, across 31984 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.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for tags

7 MCP tools reach this
  • find_tagsBrowse and filter every tag in the catalog.
  • get_cohortThis tag as a scored cohort — every provider carrying it, with scores.
  • cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.
  • cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/cad"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/cad"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/cad/stats" \
  -H "X-API-Key: $APIS_IO_KEY"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.