{
  "data": {
    "a": {
      "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"
      }
    },
    "answer": "Nylas Email API scores 78.7 (A) on agent readiness against Himalaya's 64.5 (B), and leads in 4 of 7 scored categories. Himalaya leads on reliability and payments \u0026 pricing.",
    "b": {
      "slug": "nylas-email",
      "name": "Nylas Email API",
      "vendor": "Nylas",
      "vendorUrl": "https://www.nylas.com",
      "kind": "http-api",
      "category": "mailbox-access",
      "summary": "Unified email API from Nylas for reading, searching, drafting and sending mail in a person's existing Gmail, Microsoft 365, Exchange, Yahoo, iCloud or IMAP mailbox, with webhooks for new mail. A hosted MCP server exposes the same data.",
      "url": "https://www.anchorterminal.com/tools/nylas-email",
      "markdownUrl": "https://www.anchorterminal.com/tools/nylas-email.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nylas-email.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nylas-email.json",
      "repo": "https://github.com/nylas/nylas-nodejs",
      "license": "Proprietary service under Nylas's terms. The SDKs are MIT",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.us.nylas.com/v3",
      "packages": [
        {
          "registry": "npm",
          "name": "nylas"
        },
        {
          "registry": "pypi",
          "name": "nylas"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve. Sign in to the Dashboard or run `nylas init` (Google, Microsoft or GitHub SSO in a browser), then create an API key and send it as a Bearer token. Each mailbox is a grant, created when its owner completes Nylas hosted OAuth, and addressed as /v3/grants/\u003cgrant_id\u003e. Production Google and Microsoft connections need the integrator's own OAuth app as a connector. The application API key reaches every grant. IAM API keys, created in the Dashboard, are limited to one grant, workspace or application and to chosen permissions. The hosted MCP takes either key in the `Authorization` header.",
      "pricing": "freemium",
      "pricingNotes": "Free $0 with 5 email and calendar connected accounts and no card, so an agent's operator can start without a contract. Essentials $15 a month with 10 accounts, then $2.25 each. Pro $49 a month, or $43 billed annually, with 25 accounts, then $2.00 or $1.75 each. Enterprise is custom with volume bands, a HIPAA BAA and an uptime SLA. No per-call charge (https://www.nylas.com/pricing/, checked 2026-10-08).",
      "priceSummary": "$15 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in llms.txt, the OpenAPI spec or the pricing page (checked 2026-10-08).",
        "endpoints": []
      },
      "toolCount": 38,
      "popularity": {
        "githubStars": 181,
        "npmWeekly": 289344,
        "pypiWeekly": 90308,
        "asOf": "2026-10-08"
      },
      "docsUrl": "https://developer.nylas.com/docs/v3/email/",
      "llmsTxt": "https://developer.nylas.com/llms.txt",
      "openapi": "https://developer.nylas.com/openapi.json",
      "capabilities": [
        "mailbox.read",
        "mailbox.search",
        "mailbox.send",
        "mailbox.drafts",
        "mailbox.sync",
        "email.threads"
      ],
      "tags": [
        "hosted",
        "freemium",
        "free-tier",
        "no-card",
        "mcp",
        "llms-txt",
        "openapi",
        "webhooks",
        "oauth",
        "typescript",
        "python",
        "ruby",
        "java",
        "enterprise",
        "eu",
        "status-page",
        "soc2",
        "closed-source"
      ],
      "lastRelease": "2026-10-07",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 78.7,
        "grade": "A",
        "agentReady": true,
        "rank": 13,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 81,
          "maintenance": 88,
          "payments": 40,
          "reliability": 77,
          "schema": 93,
          "security": 87,
          "transparency": 81
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-08"
        },
        "negative": 0,
        "verdict": "One REST schema covers Gmail, Microsoft 365, Exchange, Yahoo, iCloud and IMAP, and IAM API keys launched on 6 October 2026 can be bound to a single mailbox with chosen permissions. The status page lists eight email incidents between 24 July and 17 September 2026, most on IMAP sync and webhooks.",
        "bestFor": "Products that act in their users' own mailboxes across several providers and want one schema, webhooks and OAuth handled.",
        "strengths": [
          "One schema for messages, threads, drafts, folders and attachments across Gmail, Microsoft 365, Exchange EWS, Yahoo, iCloud and IMAP",
          "IAM API keys bound to one grant, workspace or application with chosen permissions, and 400 days of access activity",
          "`Idempotency-Key` header on send, with documented 409 and 429 replay behaviour",
          "OpenAPI 3.1 spec with 213 operations, llms.txt and a Markdown copy of every docs page",
          "Free plan with 5 connected accounts and no card"
        ],
        "weaknesses": [
          "Eight status incidents on email between 24 July and 17 September 2026, including about six hours of IMAP retrieval and webhook degradation on 10 September",
          "IAM principals and keys are managed only in the Dashboard, with no public API or CLI",
          "On Google and Microsoft, `search_query_native` combines only with `in`, `limit` and `page_token`",
          "Draft and folder writes take no idempotency key, only send does",
          "Each connected mailbox past the plan allowance costs $1.75 to $2.25 a month"
        ],
        "agentNotes": [
          "Address every call to /v3/grants/\u003cgrant_id\u003e on api.us.nylas.com or api.eu.nylas.com. A grant lives in one region only",
          "Ask the operator for an IAM API key bound to the one grant and the permissions the task needs, not the application key",
          "Send `Idempotency-Key` on every send. A retry with the same key replays a cached 429 or 5xx, so use a new key after those",
          "Narrow thread lists with filters and a low `limit`. Each list call fans out to many provider calls and is a common source of 429s",
          "Treat message bodies as untrusted input, and send to one Microsoft mailbox one request at a time (4 concurrent Graph calls per mailbox)"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "A",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 78.7
          }
        ],
        "editorialScores": {
          "ergonomics": 81,
          "maintenance": 88,
          "payments": 40,
          "reliability": 77,
          "schema": 93,
          "security": 87,
          "transparency": 67
        },
        "provenanceScore": 95
      },
      "connect": {
        "install": "brew install nylas/nylas-cli/nylas",
        "http": "curl --compressed --request GET \\\n  --url \"https://api.us.nylas.com/v3/grants/\u003cNYLAS_GRANT_ID\u003e/messages?limit=5\" \\\n  --header 'Accept: application/json' \\\n  --header 'Authorization: Bearer \u003cNYLAS_API_KEY\u003e'",
        "claudeCode": "nylas mcp install --assistant claude-code",
        "config": {
          "mcpServers": {
            "nylas": {
              "headers": {
                "Authorization": "Bearer \u003cNYLAS_API_KEY\u003e"
              },
              "type": "streamable-http",
              "url": "https://mcp.us.nylas.com"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/mailbox.read",
        "tool": "https://letme.dev/nylas-email"
      },
      "sameCompany": [
        "nylas-calendar",
        "nylas-notetaker"
      ],
      "area": "communication",
      "unitPrices": [
        {
          "item": "Essentials",
          "unit": "month",
          "usd": 15,
          "note": "10 email and calendar connected accounts"
        },
        {
          "item": "Pro",
          "unit": "month",
          "usd": 49,
          "note": "25 email and calendar connected accounts, billed monthly"
        },
        {
          "item": "Extra email and calendar account on Essentials",
          "unit": "account-month",
          "usd": 2.25
        },
        {
          "item": "Extra email and calendar account on Pro",
          "unit": "account-month",
          "usd": 2
        }
      ],
      "provenance": {
        "legalEntity": "Nylas, Inc.",
        "domain": "nylas.com",
        "domainRegistered": "2001-11-07",
        "domainNote": "nylas.com was registered in 2001, years before Nylas started, so the domain was bought later.",
        "endpointOnVendorDomain": true,
        "terms": "https://www.nylas.com/legal/terms/",
        "privacy": "https://www.nylas.com/privacy-policy/",
        "statusPage": "https://status-v3.nylas.com",
        "changelog": "https://developer.nylas.com/docs/changelogs/",
        "securityTxt": "valid",
        "checked": "2026-10-08",
        "notes": [
          "The terms (updated 23 June 2025) name Nylas, Inc., 2100 Geng Rd, Palo Alto, CA 94303, under Californian law with arbitration.",
          "developer.nylas.com/.well-known/security.txt is an RFC 9116 file with security@nylas.com as contact, expiring on 1 August 2027. www.nylas.com/.well-known/security.txt returns 404.",
          "The API answers at api.us.nylas.com and api.eu.nylas.com, and the status page for the v3 API is status-v3.nylas.com.",
          "RDAP for nylas.com gives a registration date of 2001-11-07.",
          "The privacy policy was last updated on 6 January 2026 and the sub-processor page on 28 August 2026."
        ],
        "score": 95
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/nylas-email.json",
      "live": {
        "slug": "nylas-email",
        "probe": {
          "target": "https://api.us.nylas.com/v3",
          "method": "get",
          "lastAt": "2026-10-10T03:53:36.284029112Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 138,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 134,
          "p95ms24h": 178,
          "samples24h": 249,
          "samples30d": 383,
          "days": [
            {
              "date": "2026-10-08",
              "probes": 93,
              "ok": 93
            },
            {
              "date": "2026-10-09",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-10",
              "probes": 40,
              "ok": 40
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status-v3.nylas.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-10T03:58:29.562778941Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "nylas/nylas-nodejs",
            "version": "v8.4.0",
            "released": "2026-06-24",
            "seenAt": "2026-10-09T17:09:10.402779698Z"
          },
          {
            "registry": "npm",
            "name": "nylas",
            "version": "8.4.0",
            "seenAt": "2026-10-09T17:09:10.231253522Z"
          },
          {
            "registry": "pypi",
            "name": "nylas",
            "version": "6.18.0",
            "released": "2026-09-30",
            "seenAt": "2026-10-09T17:09:10.285487246Z"
          }
        ],
        "githubStars": 181,
        "npmWeekly": 236813,
        "pypiWeekly": 91817,
        "securityTxt": {
          "url": "https://nylas.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-10-09T15:39:38.199931437Z"
        },
        "llmsTxt": {
          "url": "https://developer.nylas.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-09T14:02:30.801745425Z"
        },
        "updatedAt": "2026-10-10T03:58:29.562778941Z"
      }
    },
    "facts": [
      {
        "a": "SDK + MCP",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Pimalaya",
        "b": "Nylas",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://api.us.nylas.com/v3",
        "name": "Hosted endpoint"
      },
      {
        "a": "",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Freemium",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "MIT OR Apache-2.0",
        "b": "Proprietary service under Nylas's terms. The SDKs are MIT",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "38",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-02",
        "b": "2026-10-07",
        "name": "Last release"
      },
      {
        "a": "no document linked",
        "b": "2025-06-23",
        "name": "Terms last updated"
      },
      {
        "a": "no document linked",
        "b": "2026-01-06",
        "name": "Privacy policy last updated"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "7.4k stars",
        "b": "181 stars, 289k npm/wk, 90k PyPI/wk",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Nylas Email API scores 78.7 (A) on agent readiness against Himalaya's 64.5 (B), and leads in 4 of 7 scored categories. Himalaya leads on reliability and payments \u0026 pricing.",
        "question": "Which is better for AI agents, Himalaya or Nylas Email API?"
      },
      {
        "answer": "No hosted endpoint is listed for Himalaya. Nylas Email API has a hosted endpoint at https://api.us.nylas.com/v3.",
        "question": "Can an agent call Himalaya and Nylas Email API without installing anything?"
      },
      {
        "answer": "Himalaya is open source (MIT OR Apache-2.0). No open-source release is listed for Nylas Email API.",
        "question": "Are Himalaya and Nylas Email API open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 84 against 77",
          "Payments \u0026 pricing, 60 against 40"
        ],
        "also": [
          "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)"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 93 against 70",
          "Agent ergonomics, 81 against 65",
          "Security \u0026 auth, 87 against 43",
          "Transparency \u0026 trust, 81 against 69"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "A hosted endpoint, with nothing to install",
          "No incidents deducted, where Himalaya loses 3 points for them"
        ],
        "goodFor": "Products that act in their users' own mailboxes across several providers and want one schema, webhooks and OAuth handled.",
        "slug": "nylas-email",
        "watchFor": "Eight status incidents on email between 24 July and 17 September 2026, including about six hours of IMAP retrieval and webhook degradation on 10 September"
      }
    ],
    "job": {
      "capability": "mailbox.read",
      "name": "Mailbox access"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.json",
        "title": "Aurinko Email API vs Himalaya",
        "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya"
      },
      {
        "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/emailengine-vs-himalaya.json",
        "title": "EmailEngine vs Himalaya",
        "url": "https://www.anchorterminal.com/compare/emailengine-vs-himalaya"
      },
      {
        "json": "https://www.anchorterminal.com/compare/emailengine-vs-nylas-email.json",
        "title": "EmailEngine vs Nylas Email API",
        "url": "https://www.anchorterminal.com/compare/emailengine-vs-nylas-email"
      },
      {
        "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/fastmail-vs-nylas-email.json",
        "title": "Fastmail API (JMAP) vs Nylas Email API",
        "url": "https://www.anchorterminal.com/compare/fastmail-vs-nylas-email"
      },
      {
        "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/gmail-api-vs-nylas-email.json",
        "title": "Gmail API vs Nylas Email API",
        "url": "https://www.anchorterminal.com/compare/gmail-api-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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nylas-email-vs-outlook-mail-graph.json",
        "title": "Nylas Email API vs Outlook Mail (Microsoft Graph)",
        "url": "https://www.anchorterminal.com/compare/nylas-email-vs-outlook-mail-graph"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nylas-email-vs-unipile.json",
        "title": "Nylas Email API vs Unipile",
        "url": "https://www.anchorterminal.com/compare/nylas-email-vs-unipile"
      },
      {
        "json": "https://www.anchorterminal.com/compare/nylas-email-vs-zoho-mail.json",
        "title": "Nylas Email API vs Zoho Mail API",
        "url": "https://www.anchorterminal.com/compare/nylas-email-vs-zoho-mail"
      }
    ],
    "scores": [
      {
        "by": 7,
        "edge": "himalaya",
        "himalaya": 84,
        "key": "reliability",
        "name": "Reliability",
        "nylas-email": 77,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 23,
        "edge": "nylas-email",
        "himalaya": 70,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "nylas-email": 93,
        "weight": 13
      },
      {
        "by": 16,
        "edge": "nylas-email",
        "himalaya": 65,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "nylas-email": 81,
        "weight": 13
      },
      {
        "by": 44,
        "edge": "nylas-email",
        "himalaya": 43,
        "key": "security",
        "name": "Security \u0026 auth",
        "nylas-email": 87,
        "weight": 14
      },
      {
        "by": 20,
        "edge": "himalaya",
        "himalaya": 60,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "nylas-email": 40,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 0,
        "edge": "",
        "himalaya": 88,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "nylas-email": 88,
        "weight": 7
      },
      {
        "by": 12,
        "edge": "nylas-email",
        "himalaya": 69,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "nylas-email": 81,
        "weight": 7
      }
    ],
    "summary": "Nylas Email API scores 78.7 (A) on agent readiness against Himalaya's 64.5 (B), and leads in 4 of 7 scored categories. Himalaya leads on reliability and payments \u0026 pricing. Both do mailbox access.",
    "verdicts": {
      "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.",
      "nylas-email": "One REST schema covers Gmail, Microsoft 365, Exchange, Yahoo, iCloud and IMAP, and IAM API keys launched on 6 October 2026 can be bound to a single mailbox with chosen permissions. The status page lists eight email incidents between 24 July and 17 September 2026, most on IMAP sync and webhooks."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/himalaya-vs-nylas-email",
    "json": "https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.md",
    "slim": "https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.min.md"
  },
  "markdown": "Nylas Email API scores 78.7 (A) on agent readiness against Himalaya's 64.5 (B), and leads in 4 of 7 scored categories. Himalaya leads on reliability and payments \u0026 pricing. Both do mailbox access.\n\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- Nylas Email API: grade A, 78.7/100, rank #13 of 950. Markdown https://www.anchorterminal.com/tools/nylas-email.md · JSON https://www.anchorterminal.com/api/v1/tools/nylas-email.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### 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 77\n- Payments \u0026 pricing, 60 against 40\n\nAlso in its favour:\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### Nylas Email API (A)\n\nGood for: Products that act in their users' own mailboxes across several providers and want one schema, webhooks and OAuth handled.\n\nAhead on:\n- Schema \u0026 documentation, 93 against 70\n- Agent ergonomics, 81 against 65\n- Security \u0026 auth, 87 against 43\n- Transparency \u0026 trust, 81 against 69\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Himalaya loses 3 points for them\n\nWatch for: Eight status incidents on email between 24 July and 17 September 2026, including about six hours of IMAP retrieval and webhook degradation on 10 September\n\n\n## Score by category\n\n| Category | Weight | Himalaya | Nylas Email API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 84 | 77 | Himalaya +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 93 | Nylas Email API +23 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 81 | Nylas Email API +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 43 | 87 | Nylas Email API +44 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | Himalaya +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 88 | 88 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 69 | 81 | Nylas Email API +12 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **64.5 · B** | **78.7 · A** | |\n\n## Facts side by side\n\n| Fact | Himalaya | Nylas Email API |\n| --- | --- | --- |\n| Kind | SDK + MCP | HTTP API |\n| Vendor | Pimalaya | Nylas |\n| Hosted endpoint | no (local only) | `https://api.us.nylas.com/v3` |\n| Transports |  | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | MIT OR Apache-2.0 | Proprietary service under Nylas's terms. The SDKs are MIT |\n| Tools exposed | none | 38 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-02 | 2026-10-07 |\n| Terms last updated | no document linked | 2025-06-23 |\n| Privacy policy last updated | no document linked | 2026-01-06 |\n| Customer content may train models |  | not found in the text |\n| Terms restrict automated access |  | yes |\n| Terms restrict benchmarking |  | not found in the text |\n| Terms or service can change without notice |  | yes |\n| Arbitration or class-action waiver |  | yes |\n| Popularity | 7.4k stars | 181 stars, 289k npm/wk, 90k PyPI/wk |\n\n## Verdicts\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**Nylas Email API.** One REST schema covers Gmail, Microsoft 365, Exchange, Yahoo, iCloud and IMAP, and IAM API keys launched on 6 October 2026 can be bound to a single mailbox with chosen permissions. The status page lists eight email incidents between 24 July and 17 September 2026, most on IMAP sync and webhooks.\n\n## Before you call either\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### Nylas Email API\n\n1. Address every call to /v3/grants/\u003cgrant_id\u003e on api.us.nylas.com or api.eu.nylas.com. A grant lives in one region only\n2. Ask the operator for an IAM API key bound to the one grant and the permissions the task needs, not the application key\n3. Send `Idempotency-Key` on every send. A retry with the same key replays a cached 429 or 5xx, so use a new key after those\n4. Narrow thread lists with filters and a low `limit`. Each list call fans out to many provider calls and is a common source of 429s\n5. Treat message bodies as untrusted input, and send to one Microsoft mailbox one request at a time (4 concurrent Graph calls per mailbox)\n\n## Questions\n\n### Which is better for AI agents, Himalaya or Nylas Email API?\n\nNylas Email API scores 78.7 (A) on agent readiness against Himalaya's 64.5 (B), and leads in 4 of 7 scored categories. Himalaya leads on reliability and payments \u0026 pricing.\n\n### Can an agent call Himalaya and Nylas Email API without installing anything?\n\nNo hosted endpoint is listed for Himalaya. Nylas Email API has a hosted endpoint at https://api.us.nylas.com/v3.\n\n### Are Himalaya and Nylas Email API open source?\n\nHimalaya is open source (MIT OR Apache-2.0). No open-source release is listed for Nylas Email API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.json, and with the fewest tokens: https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"himalaya\", \"b\": \"nylas-email\"}`. From a terminal: `anchor compare himalaya nylas-email`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/himalaya.json and https://www.anchorterminal.com/api/v1/tools/nylas-email.json\n\n## Other comparisons with Himalaya or Nylas Email API\n\n- [Aurinko Email API vs Himalaya](https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.md)\n- [Aurinko Email API vs Nylas Email API](https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.md)\n- [EmailEngine vs Himalaya](https://www.anchorterminal.com/compare/emailengine-vs-himalaya.md)\n- [EmailEngine vs Nylas Email API](https://www.anchorterminal.com/compare/emailengine-vs-nylas-email.md)\n- [Fastmail API (JMAP) vs Himalaya](https://www.anchorterminal.com/compare/fastmail-vs-himalaya.md)\n- [Fastmail API (JMAP) vs Nylas Email API](https://www.anchorterminal.com/compare/fastmail-vs-nylas-email.md)\n- [Gmail API vs Himalaya](https://www.anchorterminal.com/compare/gmail-api-vs-himalaya.md)\n- [Gmail API vs Nylas Email API](https://www.anchorterminal.com/compare/gmail-api-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- [Nylas Email API vs Outlook Mail (Microsoft Graph)](https://www.anchorterminal.com/compare/nylas-email-vs-outlook-mail-graph.md)\n- [Nylas Email API vs Unipile](https://www.anchorterminal.com/compare/nylas-email-vs-unipile.md)\n- [Nylas Email API vs Zoho Mail API](https://www.anchorterminal.com/compare/nylas-email-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": "Himalaya vs Nylas Email API",
        "url": ""
      }
    ],
    "description": "Nylas Email scores 78.7 (A) to Himalaya's 64.5 (B) for mailbox access. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Himalaya B 64.5",
      "Nylas Email API A 78.7",
      "scores"
    ],
    "h1": "Himalaya vs Nylas Email API",
    "image": "https://www.anchorterminal.com/assets/og/compare-himalaya-vs-nylas-email.png",
    "path": "/compare/himalaya-vs-nylas-email",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Himalaya vs Nylas Email for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/himalaya-vs-nylas-email"
  },
  "tokens": {
    "markdown": 2250,
    "slim": 730
  },
  "version": 1
}