Resend through Squiid

What Resend is

Resend is a transactional email API built for developers who do not want to think about email. You verify a domain, it walks you through the SPF, DKIM and DMARC records, and then sending is a single POST with a from address, a to address, a subject and HTML. React Email lets templates be components with props rather than strings of table markup, webhooks report delivered, opened, bounced and complained events, and a batch endpoint sends up to a hundred messages in one call. Audiences and broadcasts cover simple marketing sends.

Every app an agent builds needs this on day one: verification links, password resets, magic links, receipts, invitations and notifications. It is also the service most likely to be wired up wrong, because email that goes to spam does not throw an error. Authentication records and a dedicated sending subdomain are the parts that decide whether your password reset arrives, and they have nothing to do with the code. Sending volume also grows faster than teams expect once notifications and digests exist, which makes per-email visibility useful.

Why connect it through Squiid

Resend is a launch service on Squiid. Sending goes to https://api.squiid.io/v1/resend/... with Authorization: Bearer $SQUIID_API_KEY, and the official SDKs work by pointing their base URL at the gateway (gateway convention). Squiid holds the Resend key, which matters because a leaked email key lets a stranger send mail as your domain. Emails are metered against prepaid credits at Resend's list price, and the Pro plan passes through at $20 a month on your Squiid invoice with no fee added.

• One account, one key, one bill, one dashboard. Resend sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Resend credentials. Your code carries SQUIID_API_KEY, so RESEND_API_KEY, RESEND_FROM_EMAIL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Resend costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Transactional sending through the gateway
• React Email templates and a batch endpoint
• Domain authentication guidance for SPF, DKIM and DMARC
• Delivery, bounce and complaint webhooks
• Pro at $20 a month passed through at list price

How to connect Resend

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces RESEND_API_KEY, RESEND_FROM_EMAIL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/resend/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Resend charges a monthly plan fee with an included email volume and per-email pricing above it, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Resend usage, with no markup and no per-request margin.

Resend Pro passes through at $20 a month at the provider’s listed price on your monthly Squiid invoice. Service subscriptions carry no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Resend usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: you re-verify the sending domain in your own Resend account with the same DNS records and re-create templates, which is minutes of work rather than a migration. Squiid never owns your code, your schema or your domain, and the gateway speaks Resend's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Resend through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Resend usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.