What shipped in Rasket, dated: new API surface, dashboard sections, SDK releases and deliverability tooling, phrased for the people who use it.
Mail you receive is now a conversation rather than a list of messages. Pick a mailbox, read a thread of what came in and what you sent back, and reply from the dashboard — the reply goes out on the same send path as everything else, so it appears in the log with its own delivery events. Unread counts sit on the rail.
Broadcasts and automations move onto a separate allowance with seven contact tiers, so the size of your audience decides what marketing costs and your transactional volume does not. The tier you hold is named on the billing page, and buying one says what it costs before you buy it.
Send an email with tags and they come back on the email object, filter the Emails list and the API, and travel on every webhook event for that message. A tag a provider would refuse is refused on the way in, with a message that says which one.
The metrics behind the dashboard charts and the metrics endpoint are recomputed every minute instead of every fifteen. A send you make now shows up while you are still looking at the screen.
If your domain is on Cloudflare, connect the account once and the DKIM, SPF, DMARC and return-path records for a new sending domain are created for you. It is an authorisation rather than a pasted token, and you can withdraw it from Cloudflare at any time.
The Python client joins the Node one, both generated from the same OpenAPI document. Every documentation page now has a Markdown twin at the same URL — add .md, or ask for it with an Accept header — and /llms.txt indexes the lot, so an assistant reading the docs does not have to parse a web page to do it.
Point an assistant at the MCP endpoint and it can set an account up and send for you: 74 tools across seven toolsets, scoped by the credential it connects with, with a setup recipe it can follow. No key ever has to appear in a prompt.
Three arrivals in one week. Automations run per contact on your product's own events, with waits, branches and a run log. Inbound mail is delivered to your endpoint as a signed webhook with headers, bodies and attachments. And an OAuth server lets another application act on a team's behalf with scopes the team granted.
Sign up, verify a domain and send your first email in minutes.