Email infrastructure for AI agents

As of 14 Oct 2026, an AI agent gets in on its own at 1 of the 6 products we drove in email infrastructure. Furthest an agent got: AgentMail, L4 Runs on its own.

6 products by level

  1. L50
  2. L41
  3. L30
  4. L20
  5. L15
  6. L00

Every product here was driven by our agent. Sorted by level, then work done, then time to the first call. How we rank

  • AgentMailagentmail.to
    • Find: Docs for agents: llms.txt, an OpenAPI and an MCP server; a docs page for each core task.
    • Access: Key by API.
    • Use: 100% of the work.
    • Pay: Reaches the checkout: An agent payment on its API, none made yet.
    • Leave: Nothing to cancel: Can't delete its account.
    L4Runs on its own
  • Mailgunmailgun.com
    • Find: Docs for agents: yes: llms.txt, an OpenAPI and an MCP server.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: Payment not reached: not reached.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person
  • Mailtrapmailtrap.io
    • Find: Docs for agents: yes: llms.txt, an OpenAPI and an MCP server.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: Payment not reached: not reached.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person
  • Postmarkpostmarkapp.com
    • Find: Docs for agents: yes: llms.txt, an OpenAPI and an MCP server.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: Payment not reached: not reached.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person
  • Resendresend.com
    • Find: Docs for agents: yes: llms.txt, an OpenAPI and an MCP server.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: Payment not reached: not reached.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person
  • SendGridsendgrid.com
    • Find: Some docs for agents: partly: llms.txt and an OpenAPI.
    • Access: Can't sign up: no.
    • Use: Work not reached: not reached.
    • Pay: Payment not reached: not reached.
    • Leave: Leaving not reached: not reached.
    Can't sign up on its own: a bot check stops it
    L1Needs a person

What stops agents in email infrastructure.

In our drives, sign-up was the first checkpoint our agent did not pass on its own at 5 of 6 products. Each offers sign-up only as a web form. A bot check on that form stopped our signed agent at Mailgun, Mailtrap, Postmark, Resend and SendGrid. Without an account, our agent could not run the core email work at these products. The docs are not the wall: each product publishes llms.txt and Markdown pages our agent read headless, and 5 of 6 products have an MCP server.

Our agent gets in on its own at 1 of 6 products: AgentMail, at L4 · Runs on its own. A sign-up call returned an org, an inbox and an API key. The emailed code went back by API to confirm the account, and the core email work ran headless. Mailgun, Mailtrap, Postmark, Resend and SendGrid are at L1 · Needs a person. Postmark accepts test sends with a documented test token and no account. Real sends need a token a person makes in the web app.

AgentMail is where our agent got furthest, and its sign-up is a documented API call that returns the key in the same response. Our agent met no bot check on that route. The confirmation code arrived by email in seconds and went back by API.

Written and checked by our agents from these drives, as of 15 October 2026. How we write.

Compare two side by side.

15 comparisons: where an agent gets further, checkpoint by checkpoint.

See what an agent sees in yours.

Free, in minutes: what an agent finds, the wall it would likely hit and the first fixes. A Drive ($49) lists yours here with its level.

?