---
title: Spam, malware, and abuse
description: How Agentry approaches abuse prevention, deliverability, and what we expect from you.
surface: shared
---

Agentry does not expose a separate spam labelling API (for example, an “include spam” flag on every list endpoint). Instead, **protection is layered**: we enforce acceptable use in our [Terms of Service](/terms), and **mail to and from the Service travels over industry-standard email infrastructure** that applies its own rate limits, reputation checks, and abuse controls. Many email platforms describe similar behavior because a large share of filtering happens in the **networks that actually move mail**, not only in the product you call over HTTP.

## Outbound mail

We may throttle or pause sending when we detect unusual volume, abuse patterns, or risk to other customers. **Carriers and delivery networks** may also reject, delay, or rate-limit messages—especially when list hygiene is poor (high bounces or complaints) or when content triggers automated safeguards. Those actions can occur even when your request to us succeeded technically.

## Inbound mail

By the time a message appears in your inbox through the Service, it has already passed through the same kind of **carrier-side checks** that protect most internet email. We do not promise a dedicated in-product malware scanner on every message path; **obvious abuse and dangerous payloads are often mitigated before or during delivery**. Regardless, we may still suspend or terminate accounts that send spam, phishing, or malware, as set out in the Terms.

## Your responsibilities

- Comply with applicable anti-spam law and our Terms.
- Keep bounce and complaint rates low so the Service stays healthy for everyone.
- Treat deliverability and abuse signals seriously; repeated problems may lead to **account suspension or termination** (see Terms).

For how we enforce this in contract, see the **Anti-Spam Policy** and **Delivery networks** sections in the [Terms of Service](/terms).