primitive.dev vs. Resend

Resend is “the email API for developers” — send transactional and marketing email at scale, and it also receives: Resend parses inbound mail and POSTs it to a webhook endpoint you host.^[1][2] It is aimed at a developer wiring email into an app whose recipients are people. That is a different job from the one primitive.dev does: give an autonomous agentits own identity and a conversation. Resend’s agent tooling (an MCP, skills) helps a developer send and receive throughResend from their app.

1. The agent is the mailbox, not your app

On Resend your app owns the sending domain and the receiving endpoint; the agent is a caller. primitive.dev issues the agent its own receivable *.primitive.email address (or a custom domain) in one call — a stable identity people and other agents write to.

2. Code at the address and a one-call reply, not a webhook to babysit

Resend’s inbound delivers a webhook to a server you host, or a receiving API you poll.^[2] primitive.dev runs your Function at the address — no endpoint to operate — and collapses a full round-trip into one verb: primitive chat <email> <message> sends and returns the threaded reply in a single call. On Resend you assemble send, webhook, thread correlation, and waiting yourself.

The address is the front door to a runtime: programmable routing and filters decide what reaches your agent, Functions run your code on arrival, Memories persist state across turns, and agent templates package whole behaviors — plus in-agent payments (ACP checkout live; x402 over email in early access).

3. Built and priced for the agent surface

primitive.dev is agent-native end to end: 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 a zero-touch signup that hands an agent an inbox from a single unauthenticated call. Resend is priced and shaped around your app’s send volume,^[3]not an agent’s identity.

At a glance

Beyond the address: the whole platform

Resend is a pipe for an app’s mail. primitive.dev is the runtime an agent lives in:

• 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

Reach for Resend if you are a developer adding email to an app whose users are people. Reach for primitive.dev when the sender and receiver is an agent that needs its own identity, code on inbound, and a conversation in one call. See the category guide or the developer resources.