Compare

Hunter vs Mailgun

Mailgun scores higher on the AgentReady, 58/100 against 57/100. They differ on 5 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Hunter. Hunter is an all-in-one email outreach platform for finding and connecting with professional contacts.

Mailgun. Transactional Email Delivery Service & API for Developers.

Where Hunter is ahead

Hunter passes llms.txt published and llms-full.txt / full agent docs, and Mailgun does not. That is discover, whether an agent can find the product at all without being told it exists.

Where Mailgun is ahead

Mailgun passes clear product positioning, and Hunter does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds adopt: fast time to first request and copyable quickstart. Hunter misses those.

What neither does

Both fail public docs discoverable, structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, programmatic credential creation, cli available, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover. Both sit at 73/100 here. Hunter misses clear product positioning, public docs discoverable; Mailgun misses public docs discoverable, llms.txt published, llms-full.txt / full agent docs.

Understand. Both sit at 31/100 here. Hunter misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Mailgun misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt is whether an agent can get a key and make its first successful call without a human in the loop. Mailgun leads 75 to 67. Hunter misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, cli available; Mailgun misses no mandatory sales call, programmatic credential creation, cli available.

Operate. Hunter leads 56 to 53. Hunter misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Mailgun misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable.

Pricing

Hunter does not publish a machine-readable starting price and has a free tier. Mailgun does not publish one and has a free tier.

Signal by signal

Which to pick

Mailgun clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Hunter and Mailgun. Alternatives to each: Hunter, Mailgun.

An agent can fetch this as data: POST /v1/compare {"slugs": ["hunter", "mailgun"]}