GPTMail now has an optional account dashboard for people who manage custom domains, use API keys, or submit partnership applications. It brings those assets together without turning the temporary inbox into a conventional permanent-mail account.
You can still open GPTMail, choose an address, receive a verification message, and leave without registering. The account is for continuity: it helps you return later and see the domains and developer assets that belong to you.
What the account dashboard includes
After signing in and choosing a unique username, the GPTMail account dashboard shows three groups of assets:
- public and private domains you added;
- API keys linked to your account, together with usage and remaining quota;
- friend-link applications and their review status.
The username is globally unique across GPTMail. It is separate from the display name supplied by a sign-in provider, so future sign-in methods can be attached without creating duplicate public identities.
Sign in with Cloudflare, without giving DNS access
The account currently uses Cloudflare for secure sign-in. This login confirms your Cloudflare identity, but it does not automatically authorize GPTMail to edit zones or DNS records.
Cloudflare automatic DNS setup is a separate, one-time authorization started from the domain form. That separation matters: signing in to view your dashboard does not silently grant DNS write access. If you prefer to configure records manually, you can continue copying the required MX target into your DNS provider yourself.
After the first sign-in, GPTMail asks you to choose a unique username. Once set, that username identifies the account even if more sign-in providers are supported later.
Keep track of public and private domains
The domain section shows whether a domain is public or private, whether it is active, and what GPTMail currently knows about its MX configuration. Pending setup, invalid MX records, inactive domains, and domains later deleted by an administrator are presented as different states instead of being silently removed from the account history.
For an active domain, you can request a fresh MX check directly from the dashboard. The result shows whether the authoritative records match the target expected by GPTMail. When a check fails, the dashboard keeps the error next to that domain so you do not need to search for a notification at the top of a long page.
The complete setup flow remains available on the custom-domain page. Public domains join the shared domain pool after validation. Private domains use a dedicated MX target and remain outside the public domain list.
See API-key usage before automation stops
The API section displays each linked key, its current status, usage for the current day, total usage, and remaining quota. Keys issued when a public domain is added can appear automatically. A key obtained elsewhere, such as through LDC Store, can also be linked manually.
Each API key can belong to only one GPTMail account. Linking a key does not consume quota, and it does not change the key itself. If a key is later deleted from the server, the dashboard keeps a historical entry marked as deleted so the disappearance is understandable rather than mysterious.
The full request format, authentication header, quota behavior, and endpoint examples remain in the GPTMail API documentation. The dashboard is a management view; it does not replace the API reference.
Follow partnership applications
If you apply for a friend link, the account dashboard records the application and its current review state. Approved, pending, rejected, or suspended applications remain tied to the same account, and an administrator's note can be shown when one is available.
Applications can still be submitted through the friend-links page. The account simply gives returning applicants a reliable place to check the result without depending only on a locally saved tracking code.
Start without an account and merge later
Registration is not a gate in front of GPTMail. You may add a public domain, receive an API key, or submit a friend-link application before signing in. Private domains are the exception: adding one requires signing in, because the domain belongs to your account and only that account can open its inboxes.
GPTMail associates those newly created assets with an anonymous resource session in the current browser. If you sign in later from that same browser session, eligible assets are merged into the account automatically.
This design avoids forcing a login at the moment you only want to test a feature. It also has an intentional boundary: a different browser or a cleared session cannot claim assets merely by knowing a domain name. Existing API keys can be linked separately after authentication, but a key already linked to another account cannot be taken over.
What the account does not change
An account does not make temporary mail permanent. Message retention still follows the service-wide retention window, and signing in does not preserve old inbox contents beyond that period.
The dashboard does not synchronize email bodies, verification codes, or recent-inbox history into the user profile. It manages ownership and status metadata for domains, keys, and applications. Private domains are where the account also grants mailbox access: a private domain you added opens without a password while you are signed in. Private domains added before account linking keep their password until you link them by entering it once while signed in.
The account is also not required for ordinary public inbox use. If your workflow is a quick, low-risk verification or software test, you can continue using GPTMail without creating an identity.
Who benefits most
The new dashboard is particularly useful when you:
- manage more than one public or private receiving domain;
- need to revisit an MX setup after DNS propagation;
- use a GPTMail API key in scripts or testing pipelines;
- want to know how much API quota remains;
- maintain a friend-link application over time;
- begin setup anonymously but want a durable management view later.
For a one-off inbox, nothing has become more complicated. For domain owners and developers, the pieces now have a home.
Get started
Open the account page, continue with Cloudflare, and choose your unique username. If you already added assets in the current browser, they should appear after sign-in. You can then refresh domain status, review quota, link an existing API key, or open the relevant setup page for the next action.
GPTMail will continue improving the account dashboard while keeping its original principle intact: registration should make ongoing management easier, not become a requirement for receiving temporary mail.