fshy

fshy / Email

Loops

loops.so · Email · 1 record · JSON

Loops Email

caveatemailno cardDrequest-rate

loops.so/pricing · marketing and transactional sender · email/loops · JSON · compare

Free tier4,000 sends per rolling 30 days, 1,000 contacts, marketing and transactional combined
unit requests; metered on request-count
Pricenone stated
Per-object capnot applicable
Retentionnot stated
Egressnot applicable: an outbound sender
Identityemail an account
Limits
  • request-rate 4,000 sends per rolling 30 days source
counts of things, not rates, so no vocabulary kind names them: 1,000 contacts, which makes 4,000 sends unreachable for a 4,000-person list
Bindingrequest-rate the 1,000-contact ceiling binds, not the 4,000 sends.
Interfacerest the Loops transactional API
Toolingcurl, any HTTP client
Composes with4,000 sends against 1,000 contacts, so the contact ceiling decides and a list of 1,000 can receive four messages a month.
Reliabilitysends and contacts are separate caps, so the smaller one decides
Evidence rungdocumented
Checked2026-10-23 (live); stale on 2026-11-22
Evidence (1)
datesourcewhat it proved
2026-10-22loops.so/.well-known/pricing.txtthe machine-readable pricing file states 4,000 sends per rolling 30 days and a 1,000-contact ceiling
More fields (1)
{
 "stale_after_days": 90
}