# ManyLives Email Pre-Send Compliance Checker

> ManyLives Email Pre-Send Compliance Checker is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-16).

Checks an outbound email against anti-spam laws (CAN-SPAM, etc.) and validates sender domain authentication (SPF/DMARC) before sending

## Facts

- Endpoint: POST https://api.manylives.me/paid/email/presend-check?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-email-pre-send-compliance-checker-811c46b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0PiYRP8blRyRozbn_bjRy

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability manylives-email-pre-send-compliance-checker-811c46b4 -d '<json body>'
```

Example prompt: Before I send this cold outreach email, check if it's CAN-SPAM compliant — the subject is 'Quick question about your bookkeeping', the body is 'Hi Sam, we help firms cut month-end close time. Worth a chat? To stop these emails, reply STOP. Harbour Books, 12 King Street, Concord NSW 2137.', and my sending domain is example.com.

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call pre-send compliance gate for outbound emails — especially cold outreach or bulk marketing — without setting up a full email validation platform. It uniquely combines CAN-SPAM rule-checking (physical address, opt-out language, subject line) with live DNS-based sender authentication checks (SPF, DMARC) in a single call. Prefer it over generic spam checkers when legal compliance (CAN-SPAM 15 U.S.C. 7704) is the primary concern rather than deliverability scoring.

## Known failure modes

- Missing required 'body' field returns validation error
- Invalid or unresolvable sending domain may return empty authentication fields
- Domain with no SPF/DMARC records will show empty authentication values
- Ambiguous or very short email body may produce incomplete compliance checks
- Network timeout for DNS lookups on sender domain authentication

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

Returns a JSON object with a 'ready' boolean indicating if the email is safe to send, a 'checks' array listing each compliance rule with pass/fail status and a human-readable detail explaining what needs fixing, plus an 'authentication' object showing the sending domain's SPF record, DMARC record, DMARC policy, and domain name.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "examples": [
    "Hi Sam, we help firms cut month-end close time. Worth a chat? To stop these emails, reply STOP. Harbour Books, 12 King Street, Concord NSW 2137."
   ],
   "description": "email text"
  },
  "consent": {
   "type": "string",
   "description": "optional true if recipients opted in"
  },
  "markets": {
   "type": "string",
   "description": "optional, default US"
  },
  "subject": {
   "type": "string",
   "examples": [
    "Quick question about your bookkeeping"
   ],
   "description": "subject line"
  },
  "is_reply": {
   "type": "string",
   "description": "optional true if it really is a reply"
  },
  "from_domain": {
   "type": "string",
   "examples": [
    "example.com"
   ],
   "description": "optional sending domain, e.g. example.com"
  },
  "dkim_selector": {
   "type": "string",
   "description": "optional DKIM selector (s= value)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ready": false,
  "checks": [
   {
    "ok": false,
    "rule": "valid physical postal address (15 U.S.C. 7704(a)(5)(A)(iii))",
    "detail": "add the sender's current street address, a registered PO box or registered private mailbox"
   }
  ],
  "authentication": {
   "spf": "v=spf1 include:_spf.example.net ~all",
   "dmarc": "v=DMARC1; p=none",
   "domain": "example.com",
   "dmarc_policy": "none"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-email-pre-send-compliance-checker-811c46b4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)