Dev, web & IT
Design, code, host and ship sites and internal tools, with an AI coding agent doing most of the typing.
Transactional email services send app-triggered messages such as receipts and password resets. Resend is the example in IonBin’s catalog. API access, domain authentication, delivery monitoring and message content all matter: an endpoint or vendor label does not determine whether an email is legally transactional.
Transactional email services provide APIs for app-triggered messages, including receipts and password resets. They also expose delivery events and domain-authentication setup. Some support marketing mail too: the API endpoint used does not decide a message’s legal classification.
Verify the sending domain, call the API with a reviewed template and monitor delivery events, bounces and complaints. Resend documents an MCP server for agent access; restrict recipients, templates and sending permissions before enabling automated actions.
Resend’s monthly transactional plans include Free (3,000 emails/month, 100/day), Pro (US$20 for 50,000) and Scale (US$90 for 100,000). Paid overage is listed at US$0.90 per 1,000. Its standard rate limit is per team; ordinary upgrades do not automatically increase it, while Enterprise lists custom rate limits. Batch requests support up to 100 emails.
Resend also permits marketing through its email API when consent and unsubscribe requirements are met. Those sends count against the transactional quota. That billing category does not make the message legally transactional.
Delivery acceptance does not guarantee inbox placement or that the customer read a message.
Google’s guidance for personal Gmail recipients requires authentication and other sender controls. Bulk senders face stronger SPF, DKIM and DMARC requirements; marketing and subscribed messages need the specified unsubscribe controls. Monitor spam rates and keep them below Google’s 0.3% threshold.
Under the US CAN-SPAM guidance, a purely transactional message is exempt from most provisions but cannot use misleading routing information. Mixed promotional and transactional messages are assessed by primary purpose, including the subject line and placement of transactional content. An existing customer relationship alone does not exempt marketing.
Separate sending streams only help when the domain, configuration and operational practices support that separation. Use duplicate-send protection, recipient checks and approval limits for agent-triggered mail. Applicable laws and provider policies still need review for your recipients.
Snapshot from official sources on Oct 18, 2026.
| Resend monthly transactional plans | Free: 3,000 emails/month, 100/day. Pro: US$20/month for 50,000. Scale: US$90/month for 100,000; published paid overage is US$0.90 per 1,000. [1] |
| Resend sending limits | The standard API rate limit is per team; the pricing FAQ says it is not increased by an ordinary plan upgrade. Enterprise advertises custom rate limits. Batch requests support up to 100 emails. [1] |
| Gmail sender rules | For personal Gmail recipients, all senders need SPF or DKIM and other technical requirements. Bulk senders need SPF, DKIM and DMARC; marketing/subscribed mail has additional unsubscribe requirements. [3] |
| CAN-SPAM primary purpose | Purely transactional or relationship messages are exempt from most provisions but may not use false or misleading routing information. Mixed messages need a primary-purpose assessment. [4] |
Design, code, host and ship sites and internal tools, with an AI coding agent doing most of the typing.
Hand repeat admin (receipts, logs, notices, handoffs) to workflows your agent can trigger.
| Tool in this entry | How agents connect |
|---|---|
| Resend | MCPAPI/CLIFile import |
Levels come from each tool's recorded, sourced compatibility. How the levels work.
Practitioner views are restated in our words and labeled as views, not measured results. Product facts come from official sources dated above.
IonBin's wiki isn't user-edited. Corrections go to our Directory Curator, who checks them against primary sources before anything changes. Spot something wrong or out of date on “Transactional email”? Email us with a link to a primary source.
Suggest an edit by email or write to contact@ionbin.com