Install samva. Send in one call.
Install samva, pass your key, and call email.send. Then get back to the product. Or copy the setup brief and let your agent write the integration.
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>",
});See a reply land in the same thread.
Get a demo address and email it from your own account. Samva receives it as a signed webhook and replies in the same thread through the send API, the same calls your app makes.
Email Samva, get a reply
Get a demo address, email it, and watch Samva reply in the same thread.
- Your email arrivesWe reply to mail that passes DMARC.
- We reply in the same threadOne call to the send API.
- We confirm deliveryAccepted by your mail server.
- Your reply comes backHit reply and say anything.
Preparing security verification.
Send, verify, generate from one contract.
POST /v1/messages
X-API-Key: samva_sk_live_...
{ "channel": "email",
"to": [{ "email": "ada@example.com" }],
"email": { "subject": "Your order shipped" } }
201 { "id": "msg_7q2xk9mvt4znw8rh", "status": "pending" }One typed call. The compiler catches a bad payload before it ships.
SENDING AN EMAILPOST /webhooks/samva
webhook-id: whevt_7q2xk9mvt4znw8rh
webhook-timestamp: 1783503734
webhook-signature: v1,SGVsbG8...
{ "type": "message.delivered", "timestamp": "2026-07-08T09:42:14Z",
"data": { "messageId": "msg_7q2xk9mvt4znw8rh" } }
verify({ body, id, timestamp, signature, secret })Delivery, bounce, and inbound events, signed. Retries with backoff.
WEBHOOK REFERENCE# the typed TypeScript SDK
npm install samva
# the whole API, as one spec
GET https://api.samva.dev/v1/openapi.json
200 · openapi 3.1 · every endpoint, typedInstall the TypeScript SDK, or generate a client from OpenAPI 3.1.
OPENAPI SPEC{
"mcpServers": {
"samva": {
"url": "https://mcp.samva.dev",
"headers": { "X-API-Key": "samva_sk_live_..." }
}
}
}Point your agent at mcp.samva.dev. Your agent gets sending, replies, domains, templates, campaigns, and webhooks as tools. API key or OAuth.
HOSTED MCP- SAMVA APIemail.send() · POST /v1/messages
- YOUR CUSTOMERreceives it, replies
- INBOUNDreply threaded into conv_5nz8qd3hv6r0wxkt
- SIGNED WEBHOOKmessage.received to your app
- DELIVERYmessage.delivered or message.bounced
sent 18 · delivered 18 · replies threaded 3
Replies come back to your app.
Turn on receiving for your domain. A reply to an email you sent arrives at your webhook as message.received, with the conversationId of the email it answers. Answer in the same thread by passing that id.
POST /webhooks/samva
{ "type": "message.received",
"data": {
"from": "ada@example.com",
"subject": "Re: Your order shipped",
"conversationId": "conv_01j8k5p7q9r2s4t6v8wx" } }import { createClient } from "samva";
const samva = createClient({ apiKey: process.env.SAMVA_API_KEY! });
await samva.email.send({
to: "ada@example.com",
conversationId: "conv_01j8k5p7q9r2s4t6v8wx",
subject: "Re: Your order shipped",
html: "<p>It arrives Thursday.</p>",
});- SIGNEDwebhook-signature: v1 on every request
- RETRIESup to 8 attempts, with backoff
- YOUR ENDPOINTanswers 200, the event is done
webhook-signature header and retried with backoff until your endpoint returns a successful 2xx response, up to 8 automatic attempts.Everything the one-way pipe leaves out.
Send in one typed call
One call returns a message id, and the email's status follows it from queued to sent to delivered.
Replies come back to your app
Inbound email on your domain is parsed, threaded to the email it answers, and posted to your webhook. Answer in the same thread.
Know what happened to every email
Sent, delivered, bounced, complained, received: signed webhook events, retried with backoff. Opens, clicks, and a timeline per send in the dashboard.
Change the email without a deploy
Versioned templates in a Git-backed project. Publish, roll back, or edit in the AI email editor.
Send from your own domain
Samva generates the DKIM and SPF records and checks your DMARC policy. On Cloudflare or Vercel, it adds them for you.
Announcements from the same API
Campaigns send one email to a list of contacts, now or on a schedule, using the same templates, domain and events as your transactional mail.
Your agent can run it
Hosted MCP and the CLI. Your agent edits a template, you review the diff, and you publish that exact version.
Your own sending reputation
Each account sends with its own reputation. Bounces and complaints are suppressed per account, and you can see and lift a suppression.
A bill with a ceiling
Extra emails cost exactly $0.50 per 1,000, under a spend limit you set.
An inbox for your agent
Give your app or your agent its own inbox on samva.email or your domain, like support@ or agent@. It reads, searches, and replies through the API, CLI, or MCP with a key that reaches only that mailbox.
The SDK ships an Effect-native client too.
Import Pascal-cased modules from samva/effect/* and call operations directly. Each operation composes into your Effect v4 program.
import { Effect } from "effect";
import * as Client from "samva/effect/client";
import * as Email from "samva/effect/email";
const program = Email.send({
to: "ada@example.com",
subject: "Your order shipped",
html: "<p>It arrives Thursday.</p>",
}).pipe(
Effect.catchTags({
RateLimitedError: (e) => Effect.sleep(e.retryAfterSeconds * 1_000),
ValidationError: (e) => Effect.log(e.fields),
}),
Effect.provide(Client.layerFetch({ apiKey: process.env.SAMVA_API_KEY! })),
);
const message = await Effect.runPromise(program);- Typed errors
- Failures arrive as tagged errors you narrow with catchTags. RateLimitedError carries retryAfterSeconds, ValidationError carries the offending fields.
- Layer-based services
- Domain operations require Client.Service. Build Client.layerFetch once and provide it around the part of your program that calls Samva.
- Schema-driven
- Requests and responses are decoded through Schema, so a malformed payload fails at the boundary, not three calls later.
Build it with your agent.
Samva publishes setup at /auth.md, so your agent picks the credential and writes the integration. Point it at hosted MCP, or paste the brief below.
Samva for ChatGPT, Claude, Cursor, and Grok
Open the Samva plugin in ChatGPT, connect one organization, and start with a read-only readiness check.
ClaudeComing soon
ChatGPT
CursorComing soon
GrokComing soon
ChatGPT
Cursor
GrokNumbers we publish, and the code that enforces them.
Free tier
Every month, no card
Past your allowance
Any paid plan, one rate
Webhook delivery
Automatic attempts, then the log
Signed events
What reaches your endpoint for one email
- 09:41:02message.sentmsg_8f2c1qd3hv6r0wxk
- 09:41:04message.deliveredmsg_8f2c1qd3hv6r0wxk
- 10:17:55message.receivedconv_5nz8qd3hv6r0wxkt
Send latency
p50, production, API to accepted
Prices, limits, and retries are read from the code that enforces them.
Read the docs, then send.
API key to first send in one call.
REFERENCEAPI referenceEvery resource, verb, and payload.
EVENTSWebhooksRegister endpoints and verify signatures.
SDKTypeScript SDKPromise and Effect entrypoints, typed end to end.
HTTPREST APIAuth, pagination, and errors over raw HTTP.
AGENTSHosted MCPBuild with your agent over hosted MCP.
Your customers' business email runs on it too.
Small businesses use the same platform in Samva Mail: business email on their own domain, shared inboxes, and an AI assistant that answers the routine customer email. The conversations your API writes are the ones their team answers.
Samva for small businessesQuestions from developers.
Which languages can I use?
TypeScript has a typed SDK (npm install samva). Anything else calls REST, and the OpenAPI 3.1 spec generates a client in your language.
How do I verify a webhook?
Every event is signed and follows the Standard Webhooks spec. @samva/webhooks checks the signature for you in TypeScript. In other languages, verify with any Standard Webhooks library and your signing secret.
Can my coding agent set it up?
Yes. Point any MCP client that supports OAuth at mcp.samva.dev, or run samva login. A person approves the first credential.
What does it cost?
500 emails a month free, no card. Paid plans start at $5 for 15,000.
Send the first email from your editor.
Install samva, pass your key, and call email.send. The response carries the message id you track from there.