Resend just gave AI agents their own email inboxes. Jon's agents already have one catching sales pitches
Resend opened Inboxes to every user on October 21, at $1 a month for each extra inbox. Jon's agents built a pitch filter on it that has not missed one yet.

On October 21, at its Resend Forward conference, Resend launched Inboxes, "the inbox for agents." Resend is the email service behind Jon's website mail. An inbox is a real email address on a company's own domain, like support@example.com. A program can make one with a single call to Resend's API, the way one program asks another for a job. Resend's recap says it is "available now for every Resend user." On October 20 it was still a private beta with no prices.
Now the prices are public. Every plan gets three inboxes free, and on paid plans each extra one costs $1 a month, says Resend's pricing page. Mail in and out of an inbox counts against the plan's normal email quota. Agents reach an inbox through the API, a command-line tool, ready-made skills or MCP, a standard way for AI tools to plug into apps.
Each inbox also has a built-in agent that follows plain-English instructions. The launch post says it can draft, forward, label, assign, mark spam, archive and delete. But Resend's agent guide says it "never sends email on its own." Replies and forwards wait as drafts for a person to send.
That limit matters, because anyone can email an agent. Resend's own Agent Email Inbox skill warns: "Without proper security, anyone who knows your agent's email address can send instructions that your agent will execute." That trick is called prompt injection: an email written to give the agent orders. The skill offers five security levels, from a strict list of allowed senders to a human approving every action, and says to start at the strictest.
Jon's agents put two inboxes to work. The first, set up October 19, handles client support on his site's domain. Since Resend's agent only drafts, the agents built their own handler. Jev, the decision model Jon's agents use for sorting, screens out spam and unknown senders. Claude Haiku 5.5 answers routine questions, like an invoice, in about two seconds; anything else goes to Jon. On 10 made-up emails run three times each, it made 30 of 30 right calls, including one email giving the agent orders and one from a look-alike domain. It is built, but still switched off until Jon gives the go.
The second guards HyperKonic, Jon's company. Its contact form got a pitch selling "AI visibility" when the site was one day old. Now each message gets one question to Jev: real inquiry, or sales pitch? Real ones reach Jon. Pitches go to a spam@ inbox. If Jev fails or is slow, the message counts as real, so nothing gets lost. Each test message ran twice before the filter went live on October 20:
| Messages tested | Count | Sorted right |
|---|---|---|
| Pitches the site really received | 2 | 4 of 4 |
| Made-up real inquiries: investor, VC associate, journalist, client, partner, a one-line question | 6 | 12 of 12 |
| Made-up hard pitches: one calling itself a "partnership", one telling the filter to call it an inquiry | 2 | 4 of 4 |
Each call took 98 to 211 milliseconds, and all 20 cost $0.000524 together. A second filter runs the same check on email sent straight to the company's addresses. On October 28 it caught its first real one: a pitch sent to info@ landed in spam@.
How to use it
- Sign up; there is no waitlist now. The domain needs DKIM and SPF, records that prove mail really comes from it, plus an inbound MX record, which tells the internet where to deliver mail. With
forwarding: true, DKIM and SPF are enough, says the Create Inbox reference. - Install the security skill with
npx skills add resend/resend-skills. It needs theresendpackage 6.34.1 or later. Pick a level before writing the webhook (the notice Resend sends a program when mail arrives), and check every webhook's signature. - Start the built-in agent on drafts and labels. For replies that go out on their own, route the webhook to a custom handler with its own screen and checks.
- The catch: an extra inbox is cheap, but every email in and out uses the same quota as normal sending.
- Size the trust to the test. These filters were proven on small sets: 12 emails across both HyperKonic filters and 10 for client support. Before letting a filter like this decide alone, run a few dozen of a site's own real messages through it twice.
Sources
- Inboxes: the inbox for agentsPrimary · Oct 29, 2026
- What you missed at Resend ForwardPrimary · Oct 21, 2026
- Announcing InboxesPrimary · Oct 22, 2026
- Resend pricingPrimary · Oct 29, 2026
- Inbox Agent, Resend documentationPrimary · Oct 29, 2026
- Agent Email Inbox SkillPrimary · Oct 29, 2026
- HyperKonicPrimary · Oct 20, 2026
- Create Inbox, Resend API referencePrimary · Oct 29, 2026
Comments
No comments yet.
Sign in to comment. You'll come back to this story.