The latest articles on DEV Community by agentanalytics (@agentanalytics). https://dev.to/agentanalytics https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4066784%2Fa7c50172-5db1-4012-8392-657f4698a68b.png https://dev.to/agentanalytics en agentanalytics Fri, 07 Aug 2026 04:56:42 +0000 https://dev.to/agentanalytics/best-transactional-email-apis-for-typescript-saas-53j5 https://dev.to/agentanalytics/best-transactional-email-apis-for-typescript-saas-53j5 <h1> Best transactional email APIs for TypeScript SaaS </h1> <p>Which transactional email API does a coding agent choose when it must research the category and implement a working TypeScript path?</p> <p>AgentAnalytics ran 64 fresh-workspace Claude Code attempts across four common SaaS tasks: a welcome email, a template receipt, delivery webhooks, and batch notifications. Public web research was required before each selection. Claude was not shown a provider list.</p> <h2> Answer first </h2> <p>In this panel, <strong>Resend was the strongest current selection</strong>. Claude selected it in 56 of 64 attempts, and all 56 passed the available validators.</p> <p>Postmark was selected in eight attempts, all for delivery webhooks. Seven of those implementations relied on HMAC or signature verification that Postmark's canonical documentation says is unsupported. Only one Postmark implementation passed the available provider-specific check.</p> <div class="table-wrapper-paragraph"><table> <thead> <tr> <th>Provider</th> <th>Raw selection</th> <th>Passed available validators</th> </tr> </thead> <tbody> <tr> <td>Resend</td> <td>56 / 64</td> <td>56 / 64</td> </tr> <tr> <td>Postmark</td> <td>8 / 64</td> <td>1 / 64</td> </tr> <tr> <td>SendGrid</td> <td>0 / 64</td> <td>0 / 64</td> </tr> <tr> <td>Mailgun</td> <td>0 / 64</td> <td>0 / 64</td> </tr> <tr> <td>Amazon SES</td> <td>0 / 64</td> <td>0 / 64</td> </tr> <tr> <td>Mailchimp Transactional</td> <td>0 / 64</td> <td>0 / 64</td> </tr> </tbody> </table></div> <p>This is not a universal provider ranking. It is a dated result for one model, harness, task family, and retrieval condition.</p> <h2> The task split </h2> <ul> <li> <strong>Welcome email:</strong> Resend 16 / 16.</li> <li> <strong>Template receipt:</strong> Resend 16 / 16.</li> <li> <strong>Delivery webhook:</strong> Resend 8 / 16; Postmark 8 / 16 raw. Seven Postmark artifacts failed the provider-specific authentication check.</li> <li> <strong>Batch notifications:</strong> Resend 16 / 16.</li> </ul> <p>Zero selections do not prove that a provider is incapable of a task. They mean this panel did not produce implementation evidence for that provider.</p> <h2> The shortlist came from comparison content </h2> <p>Claude made 69 WebSearch calls and no explicit WebFetch calls. Of 554 visible search-result links:</p> <ul> <li>516, or 93%, were comparison pages;</li> <li>548, or 99%, were third-party links;</li> <li>six were owned by an in-scope provider;</li> <li>no provider page was explicitly fetched.</li> </ul> <p>That matters because the decision was often shaped before Claude opened a vendor's documentation. The model-facing search result itself summarized the category and cited comparison sources.</p> <h2> A title and URL were not enough </h2> <p>Before publication, AgentAnalytics replayed 16 captured search contexts through three matched conditions:</p> <ol> <li>the original search evidence;</li> <li>the same evidence with the proposed page title and URL inserted;</li> <li>the same evidence with the page's factual task-level findings added to the model-facing synthesis.</li> </ol> <p>Listing the title and URL changed 0 of 16 provider choices. Adding the factual evidence changed five choices and produced three additional artifacts that passed the available validators, with no paired validation losses.</p> <p>The evidence mostly steered Claude away from unsupported Postmark webhook implementations. This does <strong>not</strong> show that a comparison page can promote a favored provider. It shows that task-specific evidence can change decisions once that evidence reaches the model-facing context.</p> <h2> Method </h2> <ul> <li> <strong>Agent:</strong> Claude Code 2.1.148</li> <li> <strong>Model:</strong> Claude Sonnet 4.6, low effort</li> <li> <strong>Attempts:</strong> 64 accepted, zero excluded, zero timed out</li> <li> <strong>Environment:</strong> fresh workspace per attempt</li> <li> <strong>Intent:</strong> category evaluation with live public WebSearch required</li> <li> <strong>Provider set used for analysis:</strong> Resend, Postmark, SendGrid, Mailgun, Amazon SES, and Mailchimp Transactional</li> <li> <strong>Validation:</strong> TypeScript syntax diagnostics plus a provider-specific Postmark webhook authentication check</li> </ul> <p>The benchmark did not test live provider API calls, inbox placement, deliverability, account activation, or long-term retention. Provider-semantic validation remains incomplete outside the Postmark webhook path.</p> <h2> Evidence and corrections </h2> <p>The full report, task prompts, source links, limitations, and machine-readable evidence are available at:</p> <p><strong><a href="https://agentanalytics.org/research/best-transactional-email-apis-typescript-saas" rel="noopener noreferrer">AgentAnalytics: Best transactional email APIs for TypeScript SaaS</a></strong></p> <p>This benchmark was not commissioned by an included provider. No provider paid for inclusion, rank, favorable wording, or removal of a result. Material corrections are dated and the evidence file is versioned. Corrections can be sent to <a href="mailto:founders@agentanalytics.org">founders@agentanalytics.org</a>.</p> ai typescript api webdev