niche · -1.7 market domain

SaaS Management

Score 17.7 / 100 38 providers +1 via APIs 20 APIs Search apis.io →

Providers using this tag (38)

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

Strong 2 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
Emerging 12 Early or largely undocumented
Minimal 5 Almost no public developer surface

APIs with this tag (20)

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 1 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 10 Early or largely undocumented
Minimal 1 Almost no public developer surface

Companies reaching this through an API (1)

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

Rippling

Score breakdown

Frequency
47.0
log-scaled weighted occurrences
Breadth
0.9
spread across providers
Quality lift
29.0
mean composite of providers using it
Cohesion
0.0
strength of nearest seed neighbor

Where this tag sits

38 providers carry this tag directly, and 43 counting the 2 narrower tags below — 5 more to reach.

License Management 17 providers Shadow IT 13 providers

Related tags

Shadow IT 13 co-occurrences License Management 13 co-occurrences IT Asset Management 7 co-occurrences Spend Optimization 5 co-occurrences Software Asset Management 5 co-occurrences Spend Management 10 co-occurrences IT Management 5 co-occurrences Cost Optimization 6 co-occurrences

Where this tag comes from

Provider tag38
Api tag20

Cohort brief

Auto-generated

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

Providers
36
of 38 in the catalog
Mean Kin Score
28.8
+6.6 vs catalog 22.2
Mean Agent Readiness
17.9
+5.9 vs catalog 12
Spread
5.7–60
median 29.2 · σ 14.6
How the 36 split by band
Exemplar 0Strong 2Developing 7Thin 12Emerging 12Minimal 3
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Access Clarity 32.3 23.9 +8.4 36
Contract Quality 24.5 17.2 +7.3 36
Discoverability 63.5 57.9 +5.6 36
Operational Transparency 18.1 13 +5.1 36
Contract Governance 11 6.5 +4.5 36
Developer Ergonomics 26.8 23.2 +3.6 36

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) 19% 13% +6
MCP server (first-party) 22% 12% +10
Agent Skills 0% 0% 0
OAuth scopes 17% 11% +6
Security 97% 98% -1
Arazzo workflows 0% 2% -2
Governance rules 33% 16% +17

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 Cledara 60
  2. 2 Lumos 54.5
  3. 3 Axonius 49.9
  4. 4 Torii 48.6
  5. 5 Zluri 46.4
  6. 6 Augmentt 44.2
  7. 7 G2 Track 43.9
  8. 8 Zylo 43.1
  9. 9 Cakewalk 41.5
  10. 10 Tropic 38.8
Top by Agent Readiness
  1. 1 Lumos 60.3
  2. 2 Cakewalk 50.9
  3. 3 Cledara 49.3
  4. 4 Snow Software 48.6
  5. 5 Zylo 36
  6. 6 ZenAdmin 33.1
  7. 7 Augmentt 31.4
  8. 8 LeanIX 31.2
  9. 9 BetterCloud 30.9
  10. 10 Torii 28.8
All 38 members of this roster resolve to a provider in the catalog; 36 carry a score (95%). The figures above describe the scored members only.
Coverage caveat. 30 of 36 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/saas-management"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/saas-management"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/saas-management/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.