Use SMTPfast Without the Dashboard

smtpfast init signs you up or logs you in, activates a new account, adds a domain, sets its DNS records through Domain Connect when the DNS host supports it (or prints them), waits for verification and sends a test email to your own address. See the CLI page for its flags.

npx smtpfast init

smtpfast signup                                  # 1. account and first API key
smtpfast activate                                # 2. pay, request the free plan, or use an invite code
smtpfast domains add --domain mail.example.com   # 3. a sending domain
smtpfast domains start-cloudflare-connect <id>   #    DNS through Domain Connect, if the DNS is on Cloudflare
smtpfast domains verify mail.example.com --wait  # 4. wait for the records
smtpfast send --from [email protected] --to [email protected] --subject "Hi" --text "It works"

With an account already, smtpfast login gets a key by approving a code in the browser instead of signup.

smtpfast signup emails an 8-digit code; entering it creates the account and returns its first API key with the default scopes. The address goes through the same checks as the signup form, and an address that already has an account gets an email saying so instead of a code. The account has no password; set one with Forgot password on the login page if you want the dashboard later. The endpoints are POST /v1/cli/signup and POST /v1/cli/signup/verify, on the CLI page.

A new account is pending until it is activated, whether it was made on the website or in a terminal. There are three ways, and the key from signup works for each of them right away. Every other endpoint answers 403 until the account is active.

• Pay for a plan: a Stripe Checkout link that a person opens. The account is active once Stripe confirms the payment.
• Request the free plan with a sentence about what you will send. A person reviews it and emails you.
• An invite code, if you have one.

{
  "status": "pending",
  "plan": "free",
  "email_verified": true,
  "free_trial_requested_at": null,
  "rejection_reason": null
}

{
  "plan": "growth",
  "interval": "monthly"
}

{ "url": "https://checkout.stripe.com/c/pay/cs_live_..." }

{
  "use_case": "Password resets and receipts for our app at example.com.",
  "source": "search"
}

{ "requested": true, "message": "Invite request sent. We will email you when it is approved." }

{ "code": "SF-AB12-CD34" }

{ "status": "active", "plan": "free" }

Once the account is active, every part of the API works with the key: domains (with one-click DNS on Cloudflare), sending, webhooks, and billing for the plan, usage, invoices and plan changes.

Without a terminal the CLI asks nothing and prints JSON. Signing up takes two calls, so an agent can read the code from the email in between. A person still opens the Checkout link to pay, or the free-plan request is reviewed.

smtpfast signup --email [email protected] --send-only --json
# read the code from the email, then:
smtpfast signup --signup-id <signup_id> --code 4831-0927
smtpfast activate --plan growth --no-browser     # prints the Checkout link for a person to pay
smtpfast init --domain mail.example.com --test-email --json

Agents that speak MCP can use the hosted MCP server once there is an account, and the SMTPfast skill teaches an agent the API. The site map for AI tools is at /llms.txt.