Loops through Squiid

What Loops is

Loops is email for software products rather than for newsletters. You sync contacts with properties, send events from your application, and build loops that react to them: a welcome sequence after signup, a nudge when someone has not finished onboarding, a win-back after cancellation. Transactional email runs through the same API with templates edited visually, so account mail and lifecycle mail share one system and one sending reputation. Audience filters are computed from contact properties, so a segment stays current without the application maintaining a list.

In a vibe-coded product this is the service that closes the gap between shipping a feature and getting anyone to use it. An agent can already write the code to send an event; Loops turns that event into a sequence a non-developer can edit afterwards without touching the codebase. Merging transactional and lifecycle sending also avoids the common situation where receipts come from one vendor and onboarding from another, with different domains and different deliverability. Events are the integration surface, which keeps the application code simple and the marketing logic out of it.

Why connect it through Squiid

Loops is on the Squiid roadmap. When it is connected, sends and event calls will go to https://api.squiid.io/v1/loops/... with Authorization: Bearer $SQUIID_API_KEY, with the official SDK working by base URL swap (gateway convention). Contacts and sending will bill at Loops' listed price on one Squiid invoice, drawn from prepaid credits with no markup, and the API key that can read your entire contact list will stay in Squiid's custody. Transactional and campaign sending share one domain reputation, which is an argument for consolidating rather than splitting vendors.

• One account, one key, one bill, one dashboard. Loops sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Loops credentials. Your code carries SQUIID_API_KEY, so LOOPS_API_KEY, LOOPS_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 Loops 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 lifecycle email in one product
• Event-triggered sequences editable without code
• Contact properties and audience filters
• Visual template editing for non-developers
• Loops list pricing, no markup

How to connect Loops

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 LOOPS_API_KEY, LOOPS_FROM_EMAIL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Loops charges a monthly fee based on the number of contacts, with transactional sending included at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Loops usage, with no markup and no per-request margin.

Loops 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 Loops 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 Loops 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 Loops'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

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