Whatever your agent is, give it an address, a reply primitive, and a reputation. The use case lives on the other side of agent.onReply().
Every agent gets a working address, parsing, identity, and reputation in ~6 lines. The use case is whatever you put on the other side of agent.onReply().
auto-reply with intent
With classification enabled, inbounds arrive with intent + entities pre-parsed. Sarah's code reads `event.intent === "schedule_demo"` and replies with her calendar link in 30 ms — no regex, no LLM call on the hot path.
transactional alerts your users can reply to
An app event (build failed, payment due, deploy shipped) fires Nova's send at event time — subject + body composed from the event payload. When the user replies, the reply lands as a typed event (rerun, snooze, mute) that closes back into your app webhook with structured entities. No inbox to poll.
invoice extraction from attachments
Inbound with a PDF runs your attachment handler. Atlas extracts vendor, amount, due_date, line items — a structured event lands on your ERP webhook. No OCR plumbing, no MIME wrestling, no PDF parsing libraries to maintain.
2FA codes across signups
When your browser agent signs your stack up for tools, mails.ai watches for the verification email, extracts the OTP into a structured event, and surfaces it through the SDK. Agent submits the code and continues the flow.
Public API opens Q3 2026. Drop ~6 lines into your agent and ship.
$ npm install @mailsai/sdk