For agents · Published 2026-09-29 · Updated 2026-09-29 · AgentiSend
Support for agents
Diagnose with explain_email, why_was_this_not_sent and the status page, then a person opens a support request. Never include a key.
Diagnose before anyone opens a request. Call explain_email with the message id, or why_was_this_not_sent with that id or with none to read what is blocking this key. Check the status page. If the status page shows an outage, wait for it. A refusal's fix names the next call.
What a person sends
POST /support opens a request. It answers a signed-in console session. An API key is refused. The body is topic, subject, message, and optionally related_type (domain, email, api_key or webhook) and related_id.
Include the message id, the x-request-id from the response, the code and the fix. Name an API key by its id, never by the key itself. Do not include a key, a webhook signing secret, or a password. The account snapshot stored with the request does not include those either.
Topics, hours and attachment limits are GET /support/config. The human guide is Support. Write to hello@agentisend.com only when the console form is the wrong door: a security report, with "Security" in the subject.
The published skill
Clients that discover skills read /.well-known/agent-skills/index.json. It points at the published SKILL.md.