Inventory
Inventory ManagementInventory
Providers using this tag (190)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 14 Solid coverage with minor gaps
Developing 25 Usable, with meaningful gaps to close
Thin 53 Limited public surface area
Emerging 54 Early or largely undocumented
Minimal 40 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (215)
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 15 Complete, well-documented, and agent-ready
Strong 28 Solid coverage with minor gaps
Developing 51 Usable, with meaningful gaps to close
Thin 54 Limited public surface area
Emerging 56 Early or largely undocumented
Minimal 11 Almost no public developer surface
Companies reaching this through an API (140)
These companies publish an API, specification or operation carrying “Inventory” 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.
Show all 140 companies ↓
Score breakdown
Where this tag sits
190 providers carry this tag directly, and 214 counting the 2 narrower tags below — 24 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 185 providers in the APIs.io catalog tagged Inventory, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 24.8 | 17.2 | +7.6 | 185 |
| Operational Transparency | 20 | 13 | +7 | 185 |
| Developer Ergonomics | 29.2 | 23.2 | +6 | 185 |
| Discoverability | 63.1 | 57.9 | +5.2 | 185 |
| Access Clarity | 28.9 | 23.9 | +5 | 185 |
| Contract Governance | 6.3 | 6.5 | -0.2 | 185 |
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) | 11% | 13% | -2 |
| MCP server (first-party) | 10% | 12% | -2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 11% | +5 |
| Security | 98% | 98% | 0 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 18% | 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 Lightspeed Commerce 83.9
- 2 Square 78.1
- 3 Virto Commerce 69.9
- 4 Microsoft Dynamics NAV 64.1
- 5 Optoro 61.9
- 6 LeafLink 61.5
- 7 Katana 60.4
- 8 Epsilon3 60.3
- 9 Crunchtime 59.6
- 10 Erply 59.5
- 1 Amazon Selling Partner API 65.5
- 2 Square 62.8
- 3 Newstore 58
- 4 Walmart 57.3
- 5 MarginEdge 56.4
- 6 Kargo 50.9
- 7 Epsilon3 50
- 8 Canix 47.4
- 9 ECI Solutions 45.4
- 10 Apicbase 43.9
Coverage caveat. 161 of 185 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.