Migrate from Resend to AISend in 5 Minutes

Why developers are switching from Resend

Resend built a great developer experience for email APIs, and we respect what they've done. But developers are switching to AISend for features Resend doesn't offer: intelligent multi-provider routing that eliminates single-provider risk, AI-powered deliverability scoring that catches issues before they affect your reputation, send time optimization that improves engagement metrics, and a more generous free tier. The best part? AISend's API is designed to be compatible with Resend's, so switching takes minutes, not days. You don't need to rewrite your email integration — just change the endpoint and API key.

Step 1: Create your AISend account

Sign up at aisend.app. It's free — 3,000 emails per month with all AI features included, no credit card required. Once registered, go to the API Keys section in your dashboard and create your first key. AISend keys use the as_ prefix (e.g., as_abc123...) compared to Resend's re_ prefix. Save your API key securely — it's only shown once. If you lose it, you can revoke it and create a new one from the dashboard.

Step 2: Update your API endpoint

If you're calling the Resend API directly via HTTP, change your base URL from https://api.resend.com to https://api.aisend.app. The endpoint paths are identical: POST /v1/emails to send, GET /v1/emails/:id to check status. If you're using the Resend Node.js SDK, you can either switch to the AISend SDK (npm install aisend) or simply update the base URL configuration. The request and response formats are the same, so your existing code will work without changes.

- const resend = new Resend(process.env.RESEND_API_KEY);
+ const aisend = new AISend(process.env.AISEND_API_KEY);

  // Same API — zero code changes
- await resend.emails.send({ from, to, subject, html });
+ await aisend.emails.send({ from, to, subject, html });

Step 3: Swap your API key and verify domains

Update your environment variables: replace RESEND_API_KEY with AISEND_API_KEY and set it to your new as_ key. Then add your sending domains in the AISend dashboard. If you already have SPF and DKIM records configured for Resend, you'll need to update them to point to AISend. The dashboard shows you exactly which DNS records to add or modify. Domain verification typically takes under 5 minutes once DNS records propagate.

What you get after migrating

After switching, your existing code works unchanged but now benefits from AISend's AI layer: every email is automatically routed through the best provider for that specific recipient, content is scored for deliverability before sending, and delivery timing is optimized for maximum engagement. You can monitor all of this in real-time from the AISend dashboard. The analytics show which providers are being selected, deliverability scores for each email, and trend data for your sending domains. No configuration needed — the AI features activate automatically on your first send.