Mailgun vs SuperTokens
Mailgun scores higher on the AgentReady, 58/100 against 54/100. They differ on 10 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Mailgun. Transactional Email Delivery Service & API for Developers.
SuperTokens. Open source user authentication platform that helps developers build fast, maintain control, and reduce costs.
Where Mailgun is ahead
Mailgun passes self-service signup, agent-compatible signup flow and fast time to first request, and SuperTokens does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.
It also holds operate: observable execution and agent compatibility verified. SuperTokens misses those.
Where SuperTokens is ahead
SuperTokens passes public docs discoverable, 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.
It also holds adopt: no mandatory sales call and cli available. Mailgun misses those.
What neither does
Both fail structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, programmatic credential creation, 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. SuperTokens leads 100 to 73. Mailgun misses public docs discoverable, llms.txt published, llms-full.txt / full agent docs; SuperTokens misses nothing.
Understand. Both sit at 31/100 here. Mailgun misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; SuperTokens misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Mailgun leads 75 to 60. Mailgun misses no mandatory sales call, programmatic credential creation, cli available; SuperTokens misses self-service signup, agent-compatible signup flow, programmatic credential creation, fast time to first request.
Operate is whether an agent can run against it in production and recover when a call fails. Mailgun leads 53 to 24. Mailgun misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; SuperTokens misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified.
Pricing
Mailgun does not publish a machine-readable starting price and has a free tier. SuperTokens starts at $0.02/MAU and has a free tier.
| Mailgun plans | SuperTokens plans |
|---|---|
| - | Cloud $0.02 per MAU |
| - | Self-hosted Free and open source |
Signal by signal
| Signal | Mailgun | SuperTokens |
|---|---|---|
| AgentReady | 58 | 54 |
| Discovery | 73 | 100 |
| Understanding | 31 | 31 |
| Adoption | 75 | 60 |
| Operability | 53 | 24 |
| Public API | Yes | Yes |
| MCP server | Yes | Yes |
| OpenAPI spec | Unknown | Unknown |
| CLI | Unknown | Yes |
| llms.txt | Unknown | Yes |
| Self-serve signup | Yes | Unknown |
| Free tier | Yes | Yes |
Which to pick
Signal counts are level here, so fit and price decide it. Full profiles: Mailgun and SuperTokens. Alternatives to each: Mailgun, SuperTokens.
An agent can fetch this as data: POST /v1/compare {"slugs": ["mailgun", "supertokens"]}