The email API that lands for
You send it, the reply comes back, and you get back to the product. Build with your agent, or write one typed call.
Your email lands.
Build email with your agent.
Point your agent at hosted MCP, or paste the setup brief. It gets templates, contacts, and delivery as tools.
Read auth.mdAPI key
A scoped key for server-side sends, and for the agent that sends for you.
CLI login
Sign in from the terminal when you're driving setup.
Hosted MCP
Point an OAuth-capable client at mcp.samva.dev and let discovery do the rest.
Send, receive, and thread.
import { createClient } from "samva";
const samva = createClient({ apiKey: process.env.SAMVA_API_KEY });
const message = await samva.email.send({
to: "ada@example.com",
subject: "Your order shipped",
html: "<p>Order #1042 is on its way.</p>",
});Templates you can roll back.
- Versioned templates, where the version you publish is the one that sends
- Render server-side by passing a templateId and templateData
- Full version history, with one call to restore any earlier version
Built to land.
Domain authentication, suppression, and signed events come standard.
How deliverability worksDeliverability, on domains you own.
- The exact DNS records to publish, generated for your domain
- DKIM signing on your own domain, so mail goes out from your address
- Bounces and complaints suppressed for you, before they cost you reputation
Email is a conversation. Treat it like one.
Sends, replies, forwards, and bounces live on one conversation per contact, so a reply lands in your app with its whole history attached.
How receiving worksEvery email your product sends.
All of it from one send.
Password resets
OTPs and reset links that arrive before the user gives up.
Receipts
Order confirmations from a template you can roll back.
Onboarding sequences
Welcome series scheduled ahead of time, from your own domain.
Reply-driven support
Replies land back in your app, threaded to the customer.
Weekly digests
Product email in batches, with delivery you can verify.
Set it up your way.
Use the dashboard and CLI, or hand the brief to your agent.
Works with your agent.
Hosted MCP at mcp.samva.dev. Templates, contacts, and delivery as tools.
Per-email pricing on the volume you send.
Paid plans include a monthly email volume, then you pay per email beyond it. Starter is $5 for 15,000 emails, Enterprise is custom, and the free plan sends 3,000 a month. Pay in your own currency.
- 15,000 emails/month
- Templates, inbound, and webhooks
- 5 sending domains
- 50,000 emails/month
- Templates, inbound, and webhooks
- 5 team members
- 300,000 emails/month
- Templates, inbound, and webhooks
- Priority support
Still deciding?
Ask a model you trust, or a person on the team.
Is there a free tier?
Yes. The free plan sends 3,000 emails a month and needs no card. Paid plans start at $5 a month for 15,000 emails, in your own currency.
How does threading work?
Outbound sends, replies, forwards, and bounces group into one conversation per contact. Inbound email arrives parsed with the same conversation id, so replies land back in your app with context.
Do you sign webhooks?
Yes. Each delivery carries Standard Webhooks signing headers, and Samva retries failed deliveries with backoff.
Can I bring my own domain?
Yes. Add your domain, publish the DNS records Samva generates, and your mail goes out from your own address, signed with DKIM.
What about deliverability?
SPF, DKIM, and DMARC run on your own sending domains. Samva handles bounces and suppression for you, and exposes delivery telemetry so you can verify each send.
Where does Samva run?
On our global edge network, with API compute in one US region (us-east-1). Delivery runs through established email infrastructure, and GDPR consent and unsubscribe handling are built in.