Humanizer

The humanizer rewrites outgoing emails using an LLM to make them sound more natural. Instead of sending template output verbatim, the humanizer adjusts phrasing, tone, and structure while preserving your message's content and intent.

How it works

1. You send an email through the normal send endpoint with humanization enabled.
2. The humanizer rewrites the email body in your chosen style.
3. The rewritten version is sent to the recipient.

If rewriting fails for any reason, the original email is sent unchanged — your delivery is never blocked by the humanizer.

Styles

Enabling per send

Add the humanize and humanizeStyle fields to your send request:

curl -X POST https://api.molted.email/v1/send/request \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "tenant_abc123",
    "recipientEmail": "user@example.com",
    "templateId": "follow-up",
    "dedupeKey": "followup-user@example.com",
    "payload": {
      "subject": "Following up",
      "html": "<p>Just checking in on our conversation last week.</p>",
      "text": "Just checking in on our conversation last week."
    },
    "humanize": true,
    "humanizeStyle": "friendly"
  }'

Tenant-level configuration

You can enable the humanizer at the tenant level so all sends are rewritten by default. Configure this through the portal settings or the self-service API:

curl -X PUT https://api.molted.email/v1/me/humanizer \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true,
    "style": "professional"
  }'

Per-send settings override tenant defaults. If the humanizer is enabled at the tenant level but a specific send sets humanize: false, that send will not be rewritten.

Checking your configuration

curl https://api.molted.email/v1/me/humanizer \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "enabled": true,
  "style": "professional"
}