Email API Pricing Models: Predict Your Costs

Command references used in this guide: nylas demo email list, nylas init, and nylas auth list.

What pricing models do email APIs use?

Email APIs use 3 pricing models: per-message, per-connected-account, and usage-based. Per-message pricing charges for each email sent from your domain. Per-connected-account pricing charges a monthly rate for each mailbox the API can read and write. Usage-based pricing measures how much you use a specific resource, such as hours of recorded meetings. A vendor's pricing model shows what its product does.

You can't swap one model for another, because the products are different. A transactional API like Amazon SES sends from your domain and never sees a user's inbox, so it makes sense to charge per message. A contextual API like Nylas connects to mailboxes users already have (Gmail, Outlook, Exchange, and others) for two-way sync, so it charges per account. The email API comparison guide explains that product split in detail. This page explains how each model affects your bill.

How does per-connected-account pricing work?

Per-connected-account pricing charges a base monthly fee. The fee includes a set number of mailboxes, and each extra mailbox adds a monthly rate. The table below shows the plans on the Nylas pricing page (checked September 2026). Pro Annual has a 12-month commitment, and $43 is its monthly price.

Every plan includes both account types in one subscription. There is no separate calendar-only plan. A calendar-only account has access to calendar data but not email, so it has a lower rate.

Inside a plan, the cost grows in a straight line, so one spreadsheet formula can forecast it: base fee + (accounts above the allowance × rate). The table below applies that formula to email and calendar accounts at 5, 25, 100, and 1,000 accounts.

Pro Monthly costs less than Essentials from 26 accounts: $49 compared with $51. At 100 accounts, Pro Monthly saves $18.50 a month and Pro Annual saves $43.25 a month compared with Essentials. At high volume, compare these prices with Enterprise, which uses negotiated volume pricing. Message volume isn't part of the formula. A connected account that syncs 10,000 emails costs the same as one that syncs 50, so more email traffic doesn't raise the bill.

How does per-message pricing work?

Per-message pricing charges for each email sent. Vendors charge either a flat rate per thousand emails or a monthly plan with a set number of emails. Public pricing as of May 2026: Amazon SES charges $0.10 per 1,000 emails with no monthly minimum; SendGrid starts at $19.95/month for 50,000 emails; Postmark starts at $15/month for 10,000.

This model is cheapest for steady, high-volume sending. It costs more when volume is unpredictable, such as back-and-forth conversations. Sending 50,000 receipts a month costs $5 on SES. But the model only covers outbound mail from your own domain. A transactional provider can't read a customer's inbox, sync their calendar, or send as them at any price. That's why both models exist side by side.

How are Nylas Agent Accounts priced?

Nylas Agent Accounts use usage-based pricing. An Agent Account is a mailbox and calendar that Nylas hosts for an AI agent, with its own email address. Nylas measures four things: the number of accounts, storage, bandwidth, and sent emails. Each plan includes these amounts every month:

On Free and Essentials, these amounts are hard limits. The pricing page lists no Agent Account overage rates for those plans. On Pro, Nylas bills usage above the included amounts at these rates (monthly billing / annual billing):

• Extra Agent Account: $0.40 / $0.20
• Extra storage: $0.40 / $0.20 per GB
• Extra bandwidth: $0.80 / $0.50 per GB
• Extra sent emails: $0.80 / $0.70 per 1,000

Sent emails on Agent Accounts are a per-message charge. This is the one Nylas product where message volume changes the bill. For how Agent Accounts differ from connecting a user's own mailbox, read Agent Accounts vs delegated OAuth.

Which pricing model fits which use case?

Choose the model by the direction your email flows. If you only send from your domain, use per-message pricing. If you need two-way access to user mailboxes, use per-account pricing. For measured features like meeting recording or agent inboxes, use usage-based pricing. The table below matches common workloads to the model that bills them fairly.

Some products need both. For example, a SaaS app might send receipts through SES at $0.10 per 1,000 and sync support inboxes through a per-account API. Using two vendors for two jobs is normal. It usually costs less than forcing one model to cover both.

How do you estimate costs before committing?

With per-account pricing, you can estimate costs directly: count the mailboxes and apply the rates. The free plan supports up to 5 connected accounts for building and testing, so a working prototype costs $0. You can start even earlier with the nylas demo email list command. It runs the CLI against realistic sample data with no credentials.

# Explore with sample data — no account, no credentials
nylas demo email list

# Set up the real thing (free sandbox, up to 5 accounts)
nylas init

# Count the accounts you've actually connected
nylas auth list

5 accounts are enough for a small pilot: your own mailbox plus a few teammates testing with real Gmail and Outlook data for a few weeks. When the pilot needs more than 5 accounts, nylas auth list shows how many accounts you would pay for. Essentials covers 10 accounts for $15/month, plus $2.25 a month for each extra account. Above 25 accounts, Pro costs less.

What hidden costs should you check?

The price list doesn't show the whole bill. Check four items in the fine print: SLA eligibility, support tiers, overage behavior, and deliverability extras. The Nylas pricing page shows these directly. Free and Essentials include community support. Pro Annual adds Basic Support from the Nylas team. A guaranteed uptime SLA is part of the Enterprise plan, not the lower plans. Annual billing also adds features, not only a discount. Pro Annual turns on Bring your own Auth, bulk authenticate, and Hosted Scheduler whitelabel. Pro Monthly doesn't include them.

1. SLA eligibility: vendors often offer guarantees only on the top plan or with an annual commitment. Lower plans may have no SLA (see the SLA guide for what the tiers mean).
2. Support tiers: community or email support is the usual starting level. Faster response times and dedicated support usually need an annual or enterprise commitment.
3. Overage behavior: check if the vendor bills account #11 automatically or rejects it. Automatic billing keeps production running, but it can cause unexpected invoices. Essentials and Pro bill extra connected accounts and Notetaker hours at the rates above. Agent Accounts have hard limits on Essentials and are billed for extra usage only on Pro. The Free tier has no overage rates, so its 5 accounts are a hard limit.
4. Deliverability extras: per-message vendors charge extra for dedicated IPs and domain warm-up tools that the base plan excludes.

Add one number to any vendor comparison spreadsheet: the cost at 10× your launch scale. With per-account pricing, this number is easy to calculate. Tiered per-message plans can jump in price at a tier boundary. Find that jump in your spreadsheet before it appears on an invoice.

Next steps

• Best email API for developers — the full 6-vendor comparison this pricing breakdown plugs into
• Email API SLAs: uptime vs success rate — what the Enterprise uptime SLA actually guarantees
• Getting started — install the CLI and connect your first sandbox account
• SendGrid vs Nylas — a head-to-head of the two pricing models in practice
• Full command reference — every flag and subcommand documented