Compare
AgentiSend vs Cloudflare Email Service
Yes, AgentiSend is a Cloudflare Email Service alternative when an agent holds the key, while Cloudflare Email Service includes unlimited inbound routing on the free Workers plan. Every refused request carries code, message, fix (the call that repairs it), docs_url and retryable. A Free plan that does not expire: 3,000 emails a month, 100 a day, 3 domains, no card. Then plans from $9 a month (Starter, 30,000 emails). No plan daily cap; delivery paced per inbox provider. Or 40% off paid yearly.
Pick Cloudflare Email Service when you want unlimited inbound routing on the free Workers plan, with the message handled in your own Worker; pick AgentiSend when an agent holds the key and you want a per-key budget and a kill switch. The figures below are from Cloudflare Email Service pages fetched on 21 October 2026 and from this product's pricing table and published API.
| What matters | AgentiSend | Cloudflare Email Service |
|---|---|---|
| Trying it before paying | A Free plan that does not expire: 3,000 emails a month, 100 a day, 3 domains, no card. Then plans from $9 a month (Starter, 30,000 emails). No plan daily cap; delivery paced per inbox provider. Or 40% off paid yearly. | Sending to arbitrary recipients requires the Workers Paid plan: 3,000 outbound emails a month, then $0.35 per 1,000. Sends to verified destination addresses are free on every plan and do not count toward that quota. Inbound Email Routing is unlimited on Workers Free and Workers Paid. |
| A spending limit per key | Every 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). | A 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 retry never sends twice | Idempotency-Key is accepted on every endpoint that changes something and remembered for 7 days. | An idempotency key is not documented on the REST send page. A repeated call is not described as returning the first result. |
| What a refusal tells you | Every refused request carries code, message, fix (the call that repairs it), docs_url and retryable. | 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. |
| How long the log keeps a message | 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. | 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. |
| What the model can call | A hosted MCP server with 92 MCP tools (46 listed by default, the rest named by list_more_tools). An agent gets the same budget and kill switch over MCP as over the API. | An MCP server is not documented on the pricing page, the REST send page, or the Email Workers page. |
| Audited security reports | None yet. No SOC 2 report and no penetration-test letter exist, and /security says so. | A SOC 2 report is not stated on the pricing page or the limits page. The limits page names CAN-SPAM, GDPR and CASL as rules a sender must follow. |
| Where the data sits, and a dedicated address | Not offered. Customer data is processed in the United States. Dedicated IP on request. Once one is assigned, the published ramp is 20% of volume to day 7, 40% to day 14, 60% to day 21, 80% to day 28, then all of it, on GET /dedicated-ips/ramp. | A choice of processing region is not stated on the pricing page or the limits page. A dedicated IP is not listed on those pages. |
| Receiving mail | Receiving is a switch on each verified domain: publish one MX record and mail to that domain is stored on your account, with extracted_text beside the raw body, a clear or review label on every message, an optional hold until a person releases it, and allow and block rules per domain. There is no inbox object; the domain is the address. | Inbound Email Routing is unlimited on Workers Free and Workers Paid. An Email Worker handles the message in your code: forward to a verified address, reply once when DMARC passes, or reject it. A reply must use the same sender and domain, and it is refused when the incoming message has more than 100 References entries. The Email Workers page does not describe an inbox you list later through an API. |
Sources
- Trying it before paying. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-service/platform/pricing/ (captured 2026-10-21).
- A spending limit per key. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-service/platform/limits/ and https://developers.cloudflare.com/email-service/platform/pricing/ (captured 2026-10-21).
- A retry never sends twice. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-service/api/send-emails/rest-api/ (captured 2026-10-21).
- What a refusal tells you. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-service/api/send-emails/rest-api/ (captured 2026-10-21).
- How long the log keeps a message. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-service/observability/logs/ and https://developers.cloudflare.com/email-service/observability/metrics-analytics/ (captured 2026-10-21).
- What the model can call. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-routing/email-workers/ and https://developers.cloudflare.com/email-service/platform/pricing/ (captured 2026-10-21).
- Audited security reports. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-service/platform/limits/ and https://developers.cloudflare.com/email-service/platform/pricing/ (captured 2026-10-21).
- Where the data sits, and a dedicated address. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-service/platform/pricing/ and https://developers.cloudflare.com/email-service/platform/limits/ (captured 2026-10-21).
- Receiving mail. Ours: the published API, /pricing and /security. Theirs: https://developers.cloudflare.com/email-routing/email-workers/ and https://developers.cloudflare.com/email-service/platform/pricing/ (captured 2026-10-21).