Questions · Updated 2026-09-27

How do I check my sending reputation?

Check your sending reputation with GET /trust/standing, which returns the account's state and the bounce or complaint reading behind it, GET /deliverability/domains, which lists every sending domain worst first, and GET /trust/thresholds, which publishes the lines those readings are judged against. This is the account's standing here, measured from bounces and complaints, not a mailbox provider's score.

Check your sending reputation with three reads. GET /trust/standing returns the account's state, one of ok, warning, throttled or paused, and reasons, each with metric, value, threshold, window and samples. GET /deliverability/domains returns every sending domain with its bounce and complaint rates over the window, worst first. GET /trust/thresholds returns the lines those rates are judged against. This reputation is the account's standing on this platform, measured from the bounces and complaints on mail sent here; it is not a score from a mailbox provider, and no page here states an inbox rate.

The account's standing

The summary of GET /trust/standing is "This account’s standing, machine-readable. An agent can query it and back off before enforcement does it for them." When state is ok, reasons is empty. Otherwise each reason carries metric (bounce or complaint), the measured value and the threshold it crossed as fractions, the window in days, the message recorded when the step happened, since, and samples, each a message with email_id, subject, to_domain and status. next_review_at says when the standing is reassessed, and history is its timeline.

curl -sS -X GET https://api.agentisend.com/trust/standing \
  -H "Authorization: Bearer $AGENTISEND_API_KEY"
200
{
  "history": [],
  "next_review_at": "2026-09-04T09:14:00Z",
  "reason_codes": [],
  "reasons": [],
  "sla_deadline_at": "2026-09-04T09:14:00Z",
  "state": "ok"
}
Response

The lines come from GET /trust/thresholds, whose summary opens with "The published enforcement thresholds and the ladder they drive." Bounce rate warns at 2% and pauses at 4%; complaint rate warns at 0.05% and pauses at 0.08%. No step is taken until the window of 7 days holds 100 delivered-or-bounced sends. Trust and enforcement says the ladder has two rungs, warn and pause, and never enters a throttle rung; throttled stays in the API for older clients. Deliverability says standing is hysteretic: a rate that dips back under a line does not clear at that instant, it clears at the next review. When state is not ok, POST /trust/appeal asks a person to look, and the guide says an appeal is for a wrong reading, not a way to raise a threshold.

Per domain

GET /deliverability/domains is the account by domain. Its summary is "Every sending domain with its standing over the window, worst first — the failing domain is the first row, not one you have to find." Each row has name, sent, bounce_rate, complaint_rate and standing, one of no_data, ok, warning or over_limit; window_days is a query parameter. A domain that has sent nothing is no_data, not ok.

GET /deliverability/domains/{id} is one domain in depth. Its summary is "Per-domain reputation: live rates over the rolling window, daily snapshots, the thresholds those rates are judged against, the bounce breakdown by class with its remediation, and the receiving domains rejecting the most." live carries sent, delivered, bounced, complained, bounce_rate and complaint_rate; snapshots is one row per day; each entry in bounce_classes has class, count, share and a remediation with meaning and fix; top_recipient_domains names where the bounces come from. The thresholds on these two routes are the panel's amber and red lines, which the Deliverability guide separates from the enforcement lines: one is when a person should look, the other is when the platform acts.

Authentication and raw counts

GET /deliverability/dmarc reads the aggregate authentication reports. Its summary promises "every address sending as you, flagged when it is not one of ours", so a row in sources with ours: false is another system using your domain. GET /usage returns sent_30d, bounced_30d and complained_30d under account, the counts the rates are made of.

What moves it

The Deliverability guide lists four things: send to addresses that asked for mail, publish SPF, DKIM and DMARC and keep them published, handle bounces the day they happen, and raise volume gradually on a new domain. The enforcement policy behind the numbers is at /policy/enforcement.

Next