Collaboration
Providers using this tag (236)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 11 Complete, well-documented, and agent-ready
Strong 22 Solid coverage with minor gaps
Developing 48 Usable, with meaningful gaps to close
Thin 45 Limited public surface area
Emerging 49 Early or largely undocumented
Minimal 59 Almost no public developer surface
Unrated 2 Not yet scored
APIs with this tag (74)
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 11 Complete, well-documented, and agent-ready
Strong 16 Solid coverage with minor gaps
Developing 27 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 13 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (32)
These companies publish an API, specification or operation carrying “Collaboration” 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 209 providers in the APIs.io catalog tagged Collaboration, 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 | 29.7 | 17.6 | +12.1 | 209 |
| Developer Ergonomics | 34.9 | 23.2 | +11.7 | 209 |
| Access Clarity | 36.2 | 26.5 | +9.7 | 209 |
| Operational Transparency | 21.8 | 13.7 | +8.1 | 209 |
| Discoverability | 61.9 | 58.1 | +3.8 | 209 |
| Contract Governance | 9.5 | 6.3 | +3.2 | 209 |
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) | 29% | 14% | +15 |
| MCP server (first-party) | 26% | 12% | +14 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 29% | 11% | +18 |
| Security | 97% | 98% | -1 |
| Arazzo workflows | 10% | 2% | +8 |
| Governance rules | 30% | 14% | +16 |
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 Postman 79.6
- 2 Atlassian 75.1
- 3 Trello 74.8
- 4 Fireflies.ai 72.6
- 5 Clickup 71.9
- 6 Canva 70.5
- 7 Adobe Workfront 70.3
- 8 Confluence 70.1
- 9 Asana 69.7
- 10 Slack 67.9
- 1 Taskfolk 69.2
- 2 Webex 67.4
- 3 Canva 63.3
- 4 Adobe Workfront 60.8
- 5 Fireflies.ai 60.4
- 6 Clickup 60.3
- 7 Box 58.6
- 8 Outline 57.8
- 9 data.world 56
- 10 Postman 54.9
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.