Introducing AISend: A Resend-Compatible Email API
Why we built AISend
We run a portfolio of small products, and every one of them needs the same thing: password resets, receipts, alerts, welcome emails. We were paying per-product for transactional email while the actual sending is a thin layer over infrastructure we could run ourselves. So we built AISend to send our own mail — every product in the portfolio runs on it — and opened it up. That origin shapes the product: it exists to be cheap, boring, and reliable, not to be clever.
The same API you already use
We didn't invent a new API, because the good one already exists. AISend speaks Resend's request format: the same /emails endpoint, the same JSON body, the same re_ key prefix. If you're on Resend today, migrating is a two-line change (swap the import and the client) or, if you call HTTP directly, one base URL. We made it compatible on purpose — the point isn't to make you learn something, it's to make leaving costless. If we're not better for you, switch back just as easily.
What's actually different
Two honest things. First, price: 50,000 emails is $14/mo instead of $20, and the free tier is 3,000/month (100/day) with one verified sending domain included. Second, AI agents: AISend ships a built-in MCP server, so Claude, Cursor, or an autonomous agent can send email as a native tool without you writing glue code — and an agent can provision its own account and key with a single API call. What is NOT different: we send through AWS SES, the same class of infrastructure most providers use. We're not going to tell you we deliver better than Resend, because we can't prove it and it wouldn't be true.
Developer-first, always
The REST API is clean and predictable. Four fields to send an email: from, to, subject, html. No configuration objects, no template IDs, no batch-processing ceremony. The dashboard shows deliverability metrics rather than vanity analytics: sent, delivered, bounced, complained, with webhooks for all of it. Idempotency keys make retries safe. And the whole thing is dogfooded — when something breaks, it breaks for our own products first.
Being honest about being new
AISend is newer than the incumbents and doesn't have years of shared-IP reputation behind it. If you're moving production password resets, don't take our word for it — keep your current provider configured, dual-send for a week, and watch your own inbox placement before you flip the default. That costs nothing on the free tier. We'd rather you verify us than trust us.
Related Posts
Ready to Send Smarter Emails?
3,000 emails/month free. No credit card required.