primitive.dev vs. Nylas

Nylas is an email, calendar, and meeting API whose core model connects to users’ existing accounts — syncing to a user’s Gmail, Microsoft 365, Exchange, or IMAP inbox via OAuth.^[1] It has since added Agent Accounts: hosted mailboxes an agent provisions with one API call and no OAuth^[4] — per-account-billed identities inside the Nylas platform, whose inbound path is webhooks back to a service you host. primitive.dev gives the agent the whole loop: its own address, a two-way conversation in one call, and your code running on every inbound message — usage-based, with no per-agent fee.

1. Own the address and the loop, not a connected account

Nylas’s heritage is connecting to a person’s existing inbox: “Users authenticate through secure OAuth flows for supported providers.”^[1] Its Agent Accounts drop that OAuth step and host a mailbox for the agent,^[4]which closes part of the gap — but both are identities that live inside Nylas’s connected-account platform and are billed per account.

primitive.dev issues the agent its own receivable *.primitive.emailaddress with one API call — inbound MX, SPF, DKIM, DMARC, and bounce handling managed for you — and pairs it with the agent loop a mailbox alone doesn’t give you: send-and-wait in one call, and your code running on every inbound message. The agent is the mailbox owner, with no per-agent fee.

2. Usage-based, not per-connected-account

Nylas layers per-account charges on top of a monthly plan — “you are billed a per-account rate for each additional account”^[2] — on the order of $0.20 per additional account each month past the accounts a plan includes (its Full Platform plan bundles 20). It is a small number, but it is still a per-identity line item that grows with every agent, and Agent Accounts are per-account identities inside that same platform.^[4] primitive.dev is usage-based with a free Developer tier and no per-account component, so spinning up the hundredth agent address costs the same as the first.

3. Agent-native primitives, not a sync layer

Nylas gives you a unified sync API over existing inboxes.^[3] primitive.dev does email only, by design — and builds the agent’s whole runtime around it: a one-call primitive chat send-and-wait verb, hosted Functions that run your code on every inbound message, programmable routing and filters, durable Memories, agent templates, an in-agent MCP App, and payments (ACP checkout live; x402 over email in early access). There is no correlation step to build and no webhook server to keep running: the reply comes back in the same call, and your code runs at the address itself.

At a glance

Beyond the address: the whole platform

Nylas hands an agent a mailbox; primitive.dev gives it a whole platform to run on:

• Hosted Functions — your JavaScript runs on every inbound email, server-side, with nothing to host or keep online.
• Programmable routing & filters — route bugs@ to a triage Function and support@ to a webhook, by rule, with sender allow/block lists.
• Primitive Memories — durable JSON state an agent and its Functions keep across turns, retries, and restarts, without bringing a database.
• Agent templates — install a ready-made agent from the template gallery (like a summarizer that replies with a summary of whatever you forward it) and run it as a hosted Function in one step.
• In-agent MCP App — an email console published as a ChatGPT app that also renders in Claude and other MCP-compatible clients, plus a public docs MCP and Node, Python, and Go SDKs.
• Payments over email — agents charge and pay each other in USDC, non-custodially, over x402 (early access), and buy usage pay-as-you-go over the Agentic Commerce Protocol.

Which to choose

Choose Nylaswhen the job is operating a human’s real Gmail or Microsoft 365 account and you want calendar and contacts in one enterprise platform — but note its per-account model ($0.20 per account each month past the accounts a plan includes) still puts a recurring line item on every agent identity. Choose primitive.dev when your agent needs its own email identity and the loop around it — a one-call conversation and code on inbound — usage-based with no per-identity fee, so the hundredth agent costs the same as the first. See the category guide or the developer resources.