primitive.dev vs. Postmark

Postmark is a transactional email service — “the email delivery service that people actually like” — built so an application can send password resets and notifications to people and trust they land.^[1] It also parses inbound mail into JSON for your webhook.^[2] It is built for humans on the receiving end — deliverability, open tracking, and message streams for a human audience. primitive.dev is built for a different actor — an autonomous agent that needs its own identity and a two-way conversation — and it owns its full mail stack end to end (inbound MX through outbound) rather than a send API bolted onto your app.

1. An agent identity, not an app sender

Postmark sends from domains your app verifies. primitive.dev issues the agent its own receivable *.primitive.email address (or a custom domain) with one call, fully managed. The agent is the mailbox — a stable identity other people and agents can write to, not just a from-address.

2. Run code at the address, not just parse to a webhook

Postmark’s inbound parses a message and POSTs JSON to your server.^[2] primitive.dev runs your hosted Function at the address on every inbound email — no server to stand up — and collapses a full round-trip into primitive chat <email> <message>, which sends and returns the threaded reply in one call.

3. Agent-native surface

primitive.dev adds a hosted MCP server with an in-agent email-console App — a published ChatGPT app that also renders in Claude and other MCP-compatible clients — durable Memories, a credential-free demo, and zero-touch agent signup — the surface an agent uses directly. Postmark’s surface is a REST API and webhooks for your backend.

At a glance

Beyond the address: the whole platform

Postmark delivers an app’s transactional mail. primitive.dev is the platform behind the agent’s address:

• 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 Postmark for the narrow job it is built for: an app pushing transactional mail to people and parsing replies to its own backend. That is rarely the job when the sender is an agent. Choose primitive.dev when an agent needs its own address, code that runs on inbound mail, and a one-call conversation. See the category guide or the developer resources.