Public REST API and hosted MCP server: one key per workspace, with the permissions you tick.

Mailcheer in your application

Your product will write its own email.

Your product writes to your users — invoice, alert, password reset. The Mailcheer API replaces your sending service, with the same fields as the one you are leaving.

Paste this into your project's agent
Read mailcheer.com/app/install and connect Mailcheer for me.

What the agent can do

  • Send your transactional email: welcome, confirmation, invoice, alert.
  • Then know whether it was delivered, bounced, or reported as spam.
  • Add and unsubscribe contacts from your code, double opt-in included.
  • Create a campaign and send it, if the key carries that right.
  • Never send twice, thanks to the idempotency header.

What it cannot do

  • Send anything with a key you did not grant sending rights to.
  • Send from an address whose domain is not verified in your workspace.
  • Write to someone who unsubscribed, or whose address hard-bounced.
  • Remove an address from the suppression list — no tool allows it.
  • See any workspace other than the one its key belongs to.

Connection details

SurfaceREST API, called from your code — no library to install
ConnectionAPI key in a Bearer header, one per calling service
ScopeOne Mailcheer workspace per key, with the rights you tick
RevocationOne click under Settings → API, effective on the next call

Three things to know before you connect your code: you verify the sender's domain in your Mailcheer workspace, the suppression list protects single sends too, and those sends count against your plan's monthly quota.

POST mailcheer.com/api/v1/emails — from, to, subject, html — the same fields as before — 202 Accepted · id cmu651xf20002… — GET mailcheer.com/api/v1/emails/cmu651xf20002… — delivered

Connected in 3 steps

  1. Create a key in your Mailcheer workspace: Settings → API → New key, with “emails:send”.

  2. Put it in your service's environment variables, like any other secret.

  3. Change the base URL of your sending calls. The fields and the response do not move.

What you can ask

Six examples to copy, from the first draft to domain health.

Campaigns

Send the welcome email on every confirmed sign-up.
Trigger the announcement campaign when I publish a new release.

Subscribers

Subscribe new customers to the Product list, with double opt-in.
Cleanly unsubscribe deleted accounts, everywhere.

Domain & deliverability

Use my dedicated sending subdomain for transactional email.
Surface bounces in my monitoring tool.

Useful access, clear limits

One key, one workspace

Every key belongs to a single Mailcheer workspace. Your other brands or clients stay invisible to the agent, with nothing to configure.

You tick what the key may do

Seven rights, chosen at creation: send emails, read subscribers, change them, read campaigns, send them, read webhooks, manage them. A key without sending rights can never send, whatever the agent is told.

Revoke in one click

One click under Settings → API cuts the key. The next call is refused, and your other keys keep working.

Frequently asked questions

Your product already knows how to write. Give it a sending address.

And to connect, one line is enough:
Read mailcheer.com/app/install and connect Mailcheer for me.