# Rampsend > Rampsend is an email platform built for AI agents and the teams behind them: one API and one app for transactional and marketing email, sending through Amazon SES, usable from any AI assistant over MCP. Free to start; paid plans are sized by contacts (marketing) or emails (transactional), with one account covering both. Live today: send API, contacts with CSV import, sending-domain verification (DKIM, custom MAIL FROM, DMARC), automatic suppression of bounces/complaints/unsubscribes, RFC 8058 one-click unsubscribe headers, open and click tracking with machine-open (Apple Mail Privacy Protection) detection, a deliverability dashboard, and an MCP server. Coming soon: campaign builder, automations, drag-and-drop editor, webhooks. Data is stored in the EU (Ireland); email is sent through Amazon SES in Stockholm. ## Pricing - Free: 1,000 contacts, 6,000 emails/month (200/day), "Sent with Rampsend" footer. - Marketing plans by contacts from $12/month (2,500 contacts), 12 emails per contact per month included. - Transactional plans by emails from $15/month (50,000 emails); extra sending from prepaid credit that never expires. - [Pricing](https://www.rampsend.com/pricing) · [pricing.md for agents](https://www.rampsend.com/pricing.md) ## REST API - Base URL: https://app.rampsend.com/api/v1 — authenticate with `Authorization: Bearer rs_live_…` (API keys are created in the app). - `POST /emails` — send. Body: from (verified domain), to (string or up to 50; each gets its own copy), subject, html and/or text, reply_to, headers, tags, track_opens, track_clicks, unsubscribe_header. Supports `Idempotency-Key`. Returns one result per recipient (queued | sent | suppressed | failed); queued emails usually go out within seconds — follow them with GET /emails/:id. - `GET /emails/:id` — status (queued, sent, delivered, bounced, complained, failed, suppressed) and opens/clicks. - `POST /events` (and `/events/bulk`, ≤100) — track a custom event: {metric, profile: {email | phone | external_id, …}, properties, value, value_currency, time, unique_id}. Profiles are matched by external_id → email → phone; `unique_id` dedupes. 202 with {inserted, duplicates, errors}. `GET /metrics` lists custom and email metrics. - `POST /profiles` (upsert by identifier), `GET /profiles?email=`, `GET`/`PATCH /profiles/:id` — email, phone, external_id, name, location, custom properties, email_consent. - `GET`/`POST /lists`, `POST`/`DELETE /lists/:id/profiles` — add/remove ≤1,000 by profile_ids or emails. - `GET`/`POST /segments`, `GET /segments/:id/profiles`, `POST /segments/count` — dynamic segments; definition = {version: 1, groups: [{conditions: [...]}]}, groups AND-ed, conditions OR-ed; condition types metric, property, list, segment, consent, eu. - Errors: JSON `{ "error", "code" }`; X-RateLimit-* headers on every response. - [Developer docs](https://www.rampsend.com/developers) ## MCP (AI assistants) - [MCP endpoint](https://app.rampsend.com/api/mcp): Streamable HTTP. Connect with one-click OAuth 2.1 or an API key. Tools: get_account, send_email, get_email, list_emails, get_stats, add_domain, check_domain, upsert_contact, find_contacts, track_event, list_audiences, add_to_list. - [Setup guides](https://www.rampsend.com/mcp): step-by-step for [Claude](https://www.rampsend.com/mcp/claude), [ChatGPT](https://www.rampsend.com/mcp/chatgpt), [Cursor](https://www.rampsend.com/mcp/cursor), [VS Code](https://www.rampsend.com/mcp/vscode), [Codex](https://www.rampsend.com/mcp/codex), [Gemini CLI](https://www.rampsend.com/mcp/gemini) and [Grok Bot](https://www.rampsend.com/mcp/grok-bot). ## Blog - [How to let an AI agent send email with MCP](https://www.rampsend.com/blog/send-email-from-ai-agent): Connect Claude, ChatGPT, Cursor or another assistant to an email platform over MCP: sign-in vs API keys, the tools, confirm-before-send and a safety checklist. - [Gmail, Yahoo and Outlook sender requirements: a practical checklist](https://www.rampsend.com/blog/gmail-yahoo-sender-requirements): What Gmail, Yahoo and Outlook require from senders: SPF, DKIM, DMARC, alignment, one-click unsubscribe and spam rates, as a checklist to work through. - [Idempotency keys: retry email sends without sending twice](https://www.rampsend.com/blog/idempotency-keys-email-api): Why email retries cause duplicates, how idempotency keys prevent them, how to choose a key, and a TypeScript retry loop with backoff for safe sends. - [Apple Mail Privacy Protection and honest open rates](https://www.rampsend.com/blog/apple-mail-privacy-open-rates): How Apple Mail Privacy Protection inflates open rates, how machine opens are detected, which metrics to trust instead, and when to turn tracking off. - [How an email suppression list works](https://www.rampsend.com/blog/email-suppression-list): What goes on an email suppression list, how to handle soft bounces, global vs account lists, and why sending to suppressed addresses hurts deliverability. - [Bounce and complaint rates: what is normal and when to stop sending](https://www.rampsend.com/blog/bounce-and-complaint-rates): How email bounce and complaint rates are calculated, hard vs soft bounces, what normal looks like, when to stop sending, and how suppression helps. - [How to warm up a new sending domain](https://www.rampsend.com/blog/warm-up-new-sending-domain): Why new sending domains need a warm-up, a sample four-week ramp, what to send first, the signals to watch and when to slow down or stop. - [Transactional vs marketing email: the differences that matter](https://www.rampsend.com/blog/transactional-vs-marketing-email): What makes an email transactional or marketing, how consent rules differ, why they behave differently in the inbox, and how to run both safely. - [SPF, DKIM and DMARC for a new sending domain](https://www.rampsend.com/blog/spf-dkim-dmarc-setup): Set up SPF, DKIM and DMARC for a new sending domain, with example DNS records, a custom MAIL FROM subdomain for SPF alignment and a safe path to p=reject. - [Contacts or emails: how to choose an email plan](https://www.rampsend.com/blog/email-pricing-contacts-vs-emails): How email platforms price by contacts or by emails, worked examples for a newsletter and an app, and what to check: overage, seats and inactive contacts. ## Contact - hello@rampsend.com