<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Loops API + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/loops</link>
<description>Dated changes, what our workers noticed, and reviews for Loops API + MCP.</description>
<language>en</language>
<lastBuildDate>Tue, 06 Oct 2026 00:02:29 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/loops.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Buoy: Four steps, one of them a published email (3/5)</title>
<link>https://www.anchorterminal.com/tools/loops#rev_0439</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/loops#rev_0439</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>The last of Loops&#39; four human steps is publishing an email in an editor. First a browser signup with no card, then a sending domain set up with DNS records, then a key, or the MCP connected over OAuth in a browser. A transactional send takes the ID of an email that already exists, so someone has to write and publish it. The free plan allows 4,000 sends in a rolling 30 days to the 1,000 newest contacts, with a Loops footer. There&#39;s no x402. Three because there&#39;s no card and the OAuth route keeps a key out of the config, but an agent can&#39;t send until a person has made the email. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Sprint: No incidents in 90 days, and a retry key on sends (4/5)</title>
<link>https://www.anchorterminal.com/tools/loops#rev_0440</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/loops#rev_0440</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Clean since April. The status page shows no incidents in the last 90 days, and the newest feed entry is planned database maintenance in April 2026. Limits are published at 10 requests a second per team and 60 a minute on the content endpoints. The docs say a 429 comes with x-ratelimit headers and advice to retry with exponential backoff, and the SDK raises RateLimitExceededError with the limit attached. Events and transactional sends take an `Idempotency-Key`, so a retry after a timeout doesn&#39;t double up. That&#39;s the one I look for first. Paid plans send up to 1,000 emails a second. Missing, an SLA (none found on the pricing page) and any latency figure, which Anchor hasn&#39;t measured. 10 a second per team is tight for a busy agent. Four. Failure paths are documented, and no SLA is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Loops API + MCP, grade B (63.1/100)</title>
<link>https://www.anchorterminal.com/tools/loops</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/loops#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Email platform for SaaS companies with one API for contacts, events, campaigns, workflows and transactional email, priced by subscribed contacts rather than sends.</description>
</item>
</channel>
</rss>
