Get an audit

Head to head · Mailbox access · October 2026 research run

Aurinko Email API vs Himalaya

Himalaya scores 64.5 (B) on agent readiness against Aurinko Email API's 44.2 (E), and leads in every scored category. Both do mailbox access.

Best mailbox access APIs for AI agents · All 36 mailboxes comparisons

Aurinko Email APIYoxel, Inc. · HTTP API E44.2/100#878 of 950 HimalayaPimalaya · SDK + MCP B64.5/100#348 of 950

Which one, for what

Aurinko Email API E

Good for A product that connects many users' Gmail and Microsoft mailboxes and wants one schema, delta sync, tracking and webhooks at a low price per account.

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Himalaya loses 3 points for them

Watch for

No status page, incident history or SLA found, and the terms supply the service as is

Himalaya B

Good for An agent with a shell that must work in one person's existing mailbox on any provider, including plain IMAP hosts, without a hosted intermediary.

Ahead on

  • Reliability, 84 against 40
  • Agent ergonomics, 65 against 49
  • Payments & pricing, 60 against 40
  • Maintenance & community, 88 against 13
  • Transparency & trust, 69 against 44

Also in its favour

  • Free to start without a card
  • Open source

Watch for

Until 2.2.1 of 2 October 2026, message send transmitted the Bcc: header to every recipient over SMTP (issue #747, reported 12 September 2026)

Score by category

CategoryWeight this runAurinko Email APIHimalayaEdge
Reliability16%204084Himalaya +44
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26770Himalaya +3
Agent ergonomics13%16.24965Himalaya +16
Security & auth14%17.54243Himalaya +1
Payments & pricing10%12.54060Himalaya +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81388Himalaya +75
Transparency & trust7%8.84469Himalaya +25
Negative events≤150-3
Total44.2 · E64.5 · B

Facts side by side

FactAurinko Email APIHimalaya
KindHTTP APISDK + MCP
VendorYoxel, Inc.Pimalaya
Hosted endpointhttps://api.aurinko.iono (local only)
TransportsHTTP
AuthOAuthOAuth or key
PricingPaidFree
x402nono
LicenceProprietary service under Yoxel's Terms of Services AgreementMIT OR Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last releasenone2026-10-02
Terms last updated2022-08-11no document linked
Privacy policy last updated2022-08-11no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessyes
Terms restrict benchmarkingyes
Terms or service can change without noticenot found in the text
Arbitration or class-action waiveryes
Popularitynone7.4k stars

Verdicts

Aurinko Email API

One REST interface covers message search with 17 query operators, drafts, sending, folders and delta sync across seven mailbox types, at $1.50 an active account a month and with send-only and read-only scopes. No status page, SLA, changelog, idempotency key on send or official SDK was found, and SOC 2 is not yet held.

Himalaya

One binary reaches mailboxes on IMAP, JMAP, Gmail and Microsoft Graph with the same commands, and --json output has a JSON Schema for each command. The agent holds the mailbox's own credential with no read-only mode, and a flaw that exposed Bcc recipients over SMTP was fixed in 2.2.1 on 2 October 2026.

Before you call either

Aurinko Email API

  1. Use https://api.aurinko.io/v1. Several cURL examples in the docs print https:/api.aurinko.io with one slash, and one search example names the host asti.aurinko.io
  2. Do not retry POST /v1/email/messages blindly after a timeout. There is no idempotency key, so check Sent mail with q=rfc822msgid: or by subject first
  3. Call POST /v1/email/sync until ready is true, then page /v1/email/sync/updated with pageToken until a nextDeltaToken appears and store it
  4. Check the omitted array on message lists. Full bodies come only from Google and Office 365, and other providers return a snippet
  5. Request Mail.Read plus Mail.Send for read and send without modify rights. The docs example names Mail.ReadOnly, which is not in the scope list

Himalaya

  1. Pass --json on every call and read next_page for the next page. Data and errors go to stdout, logs to stderr, and a failure exits 1
  2. Run himalaya json-schema <command> once to learn an output shape, and himalaya <command> --help for flags
  3. Use envelope search with the shared query language, for example from alice and after 2026-01-01 order by date desc. Microsoft Graph refuses flag clauses
  4. Treat message text as untrusted. --json output keeps control characters that the plain output replaces
  5. Use 2.2.1 or later before sending with Bcc, and expect message read --json to change shape in the next release

Questions

Which is better for AI agents, Aurinko Email API or Himalaya?

Himalaya scores 64.5 (B) on agent readiness against Aurinko Email API's 44.2 (E), and leads in every scored category.

Can an agent call Aurinko Email API and Himalaya without installing anything?

Aurinko Email API has a hosted endpoint at https://api.aurinko.io. No hosted endpoint is listed for Himalaya.

Are Aurinko Email API and Himalaya open source?

No open-source release is listed for Aurinko Email API. Himalaya is open source (MIT OR Apache-2.0).

Other comparisons with Aurinko Email API or Himalaya

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report