Asset Management
Providers using this tag (159)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 19 Usable, with meaningful gaps to close
Thin 25 Limited public surface area
Emerging 54 Early or largely undocumented
Minimal 54 Almost no public developer surface
APIs with this tag (46)
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 →
Exemplar 1 Complete, well-documented, and agent-ready
Strong 6 Solid coverage with minor gaps
Developing 10 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 11 Early or largely undocumented
Minimal 4 Almost no public developer surface
Companies reaching this through an API (20)
These companies publish an API, specification or operation carrying “Asset 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.
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 |
|---|---|
| Asset and Wealth Management | 34% |
Cohort brief
Auto-generatedThe 155 providers in the APIs.io catalog tagged Asset Management, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 26.8 | 23.9 | +2.9 | 155 |
| Discoverability | 59.1 | 57.9 | +1.2 | 155 |
| Contract Governance | 6.8 | 6.5 | +0.3 | 155 |
| Operational Transparency | 10.6 | 13 | -2.4 | 155 |
| Developer Ergonomics | 20.7 | 23.2 | -2.5 | 155 |
| Contract Quality | 14.1 | 17.2 | -3.1 | 155 |
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) | 9% | 13% | -4 |
| MCP server (first-party) | 6% | 12% | -6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 11% | +3 |
| Security | 99% | 98% | +1 |
| Arazzo workflows | 1% | 2% | -1 |
| Governance rules | 14% | 16% | -2 |
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 Limble CMMS 75.5
- 2 Bentley Systems 64.2
- 3 SewerAI 64
- 4 Facilio 57.1
- 5 Accruent 56.1
- 6 MaintainX 56
- 7 Amazon IoT SiteWise 55.4
- 8 73 Strings 53.1
- 9 Decisiv 52.2
- 10 Atomicwork 51.3
- 1 OpenGov 61.3
- 2 Facilio 50.9
- 3 Decisiv 46.4
- 4 Limble CMMS 45.1
- 5 Cloudinary 45
- 6 Freshservice 43.3
- 7 Accela 39.9
- 8 VTS 37.9
- 9 allwhere 36.7
- 10 ServiceChannel 35.9
Coverage caveat. 140 of 155 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.