# How to give your AI agent an email address on your domain Canonical URL: https://bangermail.com/blog/set-up-email-new-domain-ai-agent/ Give your AI agent an email address on your domain by creating a real mailbox in Banger and connecting the agent through MCP. Your agent can guide DNS setup, verify the domain and help test sending and replies. Banger is an AI-native email platform for businesses. It combines real mailboxes, transactional email and marketing automation in one system, and lets AI agents like ChatGPT and Claude operate it through MCP and a REST API. You need authority over the domain. Publishing depends on authorized DNS access; the agent should show the exact records and any required human action instead of assuming it controls your registrar. The goal is a company address that can receive mail and support your product's sending. Keep that goal concrete: one product domain, one useful mailbox, and a test you can verify before a launch audience is involved. ## Which DNS records does your agent email address need? **MX** tells other mail servers where to deliver incoming email for a domain. If you want people to reply to a company mailbox, the receiving route matters. Do not confuse mailbox MX with a sending service's return-path MX; Banger's setup distinguishes those records. **SPF** describes which servers are authorized to send for the domain used in that authentication check. Use the value Banger prepares for your configuration. Guessing an SPF value from a tutorial for another setup can leave you with a record that does not match your sending service. **DKIM** adds a cryptographic signature to outgoing mail. The matching public key is published in DNS so receiving systems can check the signature. Publish the exact selector and value from your setup, including the record type Banger specifies. **DMARC** connects authentication to the visible From domain and states a policy for messages that fail the relevant checks. Banger requires a reject policy for new Banger From domains. Root-domain policy can affect other legitimate senders, so review the scope before publishing it. Authentication is a setup requirement, not a guarantee of inbox placement. Recipients still need to expect the email, and you still need to monitor the results. The [deliverability guide](/blog/email-deliverability-new-domain/) covers that next stage. ## How do you create the address and prove it works? ### 1. Connect the assistant and identify the domain Use the [MCP guide](/banger-mcp/) to connect Banger with scoped OAuth. Tell the assistant the exact domain, the product it belongs to, and whether it already receives or sends mail anywhere else. Try: “Set up company email for my new product on this domain. Inspect the current setup, prepare the complete DNS bundle, and show me any conflicts before changes. I need a support mailbox and product sending.” Calling a domain “new” should not replace inspection. You may already have verification records, another sender, or a receiving configuration from an earlier experiment. Ask the agent to preserve working services and identify conflicts explicitly. ### 2. Review the complete DNS bundle Banger prepares receiving and sending records together. Ask the assistant to list each record's host, type, value, and purpose. If the bundle is incomplete, finish preparation before asking the DNS owner to publish it. Review existing inbox records before changing MX. Review existing SPF and DMARC configuration before introducing new policy. In particular, do not publish a second DMARC record or overwrite an existing policy without understanding the conflict. For the root domain, identify every legitimate sender using that visible From domain. A policy change can have a wider effect than the one product message you are trying to configure. Banger's setup calls for this review rather than treating root policy as a harmless checkbox. ![Four foundations represent receiving routes, sender authorization, signatures, and policy beneath a company email envelope.](/assets/blog/set-up-email-new-domain-ai-agent/inner.webp) ### 3. Publish through an available path If supported DNS automation is connected, the agent can use it to publish the records. Otherwise, use guided entry or a handoff containing the exact records for whoever controls DNS. Never paste provider secrets into the conversation to force a shortcut. Check how your DNS provider expects hostnames to be entered. Compare the saved record with Banger's required hostname and value after publishing. Confirm that the published DNS matches the requested configuration. Existing-service replacements require the appropriate human migration approval. Moving receiving email is a different decision from adding authentication for a new sender. Keep those changes visible and deliberate. ### 4. Verify and distinguish pending states Ask the agent to run verification after the approved records are saved. If records remain pending, inspect the returned details. A recently saved record may still be propagating, but an incorrect hostname or value needs a correction. When all records are verified but readiness is still pending, inspect provider activation status. Do not repeatedly rewrite correct DNS records because another activation step has not finished. Ask the assistant to report the actual state and its last check. This distinction keeps setup from becoming a loop of unnecessary edits. “DNS missing,” “DNS verified,” and “sending ready” describe different points in the process. ### 5. Create mailboxes and prove the result Create the company mailbox you need and test receiving as well as sending. Banger's setup includes a real round-trip activation check. Follow the returned workflow and inspect the evidence rather than declaring success because the DNS screen looks complete. Use a recipient you control for your own first message. Check the visible sender, reply destination, links, and delivery status. Then connect application-driven email using the [API reference](/docs/api/) or prepare a [welcome Journey](/blog/saas-welcome-email-sequence/) through your agent. ## How much does an agent email address cost? Inboxes are free and unlimited on every plan. Free includes 3,000 monthly sends with a 100-email daily cap; sends beyond that daily cap go out the next day. Paid plans refuse sending past their monthly allowance until renewal or upgrade, without overage or usage fees. Check [pricing](/pricing/) before scheduling the launch. Separate mailbox names can help people recognize support and product messages, but they do not multiply the workspace's allowance or remove suppressions. ## Which email address should you give your agent? Choose an address that makes its purpose clear to customers and to the people who share the workspace. A support mailbox can receive product questions; a newsletter reply address can collect feedback on campaigns. You can use separate mailboxes when the work needs separate context without creating a new sending allowance for each one. Decide who will read unresolved replies. An agent inbox is useful only if the business has a path for conversations the agent cannot finish. Give the assistant approved product information and a clear instruction to prepare drafts or flag questions when a response requires a person's judgment. For a domain that already hosts company email, inspect the receiving setup before changing MX. You may need a planned migration or a separately configured subdomain. Ask for the exact effect of the proposed DNS changes; adding a sender and moving the company's incoming email are separate decisions. ## How do you connect the address to your AI assistant? Use the client guide for [ChatGPT](/agents/chatgpt/), [Claude](/agents/claude/), [Grok](/agents/grok/), [Hermes](/agents/hermes/) or [OpenClaw](/agents/openclaw/). The remote Banger endpoint is `https://api.bangermail.com/mcp`. Complete OAuth for the intended workspace, then ask the agent to inspect the mailbox and its current readiness. > Help me give my agent a support address on this domain. Inspect existing receiving services first. Show the DNS records and any migration impact, then guide verification. Create the mailbox after the prerequisites are ready and prove that a test message and its reply reach the intended places. The address belongs to the business workspace, so its usefulness should survive one chat session. Verify that a person can open the mailbox, see the conversation and continue the work. The [email for AI agents overview](/email-for-ai-agents/) explains how inboxes connect to product email, Broadcasts and Journeys. If you are choosing an inbox provider, the [Banger and AgentMail comparison](/compare/agentmail/) covers receiving, agent access and pricing before you connect your domain. If you later automate follow-ups, review their actual triggers and audience. A working address establishes identity and receiving; it does not itself authorize every message the agent might propose. Banger's first Journey activation and material changes require a person to decide the Approval. Create your agent's email address with Banger. ## FAQ ### Does my agent automatically control my DNS provider? No. Publishing depends on supported, authorized access. Otherwise Banger provides guidance or a handoff for the DNS owner. ### Is MX enough to send authenticated email? No. Receiving routes and sending authentication serve different purposes. Publish and verify the complete setup Banger prepares. ### Should I keep editing records while activation is pending? Only correct records that the returned checks show are wrong. If DNS is verified, inspect activation status instead of repeatedly changing working records. ### Does verified DNS guarantee delivery to the inbox? No. It establishes the relevant configuration. Consent, message purpose, recipient response, and sending behavior still matter after setup. ### Can the agent receive replies at its own address? Yes. Banger provides real mailboxes on your domain that an agent can read and reply from through the connected tools. Test the receiving route as well as outbound sending before using the address with customers. ## Sources and setup references - [Banger MCP connection](/banger-mcp/) and [email for AI agents](/email-for-ai-agents/). - [Banger API documentation](/docs/api/) and [pricing](/pricing/).