SendRaven vs Loops
Loops charges for the list. SendRaven charges for the mail.
Loops is a pleasant product for a SaaS team that wants newsletters, onboarding sequences and transactional mail in one place with an editor a non-engineer will use. Sends are unlimited; you pay by subscribed contacts.
That is the trade. A list that grows costs more whether or not you mail it. There is no inbound, no threads, and no agent surface. If your product needs to read a reply, or an agent needs a key it cannot misuse, Loops does not have a place to put that.
Marketing email for SaaS, priced by subscribed contacts, with transactional included. Checked 2 September 2026 against loops.so.
Where Loops is the better choice
- The editor and the marketing experience. SendRaven's composer is functional; Loops' is designed.
- Unlimited sends within a contact tier, which is cheaper for a small list mailed very often.
Feature by feature
What each one does when you ask it to.
| Edge | SendRaven | Loops |
|---|---|---|
| Priced per email sent, never per contactPricing by list size charges most to the customer whose list is growing, which is the point of the product. | Yes. One meter. A contact is free. | No. by subscribed contacts; sends unlimited |
| Transactional, campaigns and automations on one planTwo products means two suppression lists that disagree and a price gap that rewards mislabelling campaigns as transactional. | Yes. One key, one plan, one dashboard, one suppression list. | Partly. marketing and transactional together; no inbound |
| The reply is a thread, not a webhookA webhook hands you a raw message and leaves you to work out which conversation it belongs to. | Yes. Joined on Message-ID to the message it answers. | No. |
| Quoted history stripped from repliesThe third reply in a thread is mostly the first two quoted back. A model reading it pays for that and gets confused by it. | Yes. text is what they typed; raw_text is the whole body. | No. |
| One query for what is awaiting a replyThis is the poll an agent actually runs. Without it you build a state machine over inbound events. | Yes. GET /v1/threads?awaiting_reply=true | No. |
| Per-key daily cap and recipient allowlistA workspace quota trips after an agent has mailed thousands of people. A key limit trips before. | Yes. daily_send_limit and allowed_recipients on the key, checked on every send. | No. |
| Human approval hold on a keyThe only way to let an agent write mail without letting it send mail. | Yes. requires_approval drafts the message and waits for a person. | No. |
| Campaign refused before it starts on bounce or complaint rateReputation dashboards report the damage. A gate prevents it. | Yes. Checked in the send path; the preview call says whether it will be allowed. | No. |
| Unsubscribe cancels queued sends and ends the sequenceDoing only the first is how a working unsubscribe still delivers day three of a welcome series. | Yes. Two writes: suppress the address, cancel what is scheduled for it. | No. not documented |
| Opt down by topic, per personGiven only all-or-nothing, people press spam instead, and a complaint costs the domain far more than an opt-out. | Yes. Preferences on (email, topic), not on a contact row. | Partly. mailing lists |
| Remote MCP server with no stored credentialsA server that holds its own database credentials is a shared identity for every caller. | Yes. mcp.sendraven.ai, OAuth or a Bearer key, reaches exactly what the key can. | No. |
| llms.txt and an unauthenticated OpenAPI documentA model decides what it is holding from the description document. Generated ones say what, not which. | Yes. Both public, written by hand, so an agent can read them before it has a key. | No. |
| Errors written for an agentA client that backs off on 429 retries a payment problem forever. A model that sees an error retries a held draft. | Yes. 402 for out of plan, not 429. pending_approval is a status, not an error. | No. |
| Inbound included and freeCharging for the reply discourages the half of email that makes it a conversation. | Yes. Replies cost nothing and land in the thread. | No. |
| Free tier without a cardA trial that expires is a deadline, not a tier. | Yes. 3,000 emails a month, inbound included. | Partly. 1,000 contacts, 4,000 sends, branded footer |
| Overage per 1,000 at the entry paid tierThe overage rate is the real price for anyone who grows. | Yes. $0.30 on Pro, $0.20 on Scale. | Not applicable. |
| Usage pricing without tier cliffsTiers do not hurt at the boundaries. They hurt in the middle, which is where most senders live. | Yes. Included allowance, then a flat rate per thousand. | No. steps by contact count |
Questions
Asked by people choosing between the two.
Does Loops have an API for transactional email?
Yes, on paid plans. It does not have inbound email, threads, or per-key limits, and it prices by contacts rather than by emails sent.
Try it on one domain first.
3,000 emails a month, inbound included, no card. The other comparisons are on the compare page.