{ "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": "Nylas Email API scores 78.7 (A) on agent readiness against Aurinko Email API's 44.2 (E), and leads in 6 of 7 scored categories.", "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": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Yoxel, Inc.", "b": "Nylas", "name": "Vendor" }, { "a": "https://api.aurinko.io", "b": "https://api.us.nylas.com/v3", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Yoxel's Terms of Services Agreement", "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": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-07", "name": "Last release" }, { "a": "2022-08-11", "b": "2025-06-23", "name": "Terms last updated" }, { "a": "2022-08-11", "b": "2026-01-06", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "181 stars, 289k npm/wk, 90k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Nylas Email API scores 78.7 (A) on agent readiness against Aurinko Email API's 44.2 (E), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, Aurinko Email API or Nylas Email API?" }, { "answer": "Aurinko Email API uses an OAuth sign-in. Nylas Email API takes an API key or an OAuth sign-in.", "question": "Do Aurinko Email API and Nylas Email API need an API key?" }, { "answer": "Yes. Aurinko Email API has a hosted endpoint at https://api.aurinko.io and Nylas Email API at https://api.us.nylas.com/v3.", "question": "Can an agent call Aurinko Email API and Nylas Email API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "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, 77 against 40", "Schema \u0026 documentation, 93 against 67", "Agent ergonomics, 81 against 49", "Security \u0026 auth, 87 against 42", "Maintenance \u0026 community, 88 against 13", "Transparency \u0026 trust, 81 against 44" ], "also": [ "Agent-ready, a grade of BB or better", "Free to start without a card" ], "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-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-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-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-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-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-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-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/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": [ { "aurinko-email": 40, "by": 37, "edge": "nylas-email", "key": "reliability", "name": "Reliability", "nylas-email": 77, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "aurinko-email": 67, "by": 26, "edge": "nylas-email", "key": "schema", "name": "Schema \u0026 documentation", "nylas-email": 93, "weight": 13 }, { "aurinko-email": 49, "by": 32, "edge": "nylas-email", "key": "ergonomics", "name": "Agent ergonomics", "nylas-email": 81, "weight": 13 }, { "aurinko-email": 42, "by": 45, "edge": "nylas-email", "key": "security", "name": "Security \u0026 auth", "nylas-email": 87, "weight": 14 }, { "aurinko-email": 40, "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "nylas-email": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "aurinko-email": 13, "by": 75, "edge": "nylas-email", "key": "maintenance", "name": "Maintenance \u0026 community", "nylas-email": 88, "weight": 7 }, { "aurinko-email": 44, "by": 37, "edge": "nylas-email", "key": "transparency", "name": "Transparency \u0026 trust", "nylas-email": 81, "weight": 7 } ], "summary": "Nylas Email API scores 78.7 (A) on agent readiness against Aurinko Email API's 44.2 (E), and leads in 6 of 7 scored categories. 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.", "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/aurinko-email-vs-nylas-email", "json": "https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.md", "slim": "https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.min.md" }, "markdown": "Nylas Email API scores 78.7 (A) on agent readiness against Aurinko Email API's 44.2 (E), and leads in 6 of 7 scored categories. 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- 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### 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\nWatch for: No status page, incident history or SLA found, and the terms supply the service as is\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- Reliability, 77 against 40\n- Schema \u0026 documentation, 93 against 67\n- Agent ergonomics, 81 against 49\n- Security \u0026 auth, 87 against 42\n- Maintenance \u0026 community, 88 against 13\n- Transparency \u0026 trust, 81 against 44\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\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 | Aurinko Email API | Nylas Email API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 77 | Nylas Email API +37 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 67 | 93 | Nylas Email API +26 |\n| Agent ergonomics | 13% (16.2 this run) | 49 | 81 | Nylas Email API +32 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 87 | Nylas Email API +45 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 13 | 88 | Nylas Email API +75 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 44 | 81 | Nylas Email API +37 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **44.2 · E** | **78.7 · A** | |\n\n## Facts side by side\n\n| Fact | Aurinko Email API | Nylas Email API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Yoxel, Inc. | Nylas |\n| Hosted endpoint | `https://api.aurinko.io` | `https://api.us.nylas.com/v3` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under Yoxel's Terms of Services Agreement | 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 | yes | yes |\n| Last release | none | 2026-10-07 |\n| Terms last updated | 2022-08-11 | 2025-06-23 |\n| Privacy policy last updated | 2022-08-11 | 2026-01-06 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | yes |\n| Popularity | none | 181 stars, 289k npm/wk, 90k PyPI/wk |\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**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### 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### 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, Aurinko Email API or Nylas Email API?\n\nNylas Email API scores 78.7 (A) on agent readiness against Aurinko Email API's 44.2 (E), and leads in 6 of 7 scored categories.\n\n### Do Aurinko Email API and Nylas Email API need an API key?\n\nAurinko Email API uses an OAuth sign-in. Nylas Email API takes an API key or an OAuth sign-in.\n\n### Can an agent call Aurinko Email API and Nylas Email API without installing anything?\n\nYes. Aurinko Email API has a hosted endpoint at https://api.aurinko.io and Nylas Email API at https://api.us.nylas.com/v3.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.json, and with the fewest tokens: https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"aurinko-email\", \"b\": \"nylas-email\"}`. From a terminal: `anchor compare aurinko-email nylas-email`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/aurinko-email.json and https://www.anchorterminal.com/api/v1/tools/nylas-email.json\n\n## Other comparisons with Aurinko Email API or Nylas Email API\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 Himalaya](https://www.anchorterminal.com/compare/aurinko-email-vs-himalaya.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 Nylas Email API](https://www.anchorterminal.com/compare/emailengine-vs-nylas-email.md)\n- [Fastmail API (JMAP) vs Nylas Email API](https://www.anchorterminal.com/compare/fastmail-vs-nylas-email.md)\n- [Gmail API vs Nylas Email API](https://www.anchorterminal.com/compare/gmail-api-vs-nylas-email.md)\n- [Himalaya vs Nylas Email API](https://www.anchorterminal.com/compare/himalaya-vs-nylas-email.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": "Aurinko Email API vs Nylas Email API", "url": "" } ], "description": "Nylas Email scores 78.7 (A) 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", "Nylas Email API A 78.7", "scores" ], "h1": "Aurinko Email API vs Nylas Email API", "image": "https://www.anchorterminal.com/assets/og/compare-aurinko-email-vs-nylas-email.png", "path": "/compare/aurinko-email-vs-nylas-email", "published": "2026-10-01", "section": "tools", "title": "Aurinko Email vs Nylas Email for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/aurinko-email-vs-nylas-email" }, "tokens": { "markdown": 2300, "slim": 680 }, "version": 1 }