Providers using this tag (25)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 9 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 5 Usable, with meaningful gaps to close
Emerging 1 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (8)
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 3 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 1 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Emerging 1 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 25 providers in the APIs.io catalog tagged SMTP, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 61.4 | 22.3 | +39.1 | 25 |
| Contract Quality | 55.4 | 17.5 | +37.9 | 25 |
| Developer Ergonomics | 53.1 | 17.9 | +35.2 | 25 |
| Operational Transparency | 40.2 | 11.3 | +28.9 | 25 |
| Contract Governance | 21.6 | 6.4 | +15.2 | 25 |
| Discoverability | 75.5 | 60.4 | +15.1 | 25 |
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) | 52% | 16% | +36 |
| MCP server (first-party) | 40% | 7% | +33 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 9% | +7 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 8% | 2% | +6 |
| Governance rules | 48% | 13% | +35 |
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 Amazon SES 79.7
- 3 SendGrid 77
- 4 SendPulse 75.7
- 5 SMTP2GO 73.6
- 6 Mailboxlayer 73.4
- 7 Postmark 71.1
- 8 Mailosaur 71
- 9 Moosend 67.9
- 10 MailerSend 64.6
- 1 SendPulse 55.8
- 2 HubSpot 54.4
- 3 MailerSend 50.2
- 4 AgentMail 45.7
- 5 Amazon SES 41.6
- 6 SendGrid 41.2
- 7 SMTP2GO 39.4
- 8 Postmark 38.7
- 9 Smartlead 38
- 10 uChecker 36.7
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/smtp"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/smtp"
curl "https://apis.io/api/v1/cohorts/tag/smtp/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.