Close the loop
Send a clear summary when an agent finishes a research, support, or analysis task.
result → recipientApimend Mail gives AI-native apps a reliable way to send transactional email. Your application—or an agent acting through it—calls one API, with idempotent retries, sending limits, and signed events.
agent.tsimport { ApimendMail } from "apimend-mail"; const mail = new ApimendMail({ apiKey: process.env.APIMEND_KEY }); // call this from your agent loop await mail.send({ from: "agent@you.com", to: "user@example.com", subject: "Your weekly report", html, idempotencyKey: run.id, // deduplicate repeated requests });
{
"name": "send_email",
"description": "Send an email to a user",
"parameters": {
"type": "object",
"properties": {
"to": { "type": "string" },
"subject": { "type": "string" },
"html": { "type": "string" }
},
"required": ["to", "subject", "html"]
}
}
curl https://app.apimend.com/v1/send \ -H "Authorization: Bearer $APIMEND_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $RUN_ID" \ -d '{ "from": "agent@you.com", "to": "user@example.com", "subject": "Your weekly report", "html": "<h1>Report ready</h1>" }'
Let your agent do the work. Keep delivery policy, credentials, and guardrails in your application—not in the model prompt.
Send a clear summary when an agent finishes a research, support, or analysis task.
result → recipientSend an approval request with the context a person needs before your workflow continues.
action → approvalNotify the right person when an agent finds an exception, deadline, or change worth acting on.
signal → actionAn agent that retries a failed call should not send the same email twice. An agent that loops should not spam your users. Most email APIs were not built for this.
Agents retry on timeouts. Without idempotency, your user gets the same email five times.
A buggy loop, a bad prompt, or a stuck job can email your whole list before you notice.
When an agent acts, you need to know what it sent, to whom, and what happened next.
A scoped key, a verified domain, and one tool call from your agent workflow.
Sign up and get a scoped API key for each agent. The free tier works immediately.
am_live_ 8f3c0d...Prove ownership, add the SES identity and DKIM records, then check verification status.
_apimend-verification TXTDrop in the JSON schema or call the SDK. Pass a run id as the idempotency key.
POST /v1/sendSend transactional email with one JSON request. The API queues your message and returns an ID you can use to check its status.
Explore the send API →Pass a stable key to deduplicate repeated requests. Uncertain provider outcomes are not automatically resent.
Suppressions, plan caps, a daily send cap, and per-key rate limits keep a runaway loop in check.
A searchable log of every send with status, provider, and error. Know what your agent did.
Signed send, failure, open, and click events. SES delivery receipts are available in email details.
Build reusable transactional emails in the visual editor or HTML, preview variables, and restore earlier revisions.
Explore templates →Prove ownership and follow guided SES identity and DKIM setup before sending from your domain.
Explore domain setup →Keep bounced, complained, and unsubscribed addresses out of future sends.
Explore suppressions →One key per agent. Revoke and rotate without touching the rest of your stack.
Boring infrastructure, done well, so the agent never has to care.
Requests are queued for a worker. Repeated requests with the same idempotency key return the original result; uncertain provider outcomes require review.
Set a daily cap and per-key rate limits. Suppressed addresses are blocked before a job is even queued, so a loop cannot reach people who opted out.
Every outgoing webhook is signed with t=<unix>,v1=<hmac>. The SDK provides a verifier; your application must verify the signature and timestamp before acting.
import { verifyWebhook } from "apimend-mail"; const ok = verifyWebhook({ secret: process.env.WH_SECRET, payload: rawBody, signature: req.headers["x-apimend-signature"], }); // reject if false
A modern email API built for automation, not 2012.
| DIY SMTP | Legacy ESP | Apimend | |
|---|---|---|---|
| Tool-ready call | build it | partial | yes |
| Idempotent retries | build it | no | built in |
| Guardrails and caps | build it | partial | yes |
| Signed webhook events | build it | partial | yes |
| Audit log of sends | logs | yes | searchable |
| Guided domain setup | manual | yes | guided |
Straightforward plans based on transactional email volume. Account creation is not open yet.
Apimend Mail is an email API for AI-native apps. Your product calls one endpoint to send receipts, alerts, and digests, and we handle queueing, retries, domain verification, and delivery events.
Yes. It is built for app-triggered email like password resets, receipts, notifications, and digests. You send through an HTTP API or the TypeScript SDK.
Those are established email providers. Apimend focuses on a small, modern API for AI-first teams, with idempotent retries, guardrails, and signed webhooks in one place. Under the hood we send through Amazon SES, so you get reliable delivery without managing it.
Both are developer-focused email APIs. Apimend is built around agent workloads: idempotency for retries, daily caps and rate limits, and a tool schema for function calling. If you want marketing email or a large template editor, Resend is a better fit today.
Yes. The API is one JSON call, and the tool schema works with any function-calling framework. Your agent calls send_email and the worker handles delivery.
Pass an idempotency key, like your run id. A repeated request with the same key returns the original email instead of sending again.
Suppressions are checked before a job is queued, per-key rate limits apply, and you can set a daily send cap and a monthly plan limit. A loop hits a wall instead of your users.
Yes. A JSON schema for a send_email tool is on this page and in the SDK. It works with OpenAI, Anthropic, and other frameworks.
Apimend Mail includes a local MCP server with tools to queue an email and check its status. LangChain and other agents can call the API using their standard tool or HTTP integrations. Your application remains responsible for recipient permissions and approval policy.
Add your domain, publish the ownership TXT record, then add the SES identity and DKIM records shown in the console. Apimend checks ownership and reports SES verification status.
They are email authentication records. DKIM signs your mail, SPF lists the servers allowed to send for your domain, and DMARC tells receivers what to do when authentication fails. Together they keep your email out of spam.
There is an official TypeScript SDK for Node. Any language that can make an HTTP request can use the API, including Python, Go, Ruby, and PHP.
Yes. Install the SDK, add your API key, and call mail.send() from a server action or route handler. Keep the key on the server, never in the browser.
Yes. Subscribe to email.sent and email.failed or all events. Every outgoing webhook is signed with HMAC-SHA256 and retried with backoff.
Use the verifyWebhook() helper in the SDK. It checks the HMAC and the timestamp, so you can reject forged or replayed events.
Yes. Create templates with {{tokens}}, keep the structure under your control, and let your app or agent fill the data.
A small pixel records opens, and rewritten links record clicks. Counts show per email. You can disable tracking per send with track: false.
Bounced, complained, and unsubscribed addresses are added to suppressions automatically and are blocked before a send. That protects your sending reputation.
Yes. Set scheduledAt to delay a send, and use the batch endpoint to send up to 100 emails in one request.
Point your sending code at the Apimend API, add your domain, and run a test send. The SDK is small, so migration is usually a few lines.
Yes. The free plan includes 4,000 emails per month, one domain, the API and SDK, and signed webhooks. No card required.
Each recipient counts as one email toward your monthly allowance. Accepted sends count toward usage even if delivery later fails. Requests that exceed your remaining allowance are rejected; there are no automatic overage charges.
Not yet. Apimend is an HTTP API with an official TypeScript SDK. SMTP is on the roadmap.
API keys are hashed, webhook secrets are encrypted at rest, and webhook URLs are checked to block private addresses. You can export or delete your workspace data at any time.
Connect a tool-calling agent to transactional email with the guardrails your app needs.
Request early access