{ "data": { "a": { "slug": "aurinko-email", "name": "Aurinko Email API", "vendor": "Yoxel, Inc.", "vendorUrl": "https://www.aurinko.io", "kind": "http-api", "category": "mailbox-access", "summary": "Unified email REST API from Yoxel, Inc. It reads, searches, drafts and sends mail in a user's own mailbox on Gmail, Office 365, Outlook.com, Exchange, Zoho Mail, iCloud and IMAP, with delta sync, open and reply tracking and webhooks.", "url": "https://www.anchorterminal.com/tools/aurinko-email", "markdownUrl": "https://www.anchorterminal.com/tools/aurinko-email.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aurinko-email.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aurinko-email.json", "license": "Proprietary service under Yoxel's Terms of Services Agreement", "transports": [ "http" ], "remoteUrl": "https://api.aurinko.io", "packages": [], "auth": "oauth", "authNotes": "Self-serve. A developer signs up at app.aurinko.io and gets a client ID and secret for each application. Each mailbox owner connects through Aurinko's OAuth flow at `/v1/auth/authorize`, and the resulting account access token is sent as a Bearer token. Mail scopes are `Mail.Read`, `Mail.ReadWrite`, `Mail.Send` and `Mail.Drafts`. IMAP, iCloud and Exchange accounts connect with a password or app password. Gmail access needs the developer's own Google OAuth app, since Aurinko's default registration excludes Google email, and production Office 365 needs an Azure registration.", "pricing": "paid", "pricingNotes": "$1.50 an active account a month for Email (non-IMAP) with up to 1 GB of traffic, and $2 for any number of APIs including IMAP with unlimited traffic, per the billing FAQ. A 14-day trial gives full API access, and requests are blocked when it ends without a card on file. No free tier or sandbox beyond the trial (https://docs.aurinko.io/faq/how-does-aurinko-billing-work).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI description or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.aurinko.io/unified-apis/email-api", "llmsTxt": "https://docs.aurinko.io/llms.txt", "openapi": "https://apirefs.aurinko.io/assets/swagger.json", "capabilities": [ "mailbox.read", "mailbox.search", "mailbox.send", "mailbox.drafts", "mailbox.sync", "email.threads" ], "tags": [ "hosted", "oauth", "openapi", "llms-txt", "webhooks", "closed-source", "free-trial" ], "graded": true, "anchor": { "graded": true, "score": 44.2, "grade": "E", "agentReady": false, "rank": 878, "ranked": true, "rankOf": 950, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 49, "maintenance": 13, "payments": 40, "reliability": 40, "schema": 67, "security": 42, "transparency": 44 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public OpenAPI 3.0 description at `apirefs.aurinko.io/assets/swagger.json`, with 43 email operations, 34 of them carrying a cURL sample", "Four mail scopes. `Mail.Read` allows no writes, `Mail.Send` allows sending with no read access, and `Mail.ReadWrite` excludes send", "The `q` parameter takes 17 search operators, with a table in the docs saying where IMAP and Exchange support is partial", "Prices published per active account a month ($1.50 for email, $2 for all APIs with IMAP), with a 14-day trial", "Docs state that message contents are passed through and never stored, with only IDs and thread relations cached for sync" ], "weaknesses": [ "No status page, incident history or SLA found, and the terms supply the service as is", "No idempotency key on `POST /v1/email/messages`, so a retried send can deliver twice", "No changelog, deprecation policy or official SDK found in the docs or on the site", "The application's client ID and secret, sent as Basic auth, reach every connected mailbox, and IMAP accounts hand Aurinko a mailbox password", "The terms of 11 August 2022 forbid robots and data extraction methods in connection with the Services. This matters before any probe is run" ], "agentNotes": [ "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`", "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", "Call `POST /v1/email/sync` until `ready` is true, then page `/v1/email/sync/updated` with `pageToken` until a `nextDeltaToken` appears and store it", "Check the `omitted` array on message lists. Full bodies come only from Google and Office 365, and other providers return a snippet", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.2 } ], "editorialScores": { "ergonomics": 49, "maintenance": 13, "payments": 40, "reliability": 40, "schema": 67, "security": 42, "transparency": 27 }, "provenanceScore": 60 }, "connect": { "http": "curl -H 'Authorization: Bearer \u003caccess_token\u003e' \\\n -G https://api.aurinko.io/v1/email/messages \\\n -d q='from:alexey'" }, "letme": { "capability": "https://letme.dev/mailbox.read", "tool": "https://letme.dev/aurinko-email" }, "sameCompany": [ "aurinko-calendar" ], "area": "communication", "unitPrices": [ { "item": "Email API (non-IMAP)", "unit": "account-month", "usd": 1.5, "note": "Per active account, up to 1 GB of traffic a month" }, { "item": "Full platform, any number of APIs including IMAP", "unit": "account-month", "usd": 2, "note": "Per active account, unlimited traffic" } ], "provenance": { "legalEntity": "Yoxel, Inc.", "domain": "aurinko.io", "domainRegistered": "2019-05-08", "endpointOnVendorDomain": true, "terms": "https://www.aurinko.io/terms/", "privacy": "https://www.aurinko.io/privacy/", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Services Agreement, last updated 11 August 2022, names Yoxel, Inc., organised under the laws of California, and covers the API and the workspace integrations platform. Disputes go to binding arbitration under JAMS rules in San Francisco, with a 30-day opt-out.", "The privacy policy, last updated 11 August 2022, covers the site and the services, API included, and commits to Google's API Services User Data Policy and its Limited Use requirements.", "The terms forbid robots, data mining and similar data extraction or gathering methods in connection with the Services. We read a handful of public pages and sent nothing to the API host.", "The API answers at api.aurinko.io per the description file, with the portal at app.aurinko.io and the reference at apirefs.aurinko.io, all on the vendor's domain.", "www.aurinko.io/.well-known/security.txt returns 404. The security statement gives security@yoxel.com for reports.", "No status page or changelog is linked from the home page, the docs index or the description file.", "robots.txt on www.aurinko.io has one `User-agent: *` line and no rules. On docs.aurinko.io it allows every path with `Content-Signal: ai-input=yes`. apirefs.aurinko.io answered 404 for robots.txt, read as no rules.", "RDAP for aurinko.io gives a registration date of 2019-05-08." ], "score": 60 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/aurinko-email.json", "live": { "slug": "aurinko-email", "probe": { "target": "https://api.aurinko.io", "method": "get", "lastAt": "2026-10-10T03:53:19.824177005Z", "lastOk": true, "lastStatus": 404, "lastMs": 232, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 126, "p95ms24h": 280, "samples24h": 125, "samples30d": 125, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 40, "ok": 40 } ] }, "updatedAt": "2026-10-10T03:53:19.824177005Z" } }, "answer": "Himalaya scores 64.5 (B) on agent readiness against Aurinko Email API's 44.2 (E), and leads in every scored category.", "b": { "slug": "himalaya", "name": "Himalaya", "vendor": "Pimalaya", "vendorUrl": "https://pimalaya.org", "kind": "sdk", "category": "mailbox-access", "summary": "Himalaya is an open-source command-line email client from the Pimalaya project. It lists, searches, reads, composes and sends mail over IMAP, SMTP, JMAP, the Gmail API, Microsoft Graph and local stores, with JSON output for scripts and agents.", "url": "https://www.anchorterminal.com/tools/himalaya", "markdownUrl": "https://www.anchorterminal.com/tools/himalaya.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/himalaya.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/himalaya.json", "repo": "https://github.com/pimalaya/himalaya", "license": "MIT OR Apache-2.0", "transports": [], "packages": [ { "registry": "cargo", "name": "himalaya" } ], "auth": "mixed", "authNotes": "Himalaya issues no credential of its own. It signs in to the mailbox with what the provider accepts, which is an app password or account password over SASL for IMAP and SMTP, a bearer token or basic auth for JMAP, and one OAuth 2.0 bearer token for the Gmail API or Microsoft Graph. Each secret is read from a shell command such as a password manager, or from a raw value in the config file. Version 2 ships no OAuth flow, so tokens come from an external broker such as `ortie` and an OAuth app the owner registers with Google or Microsoft.", "pricing": "free", "pricingNotes": "Free software with nothing to buy, and the sponsor page states there is no paid tier. An agent can start with the binary and a mailbox credential. Pimalaya sells optional partnerships, from EUR 3,000 a year for email providers and EUR 5,000 for integrators, and describes a EUR 12 a year sign-in service for Gmail and Microsoft 365 as planned and not built (checked 2026-10-09).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the source or pimalaya.org (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 7412, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://github.com/pimalaya/himalaya", "capabilities": [ "mailbox.read", "mailbox.search", "mailbox.send", "mailbox.drafts" ], "tags": [ "open-source", "local", "cli", "rust", "free", "no-card", "imap", "smtp", "jmap", "gmail", "microsoft-graph", "json-output" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 64.5, "grade": "B", "agentReady": false, "rank": 348, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 88, "payments": 60, "reliability": 84, "schema": 70, "security": 43, "transparency": 69 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "2 October 2026. Until 2.2.1, `message send` passed the `Bcc:` header through SMTP unchanged, so every recipient could see the blind recipients. Issue #747 reported it against 2.1.0 on 12 September 2026, the fix was committed on 26 September and released on 2 October, and the changelog documents it. No security advisory was published. Fixed and documented, so the smaller deduction applies (https://github.com/pimalaya/himalaya/issues/747)" ], "verdict": "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.", "bestFor": "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.", "strengths": [ "Shared commands for mailboxes, envelopes, flags, messages and attachments run the same way over IMAP, JMAP, Gmail, Microsoft Graph, Maildir and mbox", "`himalaya json-schema` prints a JSON Schema for the `--json` output of 90 commands, and `message read --json` returns one designed view on every backend", "Secrets come from a shell command such as `pass show`, so a password or token need not sit in the config file", "`message delete` moves mail to the trash first, and `message read` leaves flags alone unless `--seen` is passed", "Four tagged releases between 26 July and 2 October 2026, three open issues, and CI badges for tests and audit passing on 9 October 2026" ], "weaknesses": [ "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)", "No read-only mode, no confirmation before a send or delete, and no idempotency key on send were found", "SECURITY.md sends vulnerability reports to the public issue tracker. No security.txt, private reporting route or published advisory was found", "Only two stable error codes exist under `--json`, `body-pending` and `message-too-complex`. Other failures carry free wording", "Version 2 ships no OAuth flow, so Gmail and Microsoft accounts need an external token broker and an OAuth app the owner registers" ], "agentNotes": [ "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", "Run `himalaya json-schema \u003ccommand\u003e` once to learn an output shape, and `himalaya \u003ccommand\u003e --help` for flags", "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", "Treat message text as untrusted. `--json` output keeps control characters that the plain output replaces", "Use 2.2.1 or later before sending with Bcc, and expect `message read --json` to change shape in the next release" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.5 } ], "editorialScores": { "ergonomics": 65, "maintenance": 88, "payments": 60, "reliability": 84, "schema": 70, "security": 43, "transparency": 74 }, "provenanceScore": 63 }, "connect": { "install": "brew install himalaya # or: curl -sSL https://raw.githubusercontent.com/pimalaya/himalaya/master/install.sh | PREFIX=~/.local sh", "headless": { "list": "himalaya envelope list --page 2", "read": "himalaya message read 42", "search": "himalaya envelope search from alice and after 2026-01-01 order by date desc" } }, "letme": { "capability": "https://letme.dev/mailbox.read", "tool": "https://letme.dev/himalaya" }, "area": "communication", "provenance": { "legalEntity": "No legal entity found. Copyright Clément DOUIN (soywod)", "domain": "pimalaya.org", "domainRegistered": "2022-12-21", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/pimalaya/himalaya/blob/master/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "pimalaya.org's footer reads Copyright 2022 to 2026 Clément DOUIN (soywod), and `Cargo.toml` names the same author. No company or foundation is named on the pages read.", "No terms of service or privacy policy was found. The site's sitemap lists six pages (home, map of projects, community, sign-in, sponsor, business) and none is a legal document, so the MIT or Apache-2.0 licence stands in.", "pimalaya.org/.well-known/security.txt and /security.txt both return 404. SECURITY.md in the repository lists 2.x as the supported line and gives the public issue tracker for reports.", "RDAP for pimalaya.org gives a registration date of 2022-12-21 and OVH sas as registrar.", "The software runs on the owner's machine and connects to the owner's mail servers, so no vendor endpoint exists." ], "score": 63 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/himalaya.json", "live": { "slug": "himalaya", "versions": [ { "registry": "github", "name": "pimalaya/himalaya", "version": "v2.2.1", "released": "2026-10-02", "seenAt": "2026-10-09T16:57:44.106760361Z" } ], "githubStars": 7417, "pages": [ { "url": "https://raw.githubusercontent.com/pimalaya/himalaya/master/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:45:53.201845848Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cb5190799b74" } ], "updatedAt": "2026-10-09T18:45:53.201845848Z" } }, "facts": [ { "a": "HTTP API", "b": "SDK + MCP", "name": "Kind" }, { "a": "Yoxel, Inc.", "b": "Pimalaya", "name": "Vendor" }, { "a": "https://api.aurinko.io", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Yoxel's Terms of Services Agreement", "b": "MIT OR Apache-2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "none", "b": "2026-10-02", "name": "Last release" }, { "a": "2022-08-11", "b": "no document linked", "name": "Terms last updated" }, { "a": "2022-08-11", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "yes", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "7.4k stars", "name": "Popularity" } ], "faq": [ { "answer": "Himalaya scores 64.5 (B) on agent readiness against Aurinko Email API's 44.2 (E), and leads in every scored category.", "question": "Which is better for AI agents, Aurinko Email API or Himalaya?" }, { "answer": "Aurinko Email API has a hosted endpoint at https://api.aurinko.io. No hosted endpoint is listed for Himalaya.", "question": "Can an agent call Aurinko Email API and Himalaya without installing anything?" }, { "answer": "No open-source release is listed for Aurinko Email API. Himalaya is open source (MIT OR Apache-2.0).", "question": "Are Aurinko Email API and Himalaya open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "A hosted endpoint, with nothing to install", "No incidents deducted, where Himalaya loses 3 points for them" ], "goodFor": "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.", "slug": "aurinko-email", "watchFor": "No status page, incident history or SLA found, and the terms supply the service as is" }, { "aheadOn": [ "Reliability, 84 against 40", "Agent ergonomics, 65 against 49", "Payments \u0026 pricing, 60 against 40", "Maintenance \u0026 community, 88 against 13", "Transparency \u0026 trust, 69 against 44" ], "also": [ "Free to start without a card", "Open source" ], "goodFor": "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.", "slug": "himalaya", "watchFor": "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)" } ], "job": { "capability": "mailbox.read", "name": "Mailbox access" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-emailengine.json", "title": "Aurinko Email API vs EmailEngine", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-emailengine" }, { "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-fastmail.json", "title": "Aurinko Email API vs Fastmail API (JMAP)", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-fastmail" }, { "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-gmail-api.json", "title": "Aurinko Email API vs Gmail API", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-gmail-api" }, { "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.json", "title": "Aurinko Email API vs Nylas Email API", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email" }, { "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-outlook-mail-graph.json", "title": "Aurinko Email API vs Outlook Mail (Microsoft Graph)", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-outlook-mail-graph" }, { "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-unipile.json", "title": "Aurinko Email API vs Unipile", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-unipile" }, { "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-zoho-mail.json", "title": "Aurinko Email API vs Zoho Mail API", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-zoho-mail" }, { "json": "https://www.anchorterminal.com/compare/emailengine-vs-himalaya.json", "title": "EmailEngine vs Himalaya", "url": "https://www.anchorterminal.com/compare/emailengine-vs-himalaya" }, { "json": "https://www.anchorterminal.com/compare/fastmail-vs-himalaya.json", "title": "Fastmail API (JMAP) vs Himalaya", "url": "https://www.anchorterminal.com/compare/fastmail-vs-himalaya" }, { "json": "https://www.anchorterminal.com/compare/gmail-api-vs-himalaya.json", "title": "Gmail API vs Himalaya", "url": "https://www.anchorterminal.com/compare/gmail-api-vs-himalaya" }, { "json": "https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.json", "title": "Himalaya vs Nylas Email API", "url": "https://www.anchorterminal.com/compare/himalaya-vs-nylas-email" }, { "json": "https://www.anchorterminal.com/compare/himalaya-vs-outlook-mail-graph.json", "title": "Himalaya vs Outlook Mail (Microsoft Graph)", "url": "https://www.anchorterminal.com/compare/himalaya-vs-outlook-mail-graph" }, { "json": "https://www.anchorterminal.com/compare/himalaya-vs-unipile.json", "title": "Himalaya vs Unipile", "url": "https://www.anchorterminal.com/compare/himalaya-vs-unipile" }, { "json": "https://www.anchorterminal.com/compare/himalaya-vs-zoho-mail.json", "title": "Himalaya vs Zoho Mail API", "url": "https://www.anchorterminal.com/compare/himalaya-vs-zoho-mail" } ], "scores": [ { "aurinko-email": 40, "by": 44, "edge": "himalaya", "himalaya": 84, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aurinko-email": 67, "by": 3, "edge": "himalaya", "himalaya": 70, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "aurinko-email": 49, "by": 16, "edge": "himalaya", "himalaya": 65, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "aurinko-email": 42, "by": 1, "edge": "himalaya", "himalaya": 43, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "aurinko-email": 40, "by": 20, "edge": "himalaya", "himalaya": 60, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aurinko-email": 13, "by": 75, "edge": "himalaya", "himalaya": 88, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "aurinko-email": 44, "by": 25, "edge": "himalaya", "himalaya": 69, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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.", "verdicts": { "aurinko-email": "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya", "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.md", "slim": "https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.min.md" }, "markdown": "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.\n\n- Aurinko Email API: grade E, 44.2/100, rank #878 of 950. Markdown https://www.anchorterminal.com/tools/aurinko-email.md · JSON https://www.anchorterminal.com/api/v1/tools/aurinko-email.json\n- Himalaya: grade B, 64.5/100, rank #348 of 950. Markdown https://www.anchorterminal.com/tools/himalaya.md · JSON https://www.anchorterminal.com/api/v1/tools/himalaya.json\n- Best mailbox access APIs for AI agents: https://www.anchorterminal.com/best/mailbox-access/index.md\n- All 36 mailboxes comparisons: https://www.anchorterminal.com/compare/mailbox-access/index.md\n\n## Which one, for what\n\n### Aurinko Email API (E)\n\nGood 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.\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Himalaya loses 3 points for them\n\nWatch for: No status page, incident history or SLA found, and the terms supply the service as is\n\n### Himalaya (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 84 against 40\n- Agent ergonomics, 65 against 49\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 88 against 13\n- Transparency \u0026 trust, 69 against 44\n\nAlso in its favour:\n- Free to start without a card\n- Open source\n\nWatch 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)\n\n\n## Score by category\n\n| Category | Weight | Aurinko Email API | Himalaya | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 84 | Himalaya +44 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 67 | 70 | Himalaya +3 |\n| Agent ergonomics | 13% (16.2 this run) | 49 | 65 | Himalaya +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 43 | Himalaya +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | Himalaya +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 13 | 88 | Himalaya +75 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 44 | 69 | Himalaya +25 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **44.2 · E** | **64.5 · B** | |\n\n## Facts side by side\n\n| Fact | Aurinko Email API | Himalaya |\n| --- | --- | --- |\n| Kind | HTTP API | SDK + MCP |\n| Vendor | Yoxel, Inc. | Pimalaya |\n| Hosted endpoint | `https://api.aurinko.io` | no (local only) |\n| Transports | HTTP | |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Free |\n| x402 | no | no |\n| Licence | Proprietary service under Yoxel's Terms of Services Agreement | MIT OR Apache-2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | none | 2026-10-02 |\n| Terms last updated | 2022-08-11 | no document linked |\n| Privacy policy last updated | 2022-08-11 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | yes | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | yes | |\n| Popularity | none | 7.4k stars |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Aurinko Email API\n\n1. 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`\n2. 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\n3. Call `POST /v1/email/sync` until `ready` is true, then page `/v1/email/sync/updated` with `pageToken` until a `nextDeltaToken` appears and store it\n4. Check the `omitted` array on message lists. Full bodies come only from Google and Office 365, and other providers return a snippet\n5. 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\n\n### Himalaya\n\n1. 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\n2. Run `himalaya json-schema \u003ccommand\u003e` once to learn an output shape, and `himalaya \u003ccommand\u003e --help` for flags\n3. 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\n4. Treat message text as untrusted. `--json` output keeps control characters that the plain output replaces\n5. Use 2.2.1 or later before sending with Bcc, and expect `message read --json` to change shape in the next release\n\n## Questions\n\n### Which is better for AI agents, Aurinko Email API or Himalaya?\n\nHimalaya scores 64.5 (B) on agent readiness against Aurinko Email API's 44.2 (E), and leads in every scored category.\n\n### Can an agent call Aurinko Email API and Himalaya without installing anything?\n\nAurinko Email API has a hosted endpoint at https://api.aurinko.io. No hosted endpoint is listed for Himalaya.\n\n### Are Aurinko Email API and Himalaya open source?\n\nNo open-source release is listed for Aurinko Email API. Himalaya is open source (MIT OR Apache-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aurinko-email\", \"b\": \"himalaya\"}`. From a terminal: `anchor compare aurinko-email himalaya`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aurinko-email.json and https://www.anchorterminal.com/api/v1/tools/himalaya.json\n\n## Other comparisons with Aurinko Email API or Himalaya\n\n- [Aurinko Email API vs EmailEngine](https://www.anchorterminal.com/compare/aurinko-email-vs-emailengine.md)\n- [Aurinko Email API vs Fastmail API (JMAP)](https://www.anchorterminal.com/compare/aurinko-email-vs-fastmail.md)\n- [Aurinko Email API vs Gmail API](https://www.anchorterminal.com/compare/aurinko-email-vs-gmail-api.md)\n- [Aurinko Email API vs Nylas Email API](https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.md)\n- [Aurinko Email API vs Outlook Mail (Microsoft Graph)](https://www.anchorterminal.com/compare/aurinko-email-vs-outlook-mail-graph.md)\n- [Aurinko Email API vs Unipile](https://www.anchorterminal.com/compare/aurinko-email-vs-unipile.md)\n- [Aurinko Email API vs Zoho Mail API](https://www.anchorterminal.com/compare/aurinko-email-vs-zoho-mail.md)\n- [EmailEngine vs Himalaya](https://www.anchorterminal.com/compare/emailengine-vs-himalaya.md)\n- [Fastmail API (JMAP) vs Himalaya](https://www.anchorterminal.com/compare/fastmail-vs-himalaya.md)\n- [Gmail API vs Himalaya](https://www.anchorterminal.com/compare/gmail-api-vs-himalaya.md)\n- [Himalaya vs Nylas Email API](https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.md)\n- [Himalaya vs Outlook Mail (Microsoft Graph)](https://www.anchorterminal.com/compare/himalaya-vs-outlook-mail-graph.md)\n- [Himalaya vs Unipile](https://www.anchorterminal.com/compare/himalaya-vs-unipile.md)\n- [Himalaya vs Zoho Mail API](https://www.anchorterminal.com/compare/himalaya-vs-zoho-mail.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Aurinko Email API vs Himalaya", "url": "" } ], "description": "Himalaya scores 64.5 (B) to Aurinko Email's 44.2 (E) for mailbox access. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Aurinko Email API E 44.2", "Himalaya B 64.5", "scores" ], "h1": "Aurinko Email API vs Himalaya", "image": "https://www.anchorterminal.com/assets/og/compare-aurinko-email-vs-himalaya.png", "path": "/compare/aurinko-email-vs-himalaya", "published": "2026-10-01", "section": "tools", "title": "Aurinko Email vs Himalaya for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya" }, "tokens": { "markdown": 2250, "slim": 680 }, "version": 1 }