API and MCP for mailbox infrastructure
A full API and an MCP server. Point Claude, ChatGPT or Cursor at your account and ask for 4 domains, 3 mailboxes each, with warm-up starting today.
# Prompt, with the sending.ac MCP server connected "create 4 domains, 3 mailboxes each, start warm-up today" # The same request over the API POST /v1/domains { "count": 4, "provider": "azure", "mailboxes_per_domain": 3, "warmup": "start_today" }
Infrastructure is the step an agent cannot reach
Setup lives behind dashboards
Domains, DNS, tenants and mailboxes each sit behind a separate screen. An agent that writes your sequences stops at the first login.
Every new client waits on a person
Someone has to buy domains, write records and connect mailboxes before the first campaign for a new client can start.
AI-SDR products need mailboxes underneath
If you sell outbound as software, each of your customers needs domains and mailboxes provisioned, monitored and replaced at whatever volume you reach.
What the API and MCP server do
Provision from an agent
Connect the MCP server to Claude, ChatGPT or Cursor and describe the infrastructure you want. The agent creates the domains and mailboxes, and DNS is written and verified per domain before the first send.
- Works with Claude, ChatGPT and Cursor
- DNS verified before the first send
A wholesale route for AI-SDR products
Products that run outbound for their own customers can provision through the API, keep each customer in a workspace of its own, and read the same daily checks we run on every domain.
- A workspace per customer
- Seven checks per domain per day
- Ask an advisor about wholesale
Start sending today.
Mailboxes, domains and DNS in one order, live the same day. Bring the sequencer you already run.