Skip to content

Compare

Email API alternatives, compared on guardrails

14 email APIs compared with AgentiSend on price, free plan, log retention and the guardrails every automated sender needs: Resend, Amazon SES, AgentMail…

ProviderA spending limit per keyWhat a refusal tells youA retry never sends twiceHow long the log keeps a message
AgentiSendEvery key is created with a send budget. The send path refuses with agent_budget_exceeded when it is spent, and a key cannot raise its own. The plan inclusion is a second ceiling (plan_limit_reached).Every refused request carries code, message, fix (the call that repairs it), docs_url and retryable.Idempotency-Key is accepted on every endpoint that changes something and remembered for 7 days.7 days on Free, 30 on Starter, 90 on Pro, 180 on Scale. It is part of the plan and there is no add-on to buy.
ResendThe pricing page lists API key permissions on every plan. It does not list a send budget per key.The rate-limit page names daily_quota_exceeded and monthly_quota_exceeded. A fix field naming the next call is not on that page.Idempotency-Key is supported on sending an email, sending a batch, and on sending an inbox draft, replying to a thread and forwarding a thread. Keys are kept for 24 hours and can be up to 256 characters.The pricing table lists data retention of 30 days on Free, Pro and Scale, and flexible data retention on Enterprise.
Amazon SESA per-credential send budget is not on the pricing page or the account-sending page.PutAccountSendingAttributes documents BadRequestException and TooManyRequestsException. A fix field naming the next call is not on that page.The SendEmail reference does not document an idempotency key. A retried call is not described as returning the first result.The pricing page does not include a message log. It prices storage you configure yourself, including S3 and CloudWatch.
AgentMailPlan caps are on the pricing page: 100 a day on Free, 1,000 a day and 100 every 5 minutes on Developer, 15,000 a day and 1,500 every 5 minutes on Startup. A per-key send budget is not.The error reference says most responses include a code, a message, a docs link and a fix that names the next action. The sending refusal message_rejected carries a fix that states which case applies: a recipient on a send block list, a recipient missing from a send allow list, or an attachment the server could not fetch.Idempotency-Key on send expires 24 hours after the send completes. Create calls can also take a client_id, and a repeat returns the first resource.Storage is 3 GB on Free and 10 GB on Developer. The Startup storage cell is blank. Message expiry is optional and off by default: when an organization turns it on, access to each message ends 24 hours after it was recorded.
PostmarkA per-key send budget is not on the pricing page. API permission controls are listed as a feature.A fix field naming the next call is not on the idempotency article or the webhooks overview.Postmark does not support an idempotency key. The support article says to detect duplicates yourself.45 days of activity on every listed plan. Pro and Platform can buy custom retention from 7 to 365 days.
SendGridThe pricing page lists API key permissions. It does not list a send budget per key.A fix field naming the next call is not on the pricing page or the mail-send reference.The mail-send reference does not document an idempotency key.Searchable email activity is 3 days on the 60-day column and on Essentials, and 7 days on Pro and Premier. More history is an add-on.
MailgunA per-key send budget is not on the pricing page. Free and Basic list 2 API keys.A fix field naming the next call is not on the pricing page or the webhook-signing page.An idempotency key is not documented on the pricing page or the webhook-signing page.Log retention is 1 day on Free and Basic, 5 days on Foundation, and 30 days on Scale. Scale lists message retention up to 7 days.
LoopsA per-key send budget is not on the pricing page or the MCP page.The send-transactional page documents 409 for a reused key, 404 when the template is missing, and 400 for other errors. A fix field naming the next call is not on that page.Idempotency-Key is optional, up to 100 characters. The send-transactional page says a key reused within 24 hours returns 409 Conflict.A retention period is not stated on the pricing page or the MCP page.
PlunkCaps are per project and per category, not per key. Crossing one returns 402 with error code BILLING_LIMIT_EXCEEDED. A per-key send budget is not on the billing page.The billing page names 402 and BILLING_LIMIT_EXCEEDED when a cap is hit. A fix field naming the next call is not on that page.An idempotency key is not documented on the billing page or the MCP guide.A retention period is not stated on the pricing page, the billing page or the MCP guide.
MailtrapA per-key send budget is not on the pricing plans page. The rate-limits page sets 150 requests per 10 seconds per API token, shared by every endpoint, which is a request cap rather than a send budget.A failed send returns success set to false and an errors array of strings. The bad-request response says to fix the errors listed before retrying. A field named fix that names the next call is not on that page.The send transactional page does not document an idempotency key. A repeated call is not described as returning the first result.Email log retention is 3 days on Free, 5 days on Basic, 15 days on Business, and 30 days on Enterprise.
Cloudflare Email ServiceA per-key send budget is not on the pricing page or the limits page. Daily sending limits are per account. New accounts start with a quota that rises with sending behavior, and the limits page does not publish the starting number.A failed REST send returns success set to false and an errors array of numeric codes and messages. A field named fix that names the next call is not on that page.An idempotency key is not documented on the REST send page. A repeated call is not described as returning the first result.The activity log filter covers a window from 30 minutes to 30 days. Message previews, when Email preview is on, are kept about 7 days. Sending and routing metrics are retained for 31 days.
BrevoA per-key send budget is not on the pricing page or the transactional page.The idempotency page names duplicate_parameter when a key is reused within 30 minutes. A field named fix that names the next call is not on that page. The inbound events reference lists a code and a message on a failure, and does not name a fix field.The transactional page says idempotency is a UUID kept for 30 minutes so a retry does not send twice. The idempotency page says a key reused within 30 minutes returns a duplicate_parameter error and the request is not processed. It does not say the first result is returned.The pricing page says every plan includes transactional email with unlimited log retention. The transactional page calls retention flexible, including on the free plan, and does not restate a day count. The inbound events reference returns the last 30 days when no range is set, and a chosen range cannot exceed 30 days.
MailerSendTokens are created with scopes such as email_full, and a token can be paused. The token reference does not list a count of emails the token may send. The general errors page says MS42204 means the account reached the emails in its plan, or a sending limit it set for itself, and says to raise that limit under Plan and billing.The general errors table gives each failure a code and a message, such as MS42204. A field named fix that names the next call is not on that page.The send reference lists the JSON fields for sending, including from, to, subject, text and html. An idempotency key is not among them.Email activity retention on the pricing table is 30 days on Professional, 7 days on Starter, and 1 day on Hobby and Free. API log retention is 7 days on Professional and blank on the other three columns.
MailjetThe authentication page says each request uses a public API key and a private API key, and that a plan includes one primary key and one subaccount key. It does not list a send budget on a key. The pricing page does not list one either.The status-code page lists a code, a reason and a description, including 401 for an incorrect key pair and 429 when the call rate is over the per-minute maximum. A field named fix that names the next call is not on that page.The send reference lists Messages, From, To, TextPart, HTMLPart and TemplateID. An idempotency key is not among the properties on that page.Not compared
SMTP2GOThe getting-started page says each API key can set a rate limit, which defaults to unlimited, and permissions for particular endpoints. The API keys article says a paid account has no limit on how many keys it can add. Neither page lists a count of emails the key may send.The getting-started page says a missing, invalid or disabled API key returns 401 Unauthorized. The send guide says a failed request returns 400 with error_code and error. A field named fix that names the next call is not on either page.The send guide lists 13 parameters for /email/send, including sender, to, subject, html_body and text_body. An idempotency key is not among them.The free-plan article says free accounts see 5 days of Activity reporting and paying customers see 30 days, with an option to extend from 60 days to 2 years. The vendor page says email data is deleted once it reaches 35 days by default, and that paid plans can extend Activity storage to 60 days, 120 days, 1 year or 2 years.

Each cell is a row from the full comparison, where its source and capture date are listed.

Every comparison

Resend, on price and on the import