Document-Management
Document ManagementDocument-Management
Providers using this tag (58)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 14 Early or largely undocumented
Minimal 7 Almost no public developer surface
APIs with this tag (22)
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 4 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 2 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (15)
These companies publish an API, specification or operation carrying “Document-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
Cohort brief
Auto-generatedThe 55 providers in the APIs.io catalog tagged Document-Management, 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 | 33.3 | 19.8 | +13.5 | 55 |
| Access Clarity | 37.3 | 26.5 | +10.8 | 55 |
| Developer Ergonomics | 31.4 | 23.4 | +8 | 55 |
| Operational Transparency | 20.6 | 14 | +6.6 | 55 |
| Contract Governance | 11.3 | 6.4 | +4.9 | 55 |
| Discoverability | 64.4 | 61.2 | +3.2 | 55 |
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) | 16% | 10% | +6 |
| MCP server (first-party) | 19% | 13% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 21% | 11% | +10 |
| Security | 96% | 97% | -1 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 28% | 14% | +14 |
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 Veeva 75.6
- 2 La Poste Groupe 64.5
- 3 GetAccept 62
- 4 LawVu 57
- 5 Nitro Software 54.6
- 6 DocuSeal 52.6
- 7 Zinnia 48.5
- 8 Inkit 48.4
- 9 Microsoft SharePoint 48
- 10 Zoho Sign 46.9
- 1 Sadq Holding Limited 50.3
- 2 LawVu 49.3
- 3 Hubflo 44.4
- 4 Veeva 41.5
- 5 Zinnia 39.7
- 6 Google Drive 39.6
- 7 DocuSeal 37.8
- 8 Bitrix24 36.6
- 9 BoldSign 35.9
- 10 SignNow 35.9
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.