Migrate from Resend to AISend in 5 Minutes

The whole change is two lines

AISend speaks Resend's API on purpose, so migrating isn't a rewrite — it's a swap. If you use the Resend Node SDK, the entire code change is the import and the client. Everything below is the same call you already make.

- import { Resend } from 'resend';
- const resend = new Resend(process.env.RESEND_API_KEY);
+ import { AISend } from 'aisend-email';
+ const aisend = new AISend(process.env.AISEND_API_KEY);

  // Same request shape, same re_ key format
- await resend.emails.send({ from, to, subject, html });
+ await aisend.emails.send({ from, to, subject, html });

What maps to what

For anyone calling the REST API directly, here's the full mapping. The paths are identical; the /api/v1 prefix is optional, so a Resend HTTP client only needs its host changed.

                 Resend                      AISend
Base URL         api.resend.com              api.aisend.app
Send endpoint    POST /emails                POST /emails
Get status       GET  /emails/:id            GET  /emails/:id
Auth             Bearer re_...               Bearer re_...  (same format)
Node SDK         resend                      aisend-email
Price (50k/mo)   $20                         $14

Step 1: Account and key

Sign up at aisend.app — 3,000 emails/month free (100/day), no credit card. Verify your email, then create a key in the API Keys section. Keys use the same re_ prefix as Resend, so any tooling that validates the format keeps working.

Step 2: Verify your sending domain

Add your sending domain in the dashboard — the one real step, and the same one every provider requires (Resend included): you can only send from a domain you've proven you own. If you already have SPF and DKIM set up for Resend, point them at AISend instead; the dashboard shows the exact records, or connect Cloudflare for one-click setup. The free plan includes one domain, and it usually verifies within minutes of DNS propagating.

Step 3: Migrate safely — dual-send while you verify

Be honest with yourself about the risk: AISend is newer than Resend and doesn't have Resend's years of shared-IP reputation, so don't cut over your password resets on a Friday and hope. Do what Resend itself recommends when switching providers — run both in parallel for a short window. Keep your Resend key live, send a copy (or a percentage) of real traffic through AISend, and watch the delivery events and your own inbox placement. When AISend's numbers look right for your audience, flip the default. This costs you nothing on the free tier and turns 'trust a new sender' into 'verify a new sender' — which is the honest way to earn the switch.

What you get after migrating

Both Resend and AISend send on the same class of infrastructure (AWS SES), so this isn't a deliverability upgrade — it's the same delivery for ~30% less, plus a couple of things Resend doesn't ship. SPF, DKIM, and DMARC are in place; bounces and complaints go on a suppression list automatically so a bad address can't be retried into your reputation; delivery events (sent, delivered, bounced, complained) show in the dashboard and via webhooks. And the same account works with the built-in aisend-mcp server, so an AI agent can send through it as a native tool — no extra setup.