EmailSeptember 13, 20267 min read

How to Give Meta Muse Its Own Email Address

How to give Meta Muse its own email address: create a Mermail API key, paste it into the Secrets tab, approve the connection, and Muse runs its own inbox. Five minutes, no code.

By Toan Nhu

Mermail hero: Meri mascot beside the headline Give Muse Its Own Email Address

Mermail gives AI agents a real inbox and a user-controlled Agent Wallet. Muse, Meta's personal AI agent, can own an email address of its own: ask it to get one, create a Mermail API key, paste it into the Secrets tab, approve the connection, and Muse is running its own inbox on mermail.app. The whole thing takes about five minutes and needs no code, because Muse writes its own connector to Mermail's API.

How do I give my Meta Muse agent an email address?

TL;DR

One message starts it. "Get yourself a Mermail email address."
One API key. Create it in the Mermail console, name it "Muse", paste it into the Secrets tab, not the chat.
One approval. Muse asks permission to share information with Mermail. You can make it a standing permission.
Muse picks the address unless you do. Ask for a specific name and it creates it if available.
It works alongside your Gmail connector. Gmail for reading your mail, Mermail for an address Muse owns.

How do I set up Mermail on Muse?

You need a Muse account (US only at launch) and a Mermail account. Mermail's free tier covers everything in this guide.

1. Ask Muse for an address. In your main chat, send: "Get yourself a Mermail email address." Muse replies with its plan: it will ask you to sign up for Mermail, create an API key, and hand it over.

2. Create an API key. Go to the Mermail console and sign up. Create a new API key, name it "Muse" so you can find and revoke it later, and copy it.

3. Paste the key into the Secrets tab. Muse opens a Secrets tab for the key. Paste it there. Don't paste API keys into the chat itself.

4. Approve the connection. Muse's request to share information with Mermail appears in the approval section on the right of the app. Approve it there. You can grant a standing permission for the site so Muse doesn't ask on every call.

5. Let Muse create its inbox. Muse creates an inbox and picks the address and display name unless you told it otherwise. It tells you the address when it's done.

6. Send a test. Ask: "Send an email from your Mermail address to me at [email protected]." Check your personal inbox. When it lands, the setup works.

7. Reply to it. Reply from your personal inbox, then ask Muse: "Did I reply?" It reads the reply in the same thread.

Where does the API key go?

In the Secrets tab, which stores it in Muse's secure credential store instead of the conversation. Meta's security design keeps credentials out of the agent's reach: the agent works with a stand-in token, and a separate service swaps in the real credential at the network boundary. A prompt injection that talks Muse into printing its secrets has nothing real to print.

Naming the key "Muse" matters later. If you ever want to cut Muse off from its inbox, delete that one key in the Mermail console. Your other keys and inboxes keep working.

What is the approval section for?

Every call Muse makes to an outside service goes through Sentinel, a separate permission agent on Muse's VM that Muse can't override. The first time Muse talks to Mermail, Sentinel asks whether Muse may share information with it, in the approval section on the right of the app. The request renders in the app UI, outside the chat, so a manipulated agent can't approve itself.

You choose how long the permission lasts. A one-time approval means Muse asks again next time. A standing permission for the Mermail site lets Muse send, check its inbox, and create new inboxes without interrupting you. If you'd rather approve each send, keep the shorter grant.

Can I choose the email address?

Yes. If you don't specify one, Muse picks the address and the display name. To choose, ask: "Create an inbox called brooke" or "Create an inbox called car-sale with the display name Brooke." If the name is available on mermail.app, Muse creates it. If it's taken, Muse tells you and you pick another.

Muse can hold more than one inbox. Muse organizes work into a main chat and side chats, and a separate address per side chat keeps each job's email in its own thread history: one for selling the car, one for the move, one for wedding vendors.

With a custom domain on a paid Mermail plan, the address can be on your own domain instead of mermail.app. Add the domain in the Mermail console, verify DNS, and Muse can create addresses on it.

What can Muse do with its own inbox?

Contact businesses as itself. Quote requests to movers, a special request to a restaurant, a follow-up on a refund. Replies come back to Muse's inbox, not yours, and your personal address stays off vendor mailing lists.
Sign up for accounts. Muse's Gmail connector filters verification codes out of your inbox by design, so it can't finish signups there. With its own address, Muse signs up and reads its own code.
Work from what you forward. Don't want to connect your Gmail at all? Forward Muse the order confirmation, the school form, or the contractor thread, and it works from that alone.
Join a thread. CC Muse's address on an email thread. It reads the history and follows along.
Catch alerts. Price drops, restock notices, and promo emails go to Muse's address. It surfaces the ones that matter.
Pay when a signup or purchase needs it. Mermail pairs the inbox with a user-controlled Agent Wallet, so Muse can finish a paid signup or a checkout instead of stopping at the payment form.

Gmail is not built for agents

Gmail was built for a person reading their own mail, not for automations and bots acting on their own. Mermail is built for agents: inboxes created by software, owned by the agent, with full thread history. The two do different jobs, so keep the Gmail or Outlook connector if you want Muse to search and triage your own mail. It does that well, across multiple accounts. Mermail covers the jobs the connector isn't built for: an address Muse owns, sends that don't come from you, and mail other people can send straight to Muse.

One thing not to do: don't ask Muse to open a browser and create a Gmail account for itself. Google's account policy prohibits using bots to create accounts, and agent-created Gmail accounts have been disabled within days.

Mermail gives your agents real inboxes. Create inboxes via API, send and receive email with zero complexity, and add a user-controlled Agent Wallet when your agent needs to actually pay. Free to start.

FAQ

How do I give Meta Muse an email address?

Message Muse "Get yourself a Mermail email address." Create an API key named "Muse" in the Mermail console, paste it into the Secrets tab Muse opens, and approve the connection. Muse creates its own inbox on mermail.app. Ask it to email you to confirm.

Is there an official Mermail connector for Muse?

Not a built-in one. Muse writes its own connector to Mermail's API when you ask it to get an address. Setup takes about five minutes and needs no code.

Where do I put the Mermail API key in Muse?

In the Secrets tab Muse opens during setup, not in the chat. Name the key "Muse" in the Mermail console so you can revoke it on its own later.

Can I pick my Muse's email address?

Yes. Ask Muse to create an inbox with a specific name. If it's available on mermail.app, Muse creates it. Otherwise Muse picks one for you.

Does Muse ask before sending from its Mermail inbox?

The first connection needs your approval in the app's approval section. You can make that a standing permission for Mermail, or keep shorter grants if you want to approve more often.

Is Mermail free for Muse?

Mermail's free tier covers the setup and testing in this guide. Paid plans add custom domains, higher volume, and the Agent Wallet.

Can Muse also pay for things it signs up for?

Yes. Mermail's Agent Wallet is a user-controlled wallet Muse can spend from with your limits in place, so a signup that needs a card doesn't stop the workflow.