# Resend alternative with the same API

> Scribase Mail answers the Resend API at mail-api.scribase.com: the resend SDK works with a new base URL. Free 3,000 emails a month, Pro $20, Scale $90.

Source: https://scribase.com/resend-alternative

Scribase Mail serves the Resend REST API for sending: emails, batch sends, scheduling, domains, API keys, signed webhooks and suppressions. Keep the resend package, change the base URL and the key. Contacts, broadcasts and inbound mail are not there yet, and we say so below.

## Switch with two lines

The resend package reads its base URL from the RESEND_BASE_URL environment variable or a baseUrl option. Point it at Scribase Mail and use a Scribase Mail API key; the rest of your sending code stays.

```ts
import { Resend } from 'resend'

const resend = new Resend(process.env.SCRIBASE_MAIL_KEY, {
  baseUrl: 'https://mail-api.scribase.com',
})

const { data, error } = await resend.emails.send({
  from: 'Acme <hello@mail.acme.com>',
  to: ['you@example.com'],
  subject: 'Your receipt',
  html: '<p>Thanks for your order.</p>',
})
```

_Or with curl_

```sh
curl -X POST https://mail-api.scribase.com/emails \
  -H "Authorization: Bearer $SCRIBASE_MAIL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from":"Acme <hello@mail.acme.com>","to":["you@example.com"],"subject":"Hi","html":"<p>Hi</p>"}'
```

## What the API covers

_Resend API routes served by mail-api.scribase.com_

| Resource | Routes |
| --- | --- |
| Emails | POST /emails, POST /emails/batch, GET /emails, GET /emails/:id, PATCH /emails/:id, POST /emails/:id/cancel, GET /emails/:id/events |
| Domains | POST /domains, GET /domains, GET /domains/:id, PATCH /domains/:id, DELETE /domains/:id, POST /domains/:id/verify |
| API keys | POST /api-keys, GET /api-keys, DELETE /api-keys/:id (full_access or sending_access, optionally one domain) |
| Webhooks | POST /webhooks, GET /webhooks, PATCH /webhooks/:id, DELETE /webhooks/:id, GET /webhooks/:id/deliveries; signed with a whsec_ secret, svix-* headers |
| Suppressions | GET /suppressions, POST /suppressions, DELETE /suppressions/:address |
| Usage | GET /usage, GET /audit-log, GET /billing |
| Not yet | /contacts, /audiences, /broadcasts, /templates, /emails/received answer 404 today |

## Pricing

Three plans, billed monthly, no card for Free. Real mail needs a verified domain on every plan; sk_test_ keys simulate sends without one.

_Scribase Mail plans (USD a month), from the live /billing/plans endpoint_

| Plan | Price | Emails a month | Daily cap | Domains | Webhook endpoints | Over the quota |
| --- | --- | --- | --- | --- | --- | --- |
| Free | $0 | 3,000 | 100 | 1 | 1 | Sending stops |
| Pro | $20 | 50,000 | None | 10 | 5 | $0.80 per 1,000 |
| Scale | $90 | 150,000 | None | 1,000 | 20 | $0.60 per 1,000 |

## What is different from Resend

- Mail goes out through the Oracle Cloud Email Delivery relay, DKIM-signed with your own domain key.
- Test mode is a key, not an address list: an sk_test_ key simulates every send, and recipients on test.scribase.dev script the outcome (bounced@, complained@, delayed@).
- Webhooks are signed in the Standard Webhooks format and also carry svix-* headers, so resend.webhooks.verify() and the svix library both work.
- Not yet: contacts, audiences, broadcasts, templates, inbound email and SMTP submission. Code that uses those gets a 404 today.
- It is younger. Resend has SDKs in more languages, a longer track record and more integrations.

## Export your Resend domains and broadcasts in one command

scribase-migrate is a small, separate command-line tool (no install, runs with npx) that pulls every sending domain with its DNS records, and every broadcast, out of Resend into a JSON file. No Scribase account is needed to run it. It does not import that file automatically yet — use it to re-create the domains on Scribase Mail.

_Documented at docs.scribase.com/docs/migrate_

```sh
npx --yes git+https://rithub.dev/caelum0x/scribase-migrate.git resend \
  --api-key <re_...> --out resend-export.json
```

## FAQ

**Do I need to change my email templates?**

No. The same send payload is accepted: from, to, cc, bcc, reply_to, subject, html, text, attachments, tags, headers and scheduled_at.

**Do webhooks verify with the same code?**

Yes. Each delivery carries webhook-id, webhook-timestamp and webhook-signature plus the same values as svix-id, svix-timestamp and svix-signature, signed with your whsec_ secret, so the svix library (which the resend SDK uses) accepts them. A tampered body is rejected.

**Can I use my own domain?**

Yes, and you must to send real mail. Add it in the dashboard or with POST /domains, publish the DKIM, SPF and DMARC records it shows, then verify. The check reads live DNS.

**Is Scribase Mail affiliated with Resend?**

No. It implements the same public API so existing code works. Resend is a trademark of its owner.

## Related

- [Scribase Mail overview](https://scribase.com/mail)
- [Scribase Mail docs](https://scribase.com/mail/docs)
- [Move from Resend step by step](https://scribase.com/mail/migrate-from-resend)
- [Resend domain verification failed](https://scribase.com/resend-domain-verification-failed)
- [Resend rate limit exceeded](https://scribase.com/resend-rate-limit-exceeded)
- [Resend webhook not firing](https://scribase.com/resend-webhook-not-firing)
- [Resend free tier limit](https://scribase.com/resend-free-tier-limit)
- [Scribase backend](https://scribase.com/)