# Sending > Sending is an MCP-native orchestrator for multichannel messaging (email, WhatsApp, Telegram). It exposes a developer REST API and MCP tools that let AI agents configure sending, marketing automation and hybrid cross-channel flows on their own. Email infrastructure runs on Amazon SES. Sending joins two worlds: the deliverability and developer-first API of a modern email provider, and multichannel marketing automation. What sets it apart: - **Automation-as-code with closed-loop autonomy**: agents create, activate and correct automations over MCP, inside server-side guardrails (OAuth 2.1, spend and volume caps, audit log). - **Hybrid cross-channel orchestration with cost arbitrage**: one flow can pick the channel (email, WhatsApp, Telegram) based on cost, consent and how reachable the contact is. - **First-party tracking**: HMAC-signed opens and clicks, with bot, Apple MPP and Gmail proxy classification, so the numbers mean something. ## For agents - [MCP endpoint](https://sending.dev/api/mcp): streamable HTTP. Auth with a bearer API key or OAuth 2.1 with dynamic client registration (RFC 7591). - [MCP server card](https://sending.dev/.well-known/mcp/server-card.json): server, transport and authentication, machine readable. - [Agent Skills](https://sending.dev/.well-known/agent-skills/index.json): task instructions (connect over MCP, send the first email, run a campaign, build an automation, use an agent inbox). The same files are readable as pages, one per skill, from https://sending.dev/skills. - [Credentials in prose](https://sending.dev/auth.md): how to authenticate, for an agent that reads. - [API catalogue](https://sending.dev/.well-known/api-catalog): RFC 9727 catalogue of the public APIs. - [OpenAPI spec](https://sending.dev/api/v1/openapi.json): the full v1 REST surface. - [Single REST plus MCP prompt](https://sending.dev/llms-full.txt): one reference to paste into an agent. ## Markdown Every public page has a markdown representation, in two interchangeable ways: append `.md` to the URL, or send `Accept: text/markdown`. The home page is `https://sending.dev/index.md`. English is canonical and lives at the root; Italian lives under `/it`. For example `https://sending.dev/docs/quickstart.md` and `https://sending.dev/it/docs/quickstart.md`. ## Documentation - [REST reference](https://sending.dev/docs/api/rest.md): Every REST endpoint grouped by area. Base https://sending.dev/api/v1 - [Email](https://sending.dev/docs/api/emails.md): Transactional email sending. - [Attachments](https://sending.dev/docs/api/attachments.md): Attach files to transactional email, campaigns, automations and agent inboxes. - [Agent Email](https://sending.dev/docs/api/agent-email.md): Email inboxes for AI agents: threads, replies, metrics. - [Webhooks](https://sending.dev/docs/api/webhooks.md): HMAC-signed notifications for email events. - [Allow / Block](https://sending.dev/docs/api/allow-block.md): Sender or domain rules for inbound mail on agent inboxes. - [Templates](https://sending.dev/docs/api/templates.md): Reusable content for campaigns, transactional sends and automations. - [Introduction](https://sending.dev/docs.md): REST API and MCP endpoint to send email, messages and orchestrate AI agents, on Amazon SES. - [Quickstart](https://sending.dev/docs/quickstart.md): Send your first email with an API key, via cURL or fetch. - [Official SDKs](https://sending.dev/docs/sdk.md): TypeScript and Python clients for the Sending API, generated from the OpenAPI spec. - [Authentication](https://sending.dev/docs/authentication.md): Bearer API keys and scopes. The workspace is always derived from the token. - [Domains and deliverability](https://sending.dev/docs/domains.md): Add and verify a domain, manage suppression and inbound receiving. - [Idempotency and errors](https://sending.dev/docs/errors.md): Send idempotency, error format and status codes. - [MCP overview](https://sending.dev/docs/mcp/overview.md): MCP endpoint, authentication and available tools. - [Install Sending in your agent](https://sending.dev/docs/mcp/clients.md): Add the Sending MCP server to Claude, ChatGPT, Cursor, VS Code and the other clients. - [Prompt for AI agents](https://sending.dev/docs/resources/ai-prompt.md): A single REST plus MCP reference to hand to an agent. ## Key concepts - **MCP (Model Context Protocol)**: Sending exposes MCP tools (sending email, managing contacts, building automations) behind OAuth 2.1 and scopes. Permissions come from the user-client binding, not from the token: MCP clients do not know our scope catalogue and usually request identity only. - **Channels**: email (Amazon SES, in production), WhatsApp (Meta Cloud API) and Telegram. Contacts carry a per-channel identity and per-channel consent. - **Automations**: graph flows (DAG) with triggers, event waits, conditions and send actions. A draft is published into an active version, and the DAG is serializable, so an agent can write one and read it back. - **Deliverability and compliance**: sending requires a verified domain, honours the suppression list, and demands an idempotency key on every send (in the body, minimum 8 characters, there is no `Idempotency-Key` header). - **Agent Email**: dedicated inboxes for AI agents (create, send, threads, replies) with HMAC-signed webhooks on events (mail received, delivered, bounced), allow/block lists by sender or domain, and per-inbox metrics. ## Resources - [Pricing](https://sending.dev/pricing): three products you can buy separately, transactional email by volume, marketing by contacts, agent inboxes. - [MCP clients](https://sending.dev/mcp): how to connect each MCP client, one page per client, plus the guardrails an agent cannot bypass. - [Send with your stack](https://sending.dev/docs/send-with): working send code for 30 frameworks, runtimes and automation tools, each with the mistake that costs half an hour there. - [Agent Skills as pages](https://sending.dev/skills): the five skills in HTML and markdown, same bytes as the files above. - [Agent Email](https://sending.dev/agent-email): inboxes for agents, with threading, signed inbound webhooks and allow/block rules. - [Guides](https://sending.dev/guides): comparisons with stated criteria and dated sources, including where other products beat ours. - [Sitemap](https://sending.dev/sitemap.xml): every indexable public page, in both languages. ## Notes - Application areas (dashboard, authenticated API, tracking endpoints) require authentication and are not meant to be crawled. - Canonical product domain: https://sending.dev.