xhelo

The emails brands send, in the order they send them.

xhelo keeps the email flows of established brands: welcome series, onboarding, trials, promotions. Search them in the app, or let Claude Code, Codex or Cursor pull them into the email you are writing.

Sign in with your email Set up your agent

Free to start. New accounts get 200 credits for the API. Browsing in the app does not use credits.

Dithered pixel illustration of an old computer showing an email on its screen

What is in the library

Single emails, cleaned

Screenshot on desktop and phone, the text, and the sanitized HTML. Tagged by goal, offer, tone and lifecycle stage.

Whole journeys

We sign up to a brand and record what arrives: which email came first, how long after, and whether it looks triggered by the signup or sent to everyone.

Gaps shown, not hidden

Brands can fail to deliver and our own mailbox can miss mail. Every journey says what was observed and where it might be incomplete.

What a journey looks like

Each email sits on a timeline measured from the moment the signup was confirmed. Below is a made-up example of the layout.

Illustrative mock, not real brand data
  1. Day 0+2m
    triggered 96%welcome

    Welcome to Brightside. Confirm your email

    Brightside Coffee Co.

  2. Day 1+1d 2h
    triggered 88%onboarding

    Your first brew guide

    Brightside Coffee Co.

  3. Day 3+3d 9h
    broadcast 74%promotion

    Free shipping ends tonight

    Brightside Coffee Co.

  4. Day 4gap
    Observation gap, 7 hours. Our mailbox check failed in this window, so emails may be missing here.
  5. Day 6+6d 1h
    unknownfeedback

    How was your first bag?

    Brightside Coffee Co.

Who it is for

Marketers and solo founders

You are writing a welcome series or a launch email and want to see how brands that do it well actually do it: timing, length, offer, tone.

People who work with coding agents

Your agent can look things up while it drafts. It gets cleaned text, tags and journeys, marked as third-party content so it is treated as data.

Use it from your agent

Create an API key in the app, put it in XHELO_API_KEY, then add the server.

Claude Code

claude mcp add --transport http xhelo https://xhelo.cc/mcp --header "Authorization: Bearer $XHELO_API_KEY"

Codex

[mcp_servers.xhelo]
url = "https://xhelo.cc/mcp"
bearer_token_env_var = "XHELO_API_KEY"

Cursor

{
  "mcpServers": {
    "xhelo": {
      "url": "https://xhelo.cc/mcp",
      "headers": { "Authorization": "Bearer ${env:XHELO_API_KEY}" }
    }
  }
}

Full agent docs, tools and credit costs

Start with the library

Sign in with your email