Setting up a product's email with your agent

Domain, DNS records, check, support@ and noreply@: the whole setup through the API or MCP, step by step.

When you start a new product, your AI agent can set up its email for you through MCP. You stay in charge of what it may do, and every step it takes is listed under Agent activity in the console.

Before you start

• Connect the agent to centomail: see Connecting an AI agent via MCP.
• Give the agent access to your DNS provider with its own credentials (for example a scoped API token). centomail never writes to your DNS; the agent does, with its access.

Ask the agent

A request like this is enough:

Set up email for tallyfor.app: add the domain to centomail, publish the DNS records it needs, verify it, and create support@ and noreply@ mailboxes.

The agent then:

1. Adds the domain (add_domain) and gets the exact records centomail needs: ownership TXT, MX, SPF, DKIM, DMARC and the optional ones.
2. Publishes the records at your DNS provider, with its own access.
3. Checks them (verify_domain). DNS changes can take a few minutes to show; the agent can check again until the domain is active.
4. Creates mailboxes (create_mailbox), such as support@tallyfor.app and noreply@tallyfor.app.

After that

• Mail to the new addresses lands in your one inbox, next to the rest of your mail.
• To let your app send through noreply@, give that mailbox its own sign-in in Console → Mailboxes and use the SMTP settings in IMAP and SMTP settings. Sending is priced per recipient, see Balance and billing.
• The domain page shows who sends mail as the domain once DMARC reports start arriving, usually within two days.