Leads
Leadsleads
Providers using this tag (89)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 11 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 33 Usable, with meaningful gaps to close
Thin 23 Limited public surface area
Emerging 8 Early or largely undocumented
APIs with this tag (102)
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 13 Complete, well-documented, and agent-ready
Strong 16 Solid coverage with minor gaps
Developing 39 Usable, with meaningful gaps to close
Thin 24 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 89 providers in the APIs.io catalog tagged Leads, 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 | 48.9 | 17.5 | +31.4 | 89 |
| Developer Ergonomics | 43 | 17.9 | +25.1 | 89 |
| Access Clarity | 47.4 | 22.3 | +25.1 | 89 |
| Operational Transparency | 34.2 | 11.3 | +22.9 | 89 |
| Discoverability | 73.6 | 60.4 | +13.2 | 89 |
| Contract Governance | 16.7 | 6.4 | +10.3 | 89 |
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) | 47% | 16% | +31 |
| MCP server (first-party) | 22% | 7% | +15 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 38% | 9% | +29 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 9% | 2% | +7 |
| Governance rules | 27% | 13% | +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 HubSpot 82.4
- 2 Adobe 80.4
- 3 Leadping 72.2
- 4 Vessel 72.1
- 5 Hunter 71.4
- 6 Adobe Suite 71.2
- 7 Microsoft Dynamics 365 Sales 69.9
- 8 Cvent Event Cloud 69.6
- 9 Unbounce 68.7
- 10 lemlist 68.3
- 1 lemlist 63.9
- 2 Instantly 62.7
- 3 Adobe Suite 61.5
- 4 Unbounce 59.6
- 5 HubSpot 54.4
- 6 Hunter 51.7
- 7 Adobe 46.6
- 8 Cvent Event Cloud 46.1
- 9 AlterEstate 44.1
- 10 Alto (Vebra / Zoopla) 44
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/leads"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/leads"
curl "https://apis.io/api/v1/cohorts/tag/leads/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.