Start in the portal. Run in Claude or Codex.

Portal-first onboarding with a Mailionaire-issued bearer token for Pax8-backed tenant setup, consent, install, and MCP execution.

Open portal Read docs

Why this alpha exists

Small customer surface, durable operational core.

The private alpha is deliberately narrow: portal for readiness, MCP for execution, durable orders and jobs, redacted logs, and one controlled asynchronous execution path. Mailionaire still assists the underlying setup so the customer surface stays honest and small.

Portal shows Pax8 connection, per-root-domain tenant state, consent, install path, and recent jobs in one place.

Tenant setup stays pinned to approved root domains and one selected default Pax8 company.

Preview returns a durable preview_id before execute can consume quota.

Execute returns fast with a job_id while long-running provisioning continues asynchronously.

Status, logs, and recovery remain customer-visible through one narrow control surface.

$199/mo3 provisionings per weekClaude Code and Codex

Start here

Portal is the primary onboarding surface.

Start with the Mailionaire-issued bearer token, then follow the staged customer journey in the portal. Docs remain reference material after that.

Connect Pax8
Start in the portal and connect Pax8 so the product can load company choices.

Order the tenant
Choose one default Pax8 company for the portal, then place the tenant order for each approved root domain inside the portal.

Grant consent
A tenant admin completes Microsoft admin consent for the approved root domain before the first real run.

Install the MCP
Once tenant and consent are ready, install the endpoint in Claude Code or Codex with the issued bearer token.

Run preview, then execute
Execution still happens in the MCP client. Once the portal is ready, run preview first, then execute, then follow status, logs, audit, and recovery.

Install

Install after tenant and consent are ready.

Claude Code and Codex use the same bearer token and the same public MCP endpoint.

Claude Code

read -rsp "Mailionaire MCP token: " MAILIONAIRE_MCP_TOKEN; echo
claude mcp add --transport http mailionaire https://api.mailionaire.ch/mcp --header "Authorization: Bearer ${MAILIONAIRE_MCP_TOKEN}"
unset MAILIONAIRE_MCP_TOKEN

Codex

read -rsp "Mailionaire MCP token: " MAILIONAIRE_MCP_TOKEN; echo
export MAILIONAIRE_MCP_TOKEN
codex mcp add mailionaire --url https://api.mailionaire.ch/mcp --bearer-token-env-var MAILIONAIRE_MCP_TOKEN

Reference

Docs answer questions after portal readiness.

Customer portal

Primary onboarding surface for Pax8, tenant, consent, install, and recent-job readiness.

Docs overview

Reference for the shipped MCP tools, recipes, artifact pack, and recovery model.

Trust packet

Security, subprocessors, legal framing, incidents, and customer-facing data handling.

Trust posture

Security and control stay first-class product constraints.

No raw customer secrets in customer-visible logs, cache, or state.

Customer operational secrets are stored encrypted and referenced by scope, not copied into artifacts.

Bearer tokens are hashed at rest and alpha rotation remains manual.

Every state-changing action appends a durable audit_log event with object ids and actor context.