SendGrid through Squiid

What SendGrid is

SendGrid is a long-established email platform now part of Twilio. It handles transactional sending through an API or SMTP relay, marketing campaigns with contact lists and segmentation, dynamic templates with Handlebars substitution, suppression and bounce management, dedicated IPs with warm-up for high volume, and an event webhook that reports every delivery, open, click and spam report. Subusers and scoped API keys let different parts of an organisation send without sharing one credential, which matters at volume.

In an AI-coded product SendGrid tends to be chosen for one of two reasons: the volume is high enough that per-email price and dedicated IPs matter, or the team is already using Twilio and would rather not add another vendor. Its SMTP relay is also the path of least resistance when the code an agent generated uses a generic mail library rather than a provider SDK. Deliverability at scale also depends on warming a dedicated IP gradually, which is an operational task rather than a code change.

Why connect it through Squiid

SendGrid is on the Squiid roadmap. When it lands, sending will route through https://api.squiid.io/v1/sendgrid/... with Authorization: Bearer $SQUIID_API_KEY, and the official SDKs will work by pointing their base URL at the gateway (gateway convention). Emails will meter against prepaid credits at SendGrid's list price and plan cost will pass through at the provider's price on one Squiid invoice. The API key stays with Squiid, which matters for a credential that can send mail as your domain and export your contact list. Scoped keys can also be limited to sending only, which is the minimum any generated integration should be given.

• One account, one key, one bill, one dashboard. SendGrid sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the SendGrid credentials. Your code carries SQUIID_API_KEY, so SENDGRID_API_KEY, SENDGRID_FROM_EMAIL, SMTP_PASSWORD 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 SendGrid 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 and marketing email on one key
• SMTP relay and REST API through the gateway
• Dynamic templates and suppression management
• Event webhooks for delivery and engagement
• SendGrid list pricing, no markup

How to connect SendGrid

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 SENDGRID_API_KEY, SENDGRID_FROM_EMAIL, SMTP_PASSWORD
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

SendGrid charges a monthly plan fee by email volume with extra charges for dedicated IPs and marketing contacts, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of SendGrid usage, with no markup and no per-request margin.

SendGrid has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with 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 SendGrid 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: the sending domain is re-verified in your own SendGrid account with the same DNS records, and templates and suppression lists are exported and re-imported. Squiid never owns your code, your schema or your domain, and the gateway speaks SendGrid'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

SendGrid 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 SendGrid 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.