AI Agent & Automation Workflows

Use Sendmux attachment workflows without wasting model context on base64. Use when uploading, downloading, reading, forwarding, or sending email attachments through Sendmux MCP, CLI, SDKs, or direct HTTP, especially when choosing filepath vs presigned upload URL vs inline base64, reading inbound attachments with mailboxreadattachment, fetching short-lived downloadurl links, or attaching local files to outbound mail.

Use the Sendmux command-line interface for terminal-driven Sendmux work. Use when the user wants install commands, profiles, key-scope preflight, --json output, colon-namespaced Sendmux commands, request body/path/query/header flags, or CLI examples for Management, Mailbox, or Sending API operations.

Design and route Sendmux email workflows for AI agents, including skill installation, self-registration, secure agent credential-bundle storage, owner approval, and runtime email operations. Use when a user wants to give an AI agent its own inbox or email address, let an agent receive/search/triage/reply to mail, draft human-approved replies, send notifications, monitor mailbox state, or build email-based agent workflows even when the user does not mention Sendmux by name.

Sendmux setup, skill installation, API key validation, agent access, secure agent credential-bundle storage, and first-call guidance. Use when the user wants to install Sendmux tooling or skills, check whether an smxroot, smxmbx, or smxagent credential works, choose MCP vs CLI vs SDK, connect an agent to Sendmux email, configure auth, self-register an agent, or make the first harmless Sendmux API call from an agent, terminal, or application.

Work efficiently with one Sendmux mailbox from an AI agent. Use for reading, searching, counting, syncing, triaging, filing, deleting, threading, or replying from a mailbox with an smxmbx key or scoped smxagent token, especially when the user asks an agent to inspect an inbox, find relevant messages, mark messages, or continue from a prior mailbox sync state.

Manage Sendmux account-level resources with an smxroot key. Use for domains, mailbox provisioning, mailbox API keys, sending accounts, webhooks, billing, spend, delivery logs, incoming logs, metrics, and other team administration tasks; route mailbox reading, triage, sync, and replies to sendmux-mailbox-agent.

Configure Sendmux Model Context Protocol servers for AI agent clients, using hosted OAuth first when supported and secret-backed local env config otherwise. Use when the user wants to install sendmux-mcp, connect the hosted Sendmux MCP endpoint, run local stdio or HTTP MCP servers, set mailbox/management/sending key scopes, add bearer headers, or write MCP config for Claude Code, Cursor, Codex, VS Code/Copilot, Copilot CLI, Gemini CLI, Cline, or Windsurf/Cascade.

Send email with Sendmux, including owner-approved Sending-resource smxagent tokens from claim-token exchange. Use when the user wants to send one email, send multiple emails, choose single vs batch sending, add idempotency keys, include attachments, compare HTTP Sending API vs SMTP, or use Sendmux MCP, CLI, SDK, or direct HTTP for outbound email.

Choose the cheapest correct Sendmux surface and call. Use whenever a Sendmux task could be done through MCP, the sendmux CLI, an SDK, or direct HTTP and the user needs low-token, low-round-trip usage: batch sends, mailbox search/count/batch reads, sync deltas, cursor pagination, ETags, conditional requests, idempotency keys, attachment file transfer, or avoiding broad mailbox/log fetches.