Wave 6: scheduling, dedicated IPs, and 9 SDKs

This wave is about reach and reliability: getting messages out at the right time, from the right place, in whatever language your agent is written in. Here's what shipped — and what's on the way.

Scheduled sends

Agents don't just react — they plan. You can now schedule a send for a future time instead of firing it immediately. Pass a scheduledAt timestamp and Dairo queues the message and delivers it when the time arrives, with the same delivery events you get from an immediate send.

TypeScript
await dairo.messages.send({
  from: inbox.address,
  to: "[email protected]",
  subject: "Your weekly summary",
  text: "Here's what happened this week…",
  scheduledAt: "2026-06-16T08:00:00Z", // delivered Monday morning
});

It's built on a dispatcher-and-queue design rather than a per-message timer, so a digest going out to ten recipients and one going out to ten million behave the same way and stay on time.

Nine SDKs, one API

Agents are polyglot, so Dairo is too. The full official SDK lineup is now live across nine languages:

• Python and TypeScript — the most common agent stacks, first-class.
• Go, Ruby, PHP, and Java — for backend services that send on an agent's behalf.
• .NET, Elixir, and Rust — covering the rest of where real systems are built.

Every SDK wraps the same REST API, so capabilities never drift between languages. Alongside them, the Dairo CLI is great for scripts, CI, and quick checks, and the native MCP server exposes inboxes, sends, messages, and events as tools your agent can call directly.

Dedicated IPs for high-volume senders

Sender reputation is everything for deliverability. For teams sending at high volume, dedicated IP pools (managed via SES) are planned — giving you an isolated reputation that isn't affected by other senders on the shared pool.

Until those dedicated pools ship, the shared sending infrastructure is actively warmed and monitored, with bounce and complaint events surfaced so you can keep your lists clean and your reputation healthy from day one.

The rest

• Outbound events — accepted, delivered, bounced, and complained — are available on every send so agents can act on real delivery outcomes.
• Custom domains — verify your own domain and send from an address your users recognize.
• Audiences — manage recipient lists and send to all of them with messages:read / messages:send scopes.

Grab the SDK for your language and try the new scheduled sends today. The docs have the full reference, and the launch post covers the bigger picture of why we're building email infrastructure for agents.