Inventory
Inventory ManagementInventory
Providers using this tag (186)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 31 Usable, with meaningful gaps to close
Thin 56 Limited public surface area
Emerging 48 Early or largely undocumented
Minimal 35 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (209)
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 17 Complete, well-documented, and agent-ready
Strong 22 Solid coverage with minor gaps
Developing 56 Usable, with meaningful gaps to close
Thin 58 Limited public surface area
Emerging 53 Early or largely undocumented
Minimal 3 Almost no public developer surface
Companies reaching this through an API (131)
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 131 companies ↓
Score breakdown
Where this tag sits
186 providers carry this tag directly, and 210 counting the 2 narrower tags below — 24 more to reach.
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 181 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 |
|---|---|---|---|---|
| Operational Transparency | 22.6 | 13.7 | +8.9 | 181 |
| Access Clarity | 34.9 | 26.5 | +8.4 | 181 |
| Contract Quality | 24.5 | 17.6 | +6.9 | 181 |
| Developer Ergonomics | 29.5 | 23.2 | +6.3 | 181 |
| Discoverability | 62.7 | 58.1 | +4.6 | 181 |
| Contract Governance | 5.9 | 6.3 | -0.4 | 181 |
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) | 12% | 14% | -2 |
| MCP server (first-party) | 11% | 12% | -1 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 17% | 11% | +6 |
| Security | 98% | 98% | 0 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 15% | 14% | +1 |
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 78.8
- 2 Square 75.4
- 3 Virto Commerce 71.4
- 4 Commerce Layer 65.1
- 5 Benchling 64.5
- 6 Microsoft Dynamics NAV 63.7
- 7 Optoro 61.8
- 8 LeafLink 61
- 9 Walmart 60.9
- 10 Katana 60.4
- 1 Amazon Selling Partner API 64.6
- 2 Square 60.6
- 3 Newstore 59.2
- 4 Walmart 58.5
- 5 MarginEdge 57.5
- 6 Epsilon3 50
- 7 Canix 46.2
- 8 RELEX Solutions 45.5
- 9 ECI Solutions 45.1
- 10 Apicbase 44.6
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.