Transactional Email
Providers using this tag (36)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 16 Complete, well-documented, and agent-ready
Strong 9 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
APIs with this tag (9)
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 2 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Companies reaching this through an API (4)
These companies publish an API, specification or operation carrying “Transactional Email” 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
Where this tag sits
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 36 providers in the APIs.io catalog tagged Transactional Email, 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 | 74.9 | 26.5 | +48.4 | 36 |
| Operational Transparency | 57 | 13.7 | +43.3 | 36 |
| Developer Ergonomics | 63.2 | 23.2 | +40 | 36 |
| Contract Quality | 57.2 | 17.6 | +39.6 | 36 |
| Discoverability | 72 | 58.1 | +13.9 | 36 |
| Contract Governance | 16.3 | 6.3 | +10 | 36 |
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) | 53% | 14% | +39 |
| MCP server (first-party) | 53% | 12% | +41 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 33% | 11% | +22 |
| Security | 97% | 98% | -1 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 39% | 14% | +25 |
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 AhaSend 84.3
- 2 Customer.io 83.8
- 3 SendGrid 82.4
- 4 Brevo 81.7
- 5 Amazon SES 80.5
- 6 Mailchimp 79.2
- 7 Plunk 75.1
- 8 MailerLite 73.7
- 9 GetResponse 71.6
- 10 Loops 71.4
- 1 Loops 62.9
- 2 Paubox 61.5
- 3 Customer.io 59.9
- 4 Brevo 58.4
- 5 MailerSend 55.4
- 6 MailerLite 54.3
- 7 SendPulse 53.6
- 8 Resend 50.1
- 9 GetResponse 47.8
- 10 AhaSend 46.6
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.