email59

Gmail cleanup

Years of old email in Gmail? Clear it in three steps.

Most of a full Gmail is mail nobody opens again: old shop offers, delivery updates and social media alerts. email59 finds it, shows you what it found and moves only what you pick to Trash.

It reads dates, senders and subjects. Never the body of an email.

  1. 1. Sign up and connect GmailSign in to email59, then connect your mailbox.
  2. 2. Let email59 look through itWhen you're done, one button deletes what email59 saw.
  3. 3. Pick what goesGroups that are safe to delete, with counts and examples. One click moves them to Trash.

✉New ยท Mailbox for your business

A real inbox at you@email59.com.

Keep work mail out of your personal inbox. Pick an address and it's yours: read, answer and write mail on one page, and open photos and attachments right there. Nothing to set up or install.

2 mailboxes free, 5 GB each. 100 mailboxes for only $10 a month.

  1. 1. Sign in and pick an addressorders@, hello-yourshop@, your own name.
  2. 2. Mail arrives on one pageInbox, Sent, Spam and Trash, with search.
  3. 3. Answer from the same addressReplies come back to your inbox.

@Deep email check

Is an email address real? Run a deep check.

Before you send an invoice or save a new customer, check the address. You get a score from 0 to 99 and the reasons in plain words. No email is sent to it.

No sign-up needed. Also an API and an MCP tool.

  • Typos and made-up namesIs it written the way Gmail, Outlook and others allow?
  • Can it get mail at all?Whether the part after the @ is set up to receive email.
  • One score, plain reasonsEach check is listed with what it found.

</>For people building an app

Email in your app before you own a domain.

One call to sign up, one call to send. No DNS records, no account review, no SMTP server. Sign-up codes, password resets and alerts go out from yourapp@email59.com.

Plain HTTPS and JSON. Nothing to install.

  • No domain, no DNS, no reviewPick a name and mail goes out from that name at email59.com.
  • Bots sign up on their ownAn agent asks for a code, reads it and gets a key. The MCP server is built in.
  • For the emails people count onCodes, confirmations, receipts and alerts, with unsubscribe links handled.

Email router

Email in your app before you own a domain.

One call to sign up, one call to send. No DNS records, no account review, no SMTP server. Your sign-up codes, password resets and alerts go out from yourapp@email59.com while your app is still on a preview address.

Bots and agents can sign themselves up. The MCP server is built in.

No domain, no DNS, no review.

Most email services want a verified domain, SPF and DKIM records and a human review before your first send. Here you pick a name, and mail goes out from that name at email59.com.

Bots sign up on their own.

An agent asks for a code, reads it and gets a key, with no person in the loop. Or it connects to the MCP server at /v1/mcp and calls send_email.

Built for the emails your users count on.

OTP codes, sign-up confirmations, newsletters, and alerts like "your export is ready" or a missed-payment notice.

Code samples

Send your first email.

Each sample makes one HTTPS call to /v1/send with your key in the EMAIL59_KEY environment variable. "from": "yourapp" sends as yourapp@email59.com. Get your key on your account page.

import json, os, urllib.request

req = urllib.request.Request(
    "https://email59.com/v1/send",
    data=json.dumps({"from": "yourapp", "to": "user@gmail.com",
                     "subject": "Welcome", "text": "Thanks for signing up."}).encode(),
    headers={"Authorization": "Bearer " + os.environ["EMAIL59_KEY"],
             "Content-Type": "application/json"},
)
print(urllib.request.urlopen(req).read().decode())

Why "router"

email59 is a router, not a mail server.

We don't run our own mail servers or write our own sending code. email59 takes your send call and routes it to an established sending provider, then adds what small apps and agents need on top: sign-up without a domain, sign-up for bots, an MCP server, unsubscribe links and lists, a blocklist and address checks.

Like other routers, we pass the provider's rate on to you instead of marking it up: paid credits are a one-time purchase, last until used, and there is no subscription. How credits work. More providers can sit behind the same endpoint later; your code keeps calling it unchanged.

How it works

Three calls. No SMTP, no deliverability setup.

1

Sign in

Sign in with osec.one (email code, Google or Apple) to get your API key. Bots can do the same with one POST. Nothing to set up: mail goes out from email59.com.

2

Send

Codes and alerts go through /v1/send. Newsletters go through /v1/campaigns. We check every address before it counts against your day.

3

Watch it work

Every send returns an id. Check your account for what went out today, and keep unsubscribes and blocked addresses in one place.

Features

Small, plain and built for small volume.

One-time codes and alerts

Send OTP codes, transactional alerts and missed-payment notices with one POST. Each one is a plain JSON call.

Lightweight, no SDK

Plain HTTPS and JSON. Use the standard HTTP client in Python, JavaScript, PHP, C# or Go. Nothing to install.

Marketing campaigns

One request sends a campaign to up to 1,000 people. The campaign provider adds the unsubscribe link and handles opt-outs.

Unsubscribe lists

Opt-outs are kept per list or for all lists. Unsubscribed people are skipped on every later campaign.

Blocklist

Block single addresses or whole domains for your account. Blocked recipients never count against your day.

Email validation

Syntax, disposable providers, role addresses such as info@, and whether the domain takes mail (MX).

Mailbox

A real inbox at an email59.com address: read, answer, write and delete on one page, attachments included. Pick an address.

Gmail cleanup

For your own mailbox: find years of old notifications, Promotions and no-reply mail and move them to Trash in one go. Clean up Gmail.

Deep address check

Before you send, check an address in depth: format, provider rules, MX, SPF, DMARC and DKIM, with a score. Try it.

Bot-first API

Plain JSON, bearer keys, OpenAPI at /docs. Agents can sign up, send and check balance themselves.

For bots

Bots welcome. Sign up and start sending on your own.

Every agent, script and CI job can use email59 without a person in the loop: sign up with an email code (or one signup call), get a key, then send. Agents can connect to the MCP server at https://email59.com/v1/mcp. Read llms.txt for a short, machine-friendly description.

agent steps
POST /v1/auth          {email}                    -> code emailed to you
POST /v1/auth          {email, otp}               -> {session_key} (new emails are signed up)
POST /v1/send          {from, to, subject, text}  -> {id, remaining_today}
POST /v1/campaigns     {from, subject, html, recipients[]} -> {campaign_id, accepted, rejected}
POST /v1/validate      {email}                    -> {verdict}
GET  /v1/account                                  -> {daily_limit, sent_today, remaining_today, credits_remaining}

Articles

Short reads on how email really works.

Eighteen posts with bullet points: the history, the blocklists that decide delivery, spam filters and what they cost, and the numbers.

History

Email is older than the web. Here are nine frames of how it changed.

Deliverability

The secret lists that decide whether your email exists

Self-hosting

Why nobody can run their own mail server anymore (almost)

All 18 articles

Start sending in minutes.

No domain to buy first. Sign in, copy a sample and send your first email.