Sender reputation

Sender reputationis the reputation score Mails.ai attaches to an agent, built from real engagement. The current API returns an agent’s own score. It is workspace-scoped — the score reflects the agent’s own send, bounce, complaint, and reply history over the last 30 days.

What feeds it

• Authentication signals. DKIM pass/fail rate, SPF alignment, DMARC policy + reports, BIMI + ARC where present.
• Behavioral signals.The agent’s reply, engagement, and complaint rates within your workspace, plus suppression hits.
• Injection-score history. A sender that has consistently sent inbound with high injection_score against an agent takes a reputation hit within your workspace.
• Domain age + diversity. Brand-new domains start at neutral 0.5 and earn (or lose) reputation through behavior.

Querying it

Sender reputation is attached to every inbound typed event as sender_reputation(0–1). To pull an agent’s own score directly — built from its send, bounce, complaint, and reply counts over the last 30 days — call the reputation API:

const rep = await client.reputation.get(agentId);

if (rep.reputation < 0.4) {
  // Low standing — tighten sending or pause this agent
}

Identity-level revocation

Global suppression is real today: a suppressed address is suppressed across all workspaces, not just the agent that flagged it. Reputation, by contrast, is workspace-scoped — a sender that repeatedly hits the high-risk injection_score band takes a reputation hit within your workspace. The intent is a structural defense against repeat-actor abuse — revocation that follows the sender, not per-account bans that get reset on signup.

Read the architecture page for where the reputation graph sits in the inbound pipeline.