Pingram vs SuprSend

Pingram

Email and SMS go out through one REST call with built-in delivery, per-message prices are public and the free tier needs no card. No rate limits or idempotency keys were found in the reviewed documentation, and the MCP connector acts with the signed-in user's whole account.

SuprSend

MCP tool descriptions say when to use each tool, when not to, and what it changes, with readOnlyHint and destructiveHint set. No rate-limit page or 429 guidance.

Pingram

1. Use the API host for the account's region. The key and region (us, eu or ca) come from the API Keys page in the dashboard
2. Keep the trackingId from each send and check Logs before retrying. No idempotency key was found, so a blind retry can send twice
3. Pass accountId on MCP tools when the user belongs to several accounts. Without it the tools use the earliest account joined
4. Create broadcasts as drafts only. Pingram's own skill says a person must send a broadcast from the dashboard
5. Expect 402 when the monthly budget is spent. Unused balance does not roll over

SuprSend

1. Pass an idempotency key on each trigger. It holds for 24 hours
2. Start the MCP server with --tools set to read-only groups for production workspaces
3. Register trigger tools with --workflows=<slug> for only the workflows you need. The default registers none
4. Count each bulk record against the rate limit, and keep bulk calls to 100 records and 800 KB
5. Treat management API responses as secrets. They include the workspace secret in plain text