# Sendocado

> Sendocado sends activation and onboarding emails for software products, through the user's own Resend, Amazon SES, Postmark, SendGrid, Mailgun, SMTP or Gmail account: a welcome email when someone signs up, then follow-ups on later days that stop when the person finishes setup. These are not account-verification emails. An agent can set it all up and change it later through the hosted MCP server.

## At a glance

- For: founders and small teams with a software product and no marketing team.
- Connect from Claude Code: `claude mcp add --transport http sendocado https://sendocado.com/api/mcp`, then type `/mcp` to sign in.
- Connect from any MCP client: https://sendocado.com/api/mcp, with OAuth in the browser or the header `Authorization: Bearer sc_…`.
- REST API: https://sendocado.com/api/v1 (OpenAPI 3.1: https://sendocado.com/api/v1/openapi.json). Every MCP tool has a matching route.
- How activation works: the product adds each signup as a contact with a tag such as `trial`, and adds a tag such as `activated` when the person finishes setup. A live campaign with the audience "tag has trial, tag has not activated" sends each email after its delay. A contact who stops matching leaves the campaign. A reply ends it too, when the campaign is set to stop on reply.
- The agent can: create a project, connect a sender (Resend, Amazon SES, Postmark, SendGrid, Mailgun or SMTP), add a sending domain and read its DNS records, import up to 1,000 contacts per call, create a campaign, preview its audience, send a test email, set it live, send broadcasts and transactional email, and read stats and replies.
- The agent cannot: do the user's first sign-in (it happens in a browser), connect Gmail, add DNS records at the user's DNS host, pay for a plan (it can make a Stripe checkout link), or delete the account.
- Before anything sends: show the user the campaign and the audience, and set it live only after the user says yes. Going live emails real people.
- Changing it later: the campaign, its emails and the contact tags stay in Sendocado. A new session reads them with `get_campaign` and changes one email with `update_campaign_step`. Sendocado stores no description of the product; ask the user for it.
- After a send: a successful call means the email is queued for the user's provider, not that it arrived. `get_send` shows each event: delivered, bounced, opened or clicked.
- Limits: delays are whole days, up to 365. Up to 50 emails per campaign. 120 API and MCP requests per minute per account.
- Price: Free for 1,000 contacts, 5,000 emails a month and 1 project, with a "Sent with Sendocado" line. Starter is $10 a month for 10,000 contacts. Growth is $30 a month for 50,000 contacts. Every plan has every feature.
- For agents: https://sendocado.com/agents. Step-by-step guide: https://sendocado.com/docs/activation-emails.md
- Every docs page in one file: https://sendocado.com/llms-full.txt

## Get started

