Home / Email
Loops
loops.so/pricingMarketing and transactional senderemail/loopsJSONcomparereport an errorprovider JSON
- Free allowance
- 4,000 sends per rolling 30 days, 1,000 contacts, marketing and transactional combined
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- request-rate4,000 sends per rolling 30 days
- Evidence
- documented1 source; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | 4,000 sends per rolling 30 days, 1,000 contacts, marketing and transactional combined unit requests; metered on request-count |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) 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 |
|---|
| Binding | request-rate the 1,000-contact ceiling binds, not the 4,000 sends. |
|---|
| Identity | email an account |
|---|
| Egress | not applicable: an outbound sender |
|---|
| Retention | not stated |
|---|
| Interface | rest the Loops transactional API |
|---|
| Tooling | curl, any HTTP client |
|---|
| Composes with | 4,000 sends against 1,000 contacts, so the contact ceiling decides and a list of 1,000 can receive four messages a month. |
|---|
| Reliability | sends and contacts are separate caps, so the smaller one decides |
|---|
| Parsed numbers | |
|---|
Evidence 1
| date | source | what it proved |
|---|
| 2026-10-22 | loops.so/.well-known/pricing.txt | the machine-readable pricing file states 4,000 sends per rolling 30 days and a 1,000-contact ceiling |
More fields 1