Group
GroupGroupsgroupgroups
Providers using this tag (359)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 12 Complete, well-documented, and agent-ready
Strong 71 Solid coverage with minor gaps
Developing 143 Usable, with meaningful gaps to close
Thin 111 Limited public surface area
Emerging 22 Early or largely undocumented
APIs with this tag (376)
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 12 Complete, well-documented, and agent-ready
Strong 76 Solid coverage with minor gaps
Developing 149 Usable, with meaningful gaps to close
Thin 115 Limited public surface area
Emerging 24 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 359 providers in the APIs.io catalog tagged Group, 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 | 56.5 | 17.5 | +39 | 359 |
| Developer Ergonomics | 41.8 | 17.9 | +23.9 | 359 |
| Access Clarity | 41.6 | 22.3 | +19.3 | 359 |
| Operational Transparency | 29.3 | 11.3 | +18 | 359 |
| Discoverability | 71.8 | 60.4 | +11.4 | 359 |
| Contract Governance | 16.7 | 6.4 | +10.3 | 359 |
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) | 37% | 16% | +21 |
| MCP server (first-party) | 12% | 7% | +5 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 34% | 9% | +25 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 16% | 2% | +14 |
| Governance rules | 50% | 13% | +37 |
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 Customer.io 87.3
- 2 Centers for Medicare and Medicaid Services 85.2
- 3 Salesforce 83.3
- 4 HubSpot 82.4
- 5 Stannp 78.5
- 6 MailerLite 77.2
- 7 Dynatrace 71.8
- 8 Agorapulse 71.4
- 9 BlueConic 68.8
- 10 Bitly 68
- 1 OpenGov 63.1
- 2 Coda Project 55.5
- 3 Genesys 55.1
- 4 Frame.io 54.9
- 5 Lytx 54.5
- 6 HubSpot 54.4
- 7 Factset 52.8
- 8 Red Hat 52.3
- 9 Salesforce 52.2
- 10 ModMed 52
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/group"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/group"
curl "https://apis.io/api/v1/cohorts/tag/group/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.