Mailgentic

Plans and billing

Mailgentic is priced on two things: inboxes and emails. An email is one recipient; a message to three people counts as three.

Plan Inboxes Emails / month Overage Shield Price
Free 3 (shared domain) 3,000 none — sending stops at the limit Basic: authentication + spam $0
Developer 10 10,000 $2.00 per 1,000 Full: injection heuristics, DLP, caps, auto-suspend $20 / mo
Startup 150 150,000 $1.50 per 1,000 Full + human approvals, dedicated IP pools $200 / mo
Enterprise custom usage-based $1.00 per 1,000 Full + in-region classifier, SSO, SLA custom

Overage is billed monthly in arrears. Free is a hard stop; it never produces a bill.

What each plan includes

Protocols are never gated: REST, SMTP, IMAP, MCP, webhooks, SSE and WebSocket work on every plan including Free. Plans differ in how much control you get.

Free Developer Startup Enterprise
Own sending and inbound domains shared agents.mailgentic.ai only yes yes yes
Shield inbound verdicts (auth, spam, injection) yes yes yes yes
Shield outbound: DLP, hourly caps, recipient allowlist, auto-suspend — yes yes yes
Human approvals (held queue, tainted-thread holds) — — yes yes
AI auto-label and extraction — 100k tokens / mo 1M tokens / mo custom
Dedicated IP pool with automated warm-up — — one included as needed
Connected Gmail / Microsoft 365 inboxes — — yes yes
Message retention 30 days 90 days 1 year custom
Audit log view view view + export export, SIEM feed
Support community email priority SLA, SSO, DPA, data-region pinning, in-region Shield classifier

The free trial

Signup is self-serve and needs no card. Until you add a paid plan, the account runs with three guard-rails:

They exist so a brand-new account cannot spray mail from Mailgentic’s shared reputation. Adding a plan in Console → Billing lifts all three the moment the subscription is active.

Checking usage

curl "$API/v1/billing/usage"   -H "Authorization: Bearer $KEY"   # this month's metered usage
curl "$API/v1/billing/preview" -H "Authorization: Bearer $KEY"   # what this month will cost so far
curl "$API/v1/tenants/$TENANT_ID/usage" -H "Authorization: Bearer $KEY"   # per-tenant quota and rate usage

GET /v1/billing/export?format=csv&month=2026-10 returns a line-item export suitable for re-billing your own customers.

Method Path Scope Purpose
GET /v1/billing/plans read Available plans
GET /v1/billing/assignments read Which plan applies to the account and to each tenant
POST /v1/billing/assignments admin Assign a per-tenant rate card (for re-billing)
GET /v1/billing/usage read Monthly metered usage
GET /v1/billing/preview read Projected charges
GET /v1/billing/export read JSON or CSV export

Subscribing and managing payment

Plans are purchased through Stripe Checkout, from the console (Billing → Plans & upgrade) or via the API:

curl -X POST "$API/v1/billing/checkout" -H "Authorization: Bearer $ADMIN_KEY" \
  -H "Content-Type: application/json" -d '{"plan_id": "PLAN_ID"}'
# → { "url": "https://checkout.stripe.com/..." }

curl -X POST "$API/v1/billing/portal" -H "Authorization: Bearer $ADMIN_KEY"
# → { "url": "https://billing.stripe.com/..." }   # cards, invoices, cancel

Completing checkout assigns the plan and lifts the free-trial guard-rails. Subscription changes and cancellations in the Stripe portal are mirrored automatically.

Per-tenant rate cards

If you re-bill your own customers, assign each tenant a rate card with POST /v1/billing/assignments. Usage is then metered per tenant against that card and shows up separately in /v1/billing/usage and the export. Rate cards do not change what Mailgentic charges you; they are for your invoicing.

Enterprise

Enterprise plans add SSO, an SLA, a DPA, audit-log export, data-region pinning, an in-region Shield classifier, and a proof of concept on your own scenario, including the compromised-agent, automatic-stop drill, live on your data. Talk to us.