- [Send activation and onboarding emails with your agent](https://sendocado.com/docs/activation-emails.md): How do I send activation emails for my SaaS? Connect Sendocado, add signups from your app, and set live a welcome email and follow-ups that stop when users finish onboarding.
- [MCP setup](https://sendocado.com/docs/mcp.md): Connect Claude Code, Cursor, Claude or any MCP client to Sendocado, so your agent can set up activation and onboarding emails and run them.
- [Quickstart](https://sendocado.com/docs/quickstart.md): From sign-in to a live welcome campaign: connect a provider, verify a domain, add contacts and go live, in the app or with the REST API.
- [Sendocado docs](https://sendocado.com/docs.md): How Sendocado works: activation campaigns, contacts, broadcasts and transactional email, from the app, the REST API or an agent over MCP.

## Guides

- [Campaigns](https://sendocado.com/docs/campaigns.md): How Sendocado campaigns work: steps with stable ids, waits, branches on opens and clicks, send windows, status changes, enrollments and AI drafts.
- [Audiences](https://sendocado.com/docs/audiences.md): Build Sendocado audiences from filter groups, see when contacts are matched, and preview who an audience reaches.
- [Contacts](https://sendocado.com/docs/contacts.md): Sendocado contacts: tags, attributes, time zones, batch upserts from your app, activity, exports and erasure.
- [Unsubscribes and blocks](https://sendocado.com/docs/blocked-list.md): How Sendocado handles unsubscribes, resubscribes with consent, bounces, spam complaints, manual blocks and unblocks.
- [Email content](https://sendocado.com/docs/email-content.md): Sendocado email content: HTML, markdown or templates, merge tags with fallbacks, and what Sendocado adds to every email.
- [Broadcasts](https://sendocado.com/docs/broadcasts.md): Create, schedule, send and cancel Sendocado broadcasts, and read who got them and what they did.
- [Transactional email](https://sendocado.com/docs/transactional-email.md): Send transactional email through Sendocado with templates, variables and idempotency keys, and test emails to your own inbox.
- [Replies](https://sendocado.com/docs/replies.md): How Sendocado receives replies, ties them to sends and campaigns, stops campaigns on reply and hands them to your app.
- [Webhooks](https://sendocado.com/docs/webhooks.md): Sendocado webhook events, payloads, Standard Webhooks signatures, retries and secret rotation.

## Reference

- [API basics](https://sendocado.com/docs/api.md): The Sendocado REST API: authentication, request rules, pagination, errors, rate limits and the full route reference.
- [Projects](https://sendocado.com/docs/api/projects.md): Sendocado API reference: A project holds its own contacts, campaigns, sender and settings. Every other route works inside one project.
- [Account and keys](https://sendocado.com/docs/api/account.md): Sendocado API reference: Your account, plan and usage, API keys, and the apps you connected over OAuth.
- [Contacts](https://sendocado.com/docs/api/contacts.md): Sendocado API reference: The people you email: create, update in batches, search, read their history, export or erase them.
- [Unsubscribes and blocks](https://sendocado.com/docs/api/blocked-list.md): Sendocado API reference: Who may not be emailed and why: unsubscribes, resubscribes with consent, manual blocks and unblocks.
- [Campaigns](https://sendocado.com/docs/api/campaigns.md): Sendocado API reference: Automated series of emails: the audience, the steps and their branches, status changes, enrollments, stats and AI drafts.
- [Broadcasts](https://sendocado.com/docs/api/broadcasts.md): Sendocado API reference: One-off emails to an audience, sent now or at a time you choose.
- [Transactional and test emails](https://sendocado.com/docs/api/transactional-emails.md): Sendocado API reference: One email to one address: receipts and resets from your app, and tests to your own inbox.
- [Templates](https://sendocado.com/docs/api/templates.md): Sendocado API reference: Reusable content that steps, broadcasts and transactional emails can copy.
- [Sends and events](https://sendocado.com/docs/api/sends.md): Sendocado API reference: Every email the project sent, what happened to it, and the event stream by type.
- [Replies](https://sendocado.com/docs/api/replies.md): Sendocado API reference: Answers to your emails, received for you and tied to the email they answer.
- [Senders and domains](https://sendocado.com/docs/api/senders.md): Sendocado API reference: The email provider a project sends through and the domains verified with it.
- [Webhooks](https://sendocado.com/docs/api/webhooks.md): Sendocado API reference: Signed HTTP calls to your server when emails are delivered, bounce, get replies and more.
- [Images](https://sendocado.com/docs/api/images.md): Sendocado API reference: Images hosted for use in your emails.
- [Overview](https://sendocado.com/docs/api/overview.md): Sendocado API reference: A project’s numbers over the last 7, 30 or 90 days.
- [Errors](https://sendocado.com/docs/errors.md): Sendocado API errors: the error shape, every error type and status, and when to retry.
- [Rate limits](https://sendocado.com/docs/rate-limits.md): Sendocado API and MCP rate limits, the 429 answer, plan limits and sending pace.
- [Changelog](https://sendocado.com/docs/changelog.md): Changes to the Sendocado REST API and MCP server.