Scoped API keys, WebSocket events, batch sending, scheduled sends, and SMTP
A big infrastructure drop: per-inbox scoped keys, a real-time WebSocket event stream, batch and scheduled sending, and an SMTP gateway for everything that speaks classic email.
Dvir Atias
Founder
Five features shipped this cycle. All of them are live for every account today.
Scoped API keys
Keys can now be restricted to specific inboxes and specific operations (read, send, manage). Give each agent its own key scoped to its own inbox and rotate keys per-agent instead of per-account. Existing full-access keys keep working unchanged.
WebSocket event stream
Webhooks are great until your agent is already a long-running process.
Connect to the event stream and receive message.received,
message.delivered, and message.bounced events over a single WebSocket -
same payloads as webhooks, no public endpoint required.
Batch sending
POST /v1/messages/batch accepts up to 1,000 messages in one request, with
per-message success and failure reported in the response. Rate limits apply
to the batch as a whole, not per message.
Scheduled sends
Pass sendAt with any ISO timestamp and the message is queued and delivered
at that time. Cancel any scheduled message before it leaves the queue with a
single DELETE.
SMTP gateway
Everything that speaks classic SMTP - legacy systems, CRMs, that one cron job from 2019 - can now send through AgenticEmail with per-inbox SMTP credentials. Messages sent over SMTP show up in the same threads, webhooks, and event stream as API sends.
As always: if something behaves unexpectedly, hello@agenticemail.dev reaches the people who built it.