m_maildignity.Sign in
DOCUMENTATION / V1.0 CONTRACT[ API PREVIEW ]

Human standards.
Machine-readable.

One email in. One structured verdict out.
Built to fit the workflow you already use.

→ Create an API key in your dashboard. Keys start with md_live_. Each call uses one check from your monthly quota; when it runs out the API returns 402. Remaining checks come back in the X-Checks-Remaining header.

POST /api/public/v1/check

Send email text. Optionally include the prospect’s name, company and role.

curl -X POST "$MAILDIGNITY_BASE_URL/api/public/v1/check" \
  -H "Authorization: Bearer $MAILDIGNITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email_text": "Hi Stefan, would a short overview be useful?",
    "prospect": {
      "name": "Stefan",
      "company": "Growth Agency",
      "role": "SEO Lead"
    },
    "mode": "full"
  }'
email_textrequiredThe outbound email to evaluate.
prospectoptionalRecipient name, company and role.
modeoptional"full" (default): verdict, verbatim snippets and rewrites. "fast": instant traffic light only, for high-volume batches.

A verdict with receipts.

Issues include an exact snippet, severity and a reason. Each issue carries a short suggested rewrite. On REVIEW, repaired_body returns the full email with those rewrites applied, ready to send; it is null on PASS and FAIL. In fast mode you get only the verdict and flagged rules.

{
  "verdict": "PASS",
  "summary": "Respectful, low-friction outreach.",
  "issues": [],
  "repaired_body": null,
  "context_check": {
    "status": "not_checked",
    "note": "Context evaluation is optional."
  }
}

Three verdicts. No drama.

[PASS] Respectful, focused and low-friction.

[REVIEW] A tone or assumption worth a second look. Not an automatic block.

[FAIL] Explicit rigid asks, clear problem/offer disconnects, or blatant generic clichés.

Ten boundaries are checked: asymmetric asks, guilt-trip follow-ups, fake familiarity (including fake “Re:” / “Fwd:”), unsolicited diagnosis, homework, generic flattery, bait and switch, cognitive overload, hostility and privacy intrusion (private-life facts like health, pregnancy or bereavement; public professional news is fine).

The same engine powers the playground and the API. No global fact-checking is promised.

Your tools. Better guardrails.

The planned HTTP contract can be used in Make, Clay, n8n and Zapier. Route PASS to the next step, REVIEW to the repaired email (repaired_body), and FAIL to a hold queue.

Try a demo audit