Contacts
Providers using this tag (54)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 15 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
APIs with this tag (327)
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 44 Complete, well-documented, and agent-ready
Strong 75 Solid coverage with minor gaps
Developing 103 Usable, with meaningful gaps to close
Thin 71 Limited public surface area
Emerging 29 Early or largely undocumented
Minimal 5 Almost no public developer surface
Companies reaching this through an API (275)
These companies publish an API, specification or operation carrying “Contacts” 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 275 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 49 providers in the APIs.io catalog tagged Contacts, 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 | 49 | 17.2 | +31.8 | 49 |
| Access Clarity | 49 | 23.9 | +25.1 | 49 |
| Operational Transparency | 37.7 | 13 | +24.7 | 49 |
| Developer Ergonomics | 47.3 | 23.2 | +24.1 | 49 |
| Discoverability | 68.9 | 57.9 | +11 | 49 |
| Contract Governance | 12 | 6.5 | +5.5 | 49 |
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) | 45% | 13% | +32 |
| MCP server (first-party) | 43% | 12% | +31 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 33% | 11% | +22 |
| Security | 98% | 98% | 0 |
| Arazzo workflows | 10% | 2% | +8 |
| Governance rules | 39% | 16% | +23 |
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 Nylas 87.5
- 2 ZoomInfo 86.6
- 3 Brevo 80.8
- 4 GetResponse 72.1
- 5 Cvent Event Cloud 70.9
- 6 Constant Contact 68
- 7 Microsoft Outlook 65.9
- 8 Relm 64.6
- 9 Keap 64.4
- 10 Benchmark Email 63.5
- 1 ZoomInfo 64.3
- 2 Relm 62.6
- 3 Monaco 61.4
- 4 Nylas 57.2
- 5 Brevo 57.2
- 6 Folk 53.2
- 7 Kajabi 53
- 8 Spruce Health 49.5
- 9 GetResponse 48.9
- 10 Actionstep 48.9
Coverage caveat. 26 of 49 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.