Loops API + MCP vs Zoho CPaaS (formerly ZeptoMail)

Loops API + MCP

No status incidents in the last 90 days. No scoped or read-only keys, and no read-only MCP mode.

Zoho CPaaS (formerly ZeptoMail)

A public OpenAPI 3.0 file covers all 42 operations, and each Agent has its own send-only key. Email costs $2.50 per 10,000 with the first credit free. No API rate limit, 429 handling, idempotency key or SLA was found in the reviewed documentation, and new accounts wait for a manual review.

Loops API + MCP

1. Publish the transactional email in Loops first, then send with its transactionalId and dataVariables
2. Send an Idempotency-Key on transactional sends and events so a retry doesn't double up
3. On 429, back off exponentially and read x-ratelimit-remaining
4. Ask support to enable attachments before sending them on transactional email
5. Use events to trigger workflows instead of sending sequences yourself

Zoho CPaaS (formerly ZeptoMail)

1. Call the base URL for the account's region (cpaas.zoho.com, .eu, .in, .com.au, .jp or .com.cn). A key from one region fails on another
2. Send with Authorization: Zoho-enczapikey <key>. Logs, domains, templates, agents and suppressions need a Zoho OAuth token as Authorization: Zoho-oauthtoken <token>
3. Post OAuth client secrets and refresh tokens in the request body, not the query string the guide shows, so they stay out of logs
4. Don't retry a timed-out send blindly. There is no idempotency key, so look the message up by client_reference in the email logs first
5. Count one email per recipient, including cc and bcc, and keep each address field to 500 entries and each attachment to 15 MB
6. Use a sandbox Agent for tests. It accepts up to 10,000 emails a day and sends none of them