Let an AI Agent Buy and Set Up Email for You

Most software still assumes a person is sitting at the keyboard. You pick a plan, enter payment details, and work through a setup wizard. If an AI assistant is doing work for you, it normally has to stop and ask you to finish those steps.

TrekMail lets approved AI agents buy a plan and complete the setup work while the account owner keeps control of access, payment credentials, and later subscription changes.

Start with the offer. Read https://trekmail.net/ai-agents/offer.json for current prices, supported products, and the endpoints an agent should use. Treat the amount in the payment challenge or checkout as the final amount.

What this actually looks like

Say you ask your assistant to get a mailbox running for a new project. It reads the machine-readable offer, creates the account, buys the plan, adds the domain, retrieves the DNS records, waits for verification, and creates mailboxes when its token and plan allow those actions.

The account-creation flow starts with an email-verification-credit purchase. A mail plan, Drive Storage Add-on, and White Label subscription are separate products. After an agent buys a mail plan for an account it created itself, it must reissue its agent key before using the newly available plan scopes. The old key is revoked as part of that exchange.

You are not cut out of the process. TrekMail sends a claim link to the email address supplied at account creation. Use it promptly to set up normal dashboard access and verify that you control that address.

Who pays, and how

Autonomous payment uses credentials supplied by the payment system, not your dashboard password. One-off credit purchases use a single-use payment token. Recurring subscriptions use a payment-method credential instead, because a single-use token cannot fund later renewals.

Your payment provider controls any spending rules attached to its credentials. TrekMail also checks the product and amount on the server and applies account-level per-charge, daily, and monthly caps. These controls reduce risk, but they do not replace reviewing the agent and its payment-provider permissions.

What it can and cannot buy

The offer is the source of truth for current prices and purchase details. An agent can buy email-verification credits, a mail plan, extra Drive storage, and White Label branding through their separate purchase flows.

The autonomous purchase endpoints do not provide cancellation, downgrade, resize, or general subscription-change operations. Use the dashboard for those decisions, where the account owner can review the resulting capacity, price, billing period, and data effects.

Buying is not the same as a discount

A checkout you complete yourself may include a free trial or promotional code. An autonomous agent purchase is full price and does not apply a trial, coupon, or proration. If a human checkout option matters to you, complete that purchase yourself and let the agent handle the non-billing work afterwards.

Sending email takes a little longer

Once the account exists, an assistant can prepare most setup work right away. Sending is the exception.

A new domain cannot send until the DNS records shown by TrekMail are published and verify. Its initial sending allowance can also be lower than the plan limit while the domain establishes a sending history. Treat a successful DNS check and the domain's current sending status as the completion signal, rather than assuming that account creation alone makes mail ready to send.

Staying in control

Three things keep you in charge.

The email. An agent-created account sends a claim link to the address it was given. Follow it to take over dashboard access and verify the address. Email-verification rules can block sending for accounts that remain unverified, so do not treat the claim email as optional.

The payment credential. Keep the payment credential separate from the agent's API token and give it only the limits your payment provider supports. Do not paste it into a general-purpose agent prompt.

The key. An assistant works through an API key tied to the account. Revoke the key in the dashboard to stop its API access. A key issued during autonomous signup can be reissued only for that same agent-created account; a human-granted connector token cannot widen itself.

Getting started

If you already use TrekMail with an assistant, do not assume that a token which can read billing can also make a purchase. Autonomous payment needs the separate billing:autopay scope. Check the offer before adding that scope or payment credential.

If you are starting from scratch, point an agent at https://trekmail.net/ai-agents/offer.json first. It can use the returned endpoints for the purchase and setup work.

Either way, keep the human account owner in control of dashboard access, payment credentials, DNS, and any later subscription changes.

Safest handoff sequence

1. Have the agent read the offer and return the products and endpoints that are enabled.
2. Give it only the payment credential and API scopes needed for that one task.
3. Ask it to return the account ID, payment reference, plan status, and any DNS records that still need publishing. Do not ask it to report that email is ready until the domain's DNS status confirms it.
4. Use the claim email to take over dashboard access, then review the token list and revoke or replace any credential that is no longer needed.