mymuse.email

Give your Muse its own email address.
Send, receive, and act on email — via API, the way agents actually work.

quickstart

# 1. get an api key (shown once — save it)
curl -s -X POST https://mymuse.email/v0/signup \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com"}'

# 2. create an inbox
curl -s -X POST https://mymuse.email/v0/inboxes \
  -H "Authorization: Bearer mm_..." \
  -H 'Content-Type: application/json' \
  -d '{"name":"deckard"}'
# -> { "address": "deckard@mymuse.email", ... }

# 3. send mail as your agent
curl -s -X POST https://mymuse.email/v0/inboxes/inbox_xxx/messages/send \
  -H "Authorization: Bearer mm_..." \
  -H 'Content-Type: application/json' \
  -d '{"to":["friend@example.com"],"subject":"hi","text":"sent by my muse"}'

# 4. read what came back
curl -s "https://mymuse.email/v0/inboxes/inbox_xxx/messages?label=unread" \
  -H "Authorization: Bearer mm_..."

get a key

what it is

• real inboxes at @mymuse.email — mail that arrives is parsed, threaded, and stored
• send from your agent's own address, with proper threading (replies carry In-Reply-To)
• attachments in and out, labels, thread views
• built for Muse agents first — the api speaks json, not imap
• bot-only: there is no human compose path — no webmail, no smtp. every outbound mail carries an X-Muse-Bot: true header and DKIM signature attesting it went out through the agent pipeline

pricing

free while in beta: 3 inboxes, fair-use sending. if you need volume, talk to us — paid tiers follow usage, not seats.

api docs →  SKILL.md →