mepmail.dev valid

MepMail Docs

MepMail is an open-source, Resend-compatible email platform — hosted at mepmail.dev (API: api.mepmail.dev) or self-hosted on your own AWS SES.

For agents: Open-source, Resend-compatible email platform, hosted or self-hosted on AWS SES; docs cover API, CLI, SMTP relay, MCP, integrations, billing and errors.

email platformresend compatiblesmtp relayself-hosted emailmcp email

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T14:48:45.746Z. Cached copy · Source on mepmail.dev

# MepMail Docs

> MepMail is an open-source, Resend-compatible email platform — hosted at mepmail.dev (API: api.mepmail.dev) or self-hosted on your own AWS SES.

Every page is available as raw markdown by appending `.md` to its URL.
The full documentation in one file: https://docs.mepmail.dev/llms-full.txt
The API's OpenAPI 3.1 spec (generated from code): https://docs.mepmail.dev/openapi.json
Moving an account from Resend: `npx @mepmail/cli migrate --from resend` (read-only against Resend; reference at https://docs.mepmail.dev/cli.md).
A complete agent prompt for that migration, from inventory to cutover: https://docs.mepmail.dev/prompts/migrate-from-resend.md

## Pages

- [Billing (hosted deployments)](https://docs.mepmail.dev/billing.md): How plans, Stripe Checkout, and the webhook fit together on a hosted MepMail deployment, and how to provision a Stripe account for it.
- [CLI](https://docs.mepmail.dev/cli.md): @mepmail/cli — move an email account to MepMail from your terminal: plan, apply, status, rollback.
- [Errors](https://docs.mepmail.dev/errors.md): Every error MepMail returns — names, status codes, what they mean, and what is safe to retry.
- [Introduction](https://docs.mepmail.dev/index.md): What MepMail is and how the pieces fit together.
- [Integrations](https://docs.mepmail.dev/integrations.md): n8n, Slack, Discord, Telegram, MCP, the SMTP relay and the API — how MepMail fits the tools you already run.
- [Mailboxes for people and agents](https://docs.mepmail.dev/mailboxes.md): Separate a personal or agent mailbox from application and campaign sending.
- [MCP server](https://docs.mepmail.dev/mcp.md): Connect AI agents to MepMail through the Model Context Protocol.
- [Migrate from Resend](https://docs.mepmail.dev/migrate-from-resend.md): One command moves your Resend account; two environment lines move your code, for the sending flows that follow the Resend API format.
- [npm packages](https://docs.mepmail.dev/packages.md): The packages MepMail publishes on npm — @mepmail/mcp, @mepmail/cli and the n8n node — what each one does and how to install it.
- [Quickstart](https://docs.mepmail.dev/quickstart.md): Get MepMail running and send your first email in a few minutes.
- [Rate limits](https://docs.mepmail.dev/rate-limits.md): The request, creation and sending limits a MepMail deployment enforces — and how to work within them.
- [Recipes](https://docs.mepmail.dev/recipes.md): Four end-to-end integrations — a support agent with human approval, triage without send, one agent over several mailboxes, and SaaS notifications — with the right credential, events, errors and diagnosis for each.
- [SDKs](https://docs.mepmail.dev/sdks.md): Use the official Resend SDKs against your MepMail instance — there is no client of ours to install.
- [Self-hosting](https://docs.mepmail.dev/self-hosting.md): Deploy MepMail on your own infrastructure with Docker Compose and your own AWS SES account.
- [API reference](https://docs.mepmail.dev/api-reference.md):
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=mepmail.dev · GET /v1/domain/mepmail.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for mepmail.dev:
1. POST https://agentwebmap.com/v1/sites/mepmail.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://mepmail.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/mepmail.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mepmail.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.