{ "data": { "a": { "slug": "nylas-calendar", "name": "Nylas Calendar and Scheduler API", "vendor": "Nylas", "vendorUrl": "https://www.nylas.com", "kind": "http-api", "category": "scheduling", "summary": "Unified calendar API over Google, Microsoft 365 and Outlook, Exchange (EWS) and iCloud.", "url": "https://www.anchorterminal.com/tools/nylas-calendar", "markdownUrl": "https://www.anchorterminal.com/tools/nylas-calendar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nylas-calendar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nylas-calendar.json", "dns": "nylas-calendar.grade.anchorterminal.com", "repo": "https://github.com/nylas/nylas-nodejs", "license": "MIT (SDKs)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.us.nylas.com/v3", "packages": [ { "registry": "npm", "name": "nylas" }, { "registry": "pypi", "name": "nylas" } ], "auth": "mixed", "authNotes": "Application API key or a Nylas IAM API key as a Bearer token. IAM keys (since 6 October 2026) are bound to one grant, workspace, application or organisation with roles and permissions, and always expire. Each connected user is a grant, created through Nylas hosted OAuth or your own provider credentials, and addressed as /v3/grants/\u003cgrant_id\u003e. The hosted MCP takes either key in the `Authorization` header.", "pricing": "freemium", "pricingNotes": "Free $0 with 5 email and calendar connected accounts, 5 Notetaker bot hours and 3 Agent Accounts, no credit card. Essentials $15 a month with 10 email and calendar accounts ($2.25 each after), 10 calendar-only accounts ($1.70 each after), 10 Notetaker hours then $0.80 an hour, and 10 Agent Accounts. Pro $49 a month ($43 annual) with 25 email and calendar accounts ($2.00 each after, $1.75 annual), 35 calendar-only accounts ($1.50 each after, $1.35 annual), 70 Notetaker hours then $0.70 an hour, and 50 Agent Accounts. Enterprise is custom, with a 99.99% availability SLA on annual contracts (https://www.nylas.com/pricing/).", "priceSummary": "$15 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": 38, "popularity": { "githubStars": 181, "npmWeekly": 281223, "pypiWeekly": 103888, "asOf": "2026-09-30" }, "docsUrl": "https://developer.nylas.com/docs/v3/calendar/", "llmsTxt": "https://developer.nylas.com/llms.txt", "openapi": "https://developer.nylas.com/openapi.json", "capabilities": [ "calendar.read", "calendar.write", "calendar.availability", "calendar.booking", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "llms-txt", "openapi", "webhooks", "typescript", "python", "enterprise", "eu", "closed-source" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 75.5, "grade": "BB", "agentReady": true, "rank": 51, "ranked": true, "rankOf": 1349, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 88, "payments": 40, "reliability": 72, "schema": 91, "security": 85, "transparency": 82 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars, and since 6 October IAM keys can limit an agent to one calendar grant with chosen permissions. Event writes take no idempotency key, and the MCP's confirmation step covers email sends, not event changes or deletions.", "bestFor": "Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards.", "strengths": [ "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars", "IAM API keys bind an agent to one grant with chosen permissions, always expire and are logged for 400 days", "Free plan with 5 connected accounts and no card", "MCP docs warn about hidden instructions in calendar events and tell agents to treat them as untrusted", "OpenAPI 3.1 file with 244 operations and a dated changelog with 20 entries between 15 September and 30 October 2026" ], "weaknesses": [ "Application API keys still reach every grant, and the IAM pages name no calendar permission", "No idempotency key on event writes, only on email send", "The MCP's confirmation step covers email sends only, not event creation, updates or deletion", "Delayed or missing webhooks across all providers for about five hours on 19 August 2026", "38 MCP tools load at once with no toolsets, so a calendar-only agent carries the email tools too" ], "agentNotes": [ "Address calendar calls to /v3/grants/\u003cgrant_id\u003e, one grant per connected account", "Use an IAM API key bound to the one grant the agent needs rather than the application key", "List events in the window before retrying a create, since event writes have no idempotency key", "Keep availability requests within 732 days, the cap since 10 October 2026", "On 429, use the passed-through `Retry-After` if present, otherwise back off per grant" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 75.5 } ], "editorialScores": { "ergonomics": 71, "maintenance": 88, "payments": 40, "reliability": 72, "schema": 91, "security": 85, "transparency": 67 }, "provenanceScore": 96, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.us.nylas.com/v3/grants/$NYLAS_GRANT_ID/calendars?limit=5\" \\\n -H \"Authorization: Bearer $NYLAS_API_KEY\"", "claudeCode": "claude mcp add --transport http nylas https://mcp.us.nylas.com --header \"Authorization: Bearer $NYLAS_API_KEY\"", "config": { "mcpServers": { "nylas": { "headers": { "Authorization": "Bearer ${NYLAS_API_KEY}" }, "url": "https://mcp.us.nylas.com" } } } }, "letme": { "capability": "https://letme.dev/calendar.read", "tool": "https://letme.dev/nylas-calendar" }, "sameCompany": [ "nylas-notetaker", "nylas-email" ], "area": "everyday", "unitPrices": [ { "item": "Essentials", "unit": "month", "usd": 15, "note": "10 email and calendar plus 10 calendar-only accounts" }, { "item": "Pro", "unit": "month", "usd": 49, "note": "25 email and calendar plus 35 calendar-only accounts, billed monthly" }, { "item": "Extra calendar-only account on Essentials", "unit": "account-month", "usd": 1.7 }, { "item": "Extra calendar-only account on Pro", "unit": "account-month", "usd": 1.5 }, { "item": "Extra calendar-only account on Pro annual", "unit": "account-month", "usd": 1.35 }, { "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 }, { "item": "Extra Agent Account on Pro", "unit": "account-month", "usd": 0.4 } ], "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-11-01", "notes": [ "The terms (updated 23 June 2025) name Nylas, Inc. in Palo Alto, California, under California law with arbitration.", "developer.nylas.com/.well-known/security.txt is an RFC 9116 file with security@nylas.com as contact and Policy https://www.nylas.com/security/, expiring on 1 August 2027. www.nylas.com/.well-known/security.txt returns 404.", "The status page for the v3 API is status-v3.nylas.com." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nylas-calendar.json", "live": { "slug": "nylas-calendar", "probe": { "target": "https://api.us.nylas.com/v3", "method": "get", "lastAt": "2026-11-04T21:39:37.081572903Z", "lastOk": true, "lastStatus": 404, "lastMs": 159, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 175, "p95ms24h": 248, "samples24h": 247, "samples30d": 8090, "days": [ { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 223, "ok": 223 } ] }, "vendorStatus": { "page": "https://status-v3.nylas.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:38:32.362137436Z" }, "versions": [ { "registry": "github", "name": "nylas/nylas-nodejs", "version": "v8.5.0", "released": "2026-11-04", "seenAt": "2026-11-04T20:40:39.961163038Z" }, { "registry": "npm", "name": "nylas", "version": "8.5.0", "seenAt": "2026-11-04T20:40:38.842013838Z" }, { "registry": "pypi", "name": "nylas", "version": "6.18.0", "released": "2026-09-30", "seenAt": "2026-11-04T20:40:39.626274249Z" } ], "githubStars": 180, "npmWeekly": 547955, "pypiWeekly": 122618, "securityTxt": { "url": "https://nylas.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:04.264086343Z" }, "llmsTxt": { "url": "https://developer.nylas.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:23:40.564288847Z" }, "domain": { "domain": "nylas.com", "registered": "2001-11-07", "source": "https://rdap.verisign.com/com/v1/domain/nylas.com", "checkedAt": "2026-11-01T14:23:35.373653199Z" }, "pages": [ { "url": "https://developer.nylas.com/docs/changelogs/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-04T08:18:19.35188913Z", "changedAt": "2026-10-31T06:07:27.740116772Z", "fingerprint": "bd9a2008a70b" }, { "url": "https://developer.nylas.com/docs/changelogs/2026-10-10-availability-metadata-and-provider-fixes/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-04T08:18:23.522071043Z", "changedAt": "2026-10-31T06:07:31.93033799Z", "fingerprint": "f39b8f77f7ec" }, { "url": "https://www.nylas.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:43:00.986942987Z", "changedAt": "2026-10-30T05:58:26.391023995Z", "fingerprint": "7331ddea70df" }, { "url": "https://www.nylas.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:43:02.562173764Z", "changedAt": "2026-10-30T05:58:26.881176912Z", "fingerprint": "98943bc01feb" }, { "url": "https://www.nylas.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:42:58.055948265Z", "changedAt": "2026-10-30T05:58:21.745601982Z", "fingerprint": "97e8708900a7" } ], "github": { "repo": "nylas/nylas-nodejs", "checkedAt": "2026-11-02T09:11:28.143578213Z", "stars": 181, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-21T18:59:14Z", "openIssues": 4, "openPRs": 4, "issuesOpened90d": 1, "issuesClosed90d": 0, "prsMerged90d": 4, "ci": { "branch": "main", "runs": 50, "success": 49, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-10-13T16:22:32Z" }, "replies": { "sampled": 25, "unanswered": 3, "medianDays": 10 } }, "updatedAt": "2026-11-04T21:39:37.081572903Z" } }, "answer": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in every scored category.", "b": { "slug": "youcanbookme", "name": "YouCanBookMe API", "vendor": "AI Software (Capacity) UK Ltd, trading as YouCanBookMe", "vendorUrl": "https://youcanbook.me", "kind": "http-api", "category": "scheduling", "summary": "YouCanBookMe is a booking-page service from the UK company of the same name, owned by Capacity since 2025. Its REST API manages account details, booking pages (profiles) and bookings over HTTP Basic auth, with webhooks from booking notifications.", "url": "https://www.anchorterminal.com/tools/youcanbookme", "markdownUrl": "https://www.anchorterminal.com/tools/youcanbookme.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/youcanbookme.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/youcanbookme.json", "dns": "youcanbookme.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.youcanbook.me/v1", "packages": [], "auth": "api-key", "authNotes": "HTTP Basic authentication with the account email address or account ID as the username and an account API key as the password. Only the Account Owner can generate, view, copy or delete the key, under Account Password \u0026 Security \u003e Authentication and API, and the help centre says the API key is available on the Team plan. No scopes, expiry or per-user keys are described. Administrators and Contributors must ask the owner for the key.", "pricing": "freemium", "pricingNotes": "Free plan with 1 calendar, 1 booking page and 30 bookings a month, with YouCanBookMe branding. Individual $9, Professional $13 and Teams $18 a seat a month, with 10 per cent off yearly and 20 per cent off for two years ($7.20, $10.40 and $14.40), per the help centre's pricing article. 14-day trial of every feature with no card, per the pricing page. API access is listed under the Team plan; webhooks need Professional or Teams.", "priceSummary": "$9 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, in the help centre API and webhook articles or in the API's error response (checked 2026-11-03). The API reference itself could not be read.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://ycbm.stoplight.io/", "capabilities": [ "calendar.booking", "calendar.availability", "calendar.webhooks" ], "tags": [ "hosted", "freemium", "free-tier", "free-trial", "no-card", "api-key", "webhooks", "soc2", "iso27001", "uk", "closed-source" ], "lastRelease": "2026-09-01", "graded": true, "anchor": { "graded": true, "score": 22.5, "grade": "F", "agentReady": false, "rank": 1287, "ranked": true, "rankOf": 1349, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 13, "maintenance": 28, "payments": 30, "reliability": 15, "schema": 10, "security": 24, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "A booking-page service with a Team-plan REST API over HTTP Basic auth and one account-wide key, SOC 2 Type II and ISO 27001 on its security page, and a 14-day trial without a card. Its API reference renders only by JavaScript and its status page did not resolve for us, so endpoints, limits and incidents are unverified.", "bestFor": "A booking-page product for small businesses, closest to calendly and savvycal in scheduling.", "strengths": [ "SOC 2 Type II and ISO/IEC 27001:2022 (certificate issued 20 February 2024) listed on the security page, with AES-256 at rest on AWS", "Free plan and a 14-day trial of every feature with no card", "Privacy notice (16 March 2026) states retention periods, 24 months for booking data by default, and says booking data is not used to train AI models", "Webhook notifications on six booking triggers with a JSON payload the user shapes, on Professional and Teams", "The API answers with a JSON error envelope carrying a code, message and status, and declares its version in an `x-api-version` header" ], "weaknesses": [ "The API reference at ycbm.stoplight.io could not be read without JavaScript, and the help centre's API article sat behind a Cloudflare challenge", "One account-wide API key over HTTP Basic auth, created only by the Account Owner, with no scopes or expiry documented", "API access is listed only on the Team plan ($18 a seat a month)", "No rate limits, 429 handling, idempotency keys, OpenAPI file, llms.txt or official SDK were found", "No security.txt, bug bounty or disclosure policy, and the status page at youcanbookmestatus.com did not resolve for us" ], "agentNotes": [ "Ask the Account Owner for the account ID and API key, since Administrators and Contributors cannot generate one, and send them as HTTP Basic credentials", "Read the API reference at ycbm.stoplight.io in a browser before planning calls; its endpoints and parameters were not readable to us", "Treat the key as full account access and keep it out of logs, since no scoped or read-only key is documented", "Expect a JSON error body with `code`, `message` and `status` on failures, and check for an existing booking before repeating a create, since no idempotency key is documented", "Use booking-page webhooks for booking, reschedule, cancel, reminder, follow-up and no-show events instead of polling" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 22.5 } ], "editorialScores": { "ergonomics": 13, "maintenance": 28, "payments": 30, "reliability": 15, "schema": 10, "security": 24, "transparency": 52 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -u \"$YCBM_ACCOUNT_ID:$YCBM_API_KEY\" https://api.youcanbook.me/v1/profiles" }, "letme": { "capability": "https://letme.dev/calendar.booking", "tool": "https://letme.dev/youcanbookme" }, "area": "everyday", "unitPrices": [ { "item": "Individual", "unit": "seat-month", "usd": 9, "note": "$8.10 a month yearly, $7.20 over two years, per the help centre" }, { "item": "Professional", "unit": "seat-month", "usd": 13, "note": "$11.70 a month yearly, $10.40 over two years" }, { "item": "Teams", "unit": "seat-month", "usd": 18, "note": "Per seat. $16.20 yearly, $14.40 over two years. The plan that lists API access" } ], "provenance": { "legalEntity": "AI Software (Capacity) UK Ltd", "domain": "youcanbook.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://youcanbook.me/terms", "privacy": "https://youcanbook.me/privacy", "statusPage": "https://www.youcanbookmestatus.com", "changelog": "https://youcanbook.me/product-updates", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The terms (last updated 18 March 2026) name AI Software (Capacity) UK Ltd, trading as YouCanBookMe, under English law. Clause 15.3 bars data mining, robots and similar extraction tools without written consent, and clause 7.2 bars downloading the Site's software. Recorded as a fact; the public pages were read.", "The privacy notice (16 March 2026) gives company number 7221202, AWS hosting in the United States, a DPA on request through HelloSign, and retention of 24 months for booking data and up to 7 years for support messages.", "youcanbook.me/robots.txt disallows only HubSpot preview and preference paths. support.youcanbook.me/robots.txt disallows account, search and request paths; the API article there answered a Cloudflare challenge (403), which is the host's block, not a robots rule. ycbm.capacity.com and ycbm.stoplight.io allow all.", "The status page linked from youcanbook.me/help, www.youcanbookmestatus.com, did not resolve from our reader on 3 November 2026 (DNS), with or without www, so no incident history was read.", "youcanbook.me/.well-known/security.txt returns 404. The security page gives compliance@youcanbook.me as its contact.", "RDAP for youcanbook.me (rdap.nic.me) could not be reached from our shell, so the registration date is blank.", "The product updates page at youcanbook.me/product-updates is dated by month; its newest entry is September 2026 (registered SMS numbers), which lastRelease records as the first of that month." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/youcanbookme.json", "live": { "slug": "youcanbookme", "probe": { "target": "https://api.youcanbook.me/v1", "method": "get", "lastAt": "2026-11-04T21:39:54.948803292Z", "lastOk": true, "lastStatus": 400, "lastMs": 406, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 200, "p95ms24h": 447, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://www.youcanbookmestatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:27:01.611847667Z" }, "securityTxt": { "url": "https://youcanbook.me/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:28.156243558Z" }, "updatedAt": "2026-11-04T21:39:54.948803292Z" } }, "edges": [ { "by": 81, "category": "schema", "leads": "nylas-calendar", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 file at developer.nylas.com/openapi.json with 140 paths and 244 operations on 1 November, 20 of the paths and 34 operations for calendars, events, availability and scheduling (25). llms.txt and Markdown docs (10). Guides say when to use each API, and the MCP page lists each tool with a one-line purpose and no when-not-to guidance (15). Typed parameters in the reference (12). An errors page with a JSON shape (`type`, `message`, `provider_error`, `request_id`) and a retry yes or no for each status code (14). v3 in the path and a dated changelog with 20 entries between 15 September and 30 October 2026 (15). 25+10+15+12+14+15 = 91.", "b": "The reference lives on Stoplight at ycbm.stoplight.io, which usually renders an OpenAPI file, but our reader got only the workspace shell, and no spec file was found at the usual paths; the help centre article on support.youcanbook.me sat behind a Cloudflare challenge. Scored absent (0 of 25). No llms.txt on youcanbook.me, the help centre or the Stoplight host (0). Descriptions, typed inputs and required fields unread (0 of 20, 0 of 15). The one response we saw is a JSON envelope with `code`, `errors`, `httpCode`, `message` and `status`, and the help centre gives a worked webhook payload (4 of 15). A /v1 path and `x-api-version: 1.18` and `x-api-revision` headers, with a product updates page dated by month and no API changelog (6 of 15). 0 + 0 + 0 + 0 + 4 + 6 = 10." }, "scores": { "a": 91, "b": 10 } }, { "by": 61, "category": "security", "leads": "nylas-calendar", "name": "Security \u0026 auth", "reasons": { "a": "Nylas IAM, launched 6 October 2026, issues API keys bound to one grant, workspace, application or organisation with roles and permissions. Every new IAM key expires, keys can be disabled or rotated, and the IAM guide (re-read 1 November) shows principals and credentials created and rotated through a public /v3/iam API once a first management key is made in the Dashboard. End users connect through OAuth with scopes the app picks. Application keys still reach every grant, so 1 is held back as for nylas-email, and 1 more because the IAM pages name no calendar permission, as nylas-notetaker holds back for Notetaker (28). A principal can be bound to one grant with read permissions, the agent security page shows a scheduling agent limited to reading calendars and creating events, and anything outside the binding answers 403. The MCP confirmation step covers email sends only, so creating, updating or deleting an event needs no confirmation. 3 below nylas-email's 17, which has the send confirmation (14). The MCP and agent security docs say event descriptions and locations can carry hidden instructions and tell agents to treat calendar content as untrusted (13). IAM Access Activity records allowed and denied API, authentication and MCP requests for 400 days with links to request logs, and Dashboard logs are kept 14 days. Requests made with an application key appear only in the logs (13). SOC 2 Type II, ISO 27001 and 27701, CSA STAR, an annual penetration test and a private bug bounty with security@nylas.com, per the 1 October check, and an RFC 9116 security.txt on developer.nylas.com valid to 1 August 2027. www.nylas.com still has none. nylas-email scores this 17 (17). 28+14+13+13+17 = 85.", "b": "One account-wide API key sent as the HTTP Basic password with the account ID or email, generated and deleted by the Account Owner only; no scopes, expiry or per-user keys are documented (10 of 30). No read-only mode or confirmation step found (0 of 20). The API and webhooks carry names, answers and notes written by people who book, with no injection guidance (2 of 15). No audit log or per-call visibility found (0 of 15). SOC 2 Type II and ISO/IEC 27001:2022 (certificate 20/3433, 20 February 2024) and third-party penetration tests on the security page, but no security.txt (404), bug bounty or disclosure policy (12 of 20). 10 + 0 + 2 + 0 + 12 = 24." }, "scores": { "a": 85, "b": 24 } }, { "by": 60, "category": "maintenance", "leads": "nylas-calendar", "name": "Maintenance \u0026 community", "reasons": { "a": "Changelog entries up to 30 October 2026, the last calendar-specific one on 22 October with event webhook, recurring cancellation and Microsoft availability fixes (30). 20 dated changelog entries between 15 September and 30 October (20). Public dated changelog, open SDK repositories with commits to 30 September (Python) and 13 October (Node), and support (15). Current official SDKs (15). nylas-python v6.18.0 on 30 September 2026. The Node SDK's package.json is still 8.4.0 (24 June 2026) with unreleased commits on main to 13 October (8). 30+20+15+15+8 = 88.", "b": "Read as a closed service. The newest product update is dated September 2026 (registered SMS numbers), within 90 days but not 30, taking the month's first day (20 of 30). The previous entry is November 2025, so fewer than three in 90 days (0 of 20). A help centre, a community forum at forum.youcanbook.me and one-to-one support for paid users, with a product updates page that carries no API items (8 of 15). No official SDKs found (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28." }, "scores": { "a": 88, "b": 28 } }, { "by": 58, "category": "ergonomics", "leads": "nylas-calendar", "name": "Agent ergonomics", "reasons": { "a": "38 MCP tools with no toolsets found on 1 November (5), plus 5 for `limit` and `select` field selection on the REST API (10). Page tokens and time filters on event lists (18). Typed errors with a request ID and a provider error passed through, and a retry table (18). The MCP needs a confirmation call before sending mail, but event create, update and delete need none, event writes have no idempotency key and we found no tool annotations (10). Official SDKs in Node, Python and more (15). 10+18+18+10+15 = 71.", "b": "Response sizing, field selection and pagination are in the unread reference (3 of 25, 0 of 20). The error envelope names a machine code and a message an agent can branch on (8 of 20). No idempotency key or safe-retry guidance found (0 of 20). No official SDK, and the required parameters are unread (2 of 15). 3 + 0 + 8 + 0 + 2 = 13." }, "scores": { "a": 71, "b": 13 } }, { "by": 57, "category": "reliability", "leads": "nylas-calendar", "name": "Reliability", "reasons": { "a": "Atlassian Statuspage at status-v3.nylas.com with US and EU components (20). In the 90 days from 3 August the history feed names no calendar incident. Incidents hit IMAP message reads (6 August), US message sync latency (11 August), EWS attachments (14 August), Microsoft send and read through Exchange Online (31 August to 1 September), Notetaker Teams joins (4 September), IMAP retrieval (10 September), IMAP sync (17 September) and Microsoft 365 sign-in for Sandbox applications on shared credentials (from 22 October), each limited to one provider, product or non-production surface, so partial. The exception is 19 August, delayed or missing webhooks for all providers in the US and EU from 09:11 to 14:34 PDT, mitigated by recovering the sync state of affected grants. Calendar event webhooks come from the same provider grant sync, so it counts here as one major, as for nylas-email (10). 200 requests a second per grant for calendar and 50 a second per application for grant, auth and webhook endpoints, plus the provider limits behind them, re-read on 1 November (15). 429s separate Nylas limits from provider limits and pass on the provider's Retry-After, Google's included since 22 October, and the errors page says which codes to retry with exponential backoff. Idempotency keys cover email send only, not event writes (10). The pricing page lists a 99.99 per cent availability SLA for annual Enterprise contracts, with terms in the customer agreement, which nylas-email scores 7 (7). GA (10). 20+10+15+10+7+10 = 72.", "b": "Read with the hosted lines. The help page links a status page at www.youcanbookmestatus.com, but the host did not resolve from our reader with or without www on 3 November 2026, so it is scored as not established rather than as a finding about the vendor (0). No readable history (5). No rate limit with a number in the help centre articles, the pricing page or the API's own error response; the API reference could not be read (0). No 429 or retry guidance and no idempotency key found (0). No SLA, and the terms say the service is not guaranteed to be available 100 per cent of the time (0). The API reports version 1.18 in its headers and is sold on the Team plan, so generally available (10). 0 + 5 + 0 + 0 + 0 + 10 = 15." }, "scores": { "a": 72, "b": 15 } }, { "by": 21, "category": "transparency", "leads": "nylas-calendar", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Californian law, with MIT SDKs (15). The privacy policy keeps customer data for the life of the account plus two months and lets EEA customers pick UK or US data centres, per the 1 October check and as nylas-email read it on 1 November. A sub-processor page dated 28 August 2026, with changes announced on the status page (24). v2 deprecation documented and a dated changelog, but no deprecation policy found. The 10 October changelog capped availability ranges at 732 days on the day it took effect (10). Sub-processors listed, AWS and GCP named as hosts, US and EU regions (18). 15+24+10+18 = 67.", "b": "Closed service with terms (18 March 2026) naming AI Software (Capacity) UK Ltd under English law, which bar data-mining and robot tools without consent and let the company end membership without notice for a breach (15 of 30). The privacy notice (16 March 2026) states retention periods (24 months for booking data by default, 7 years for support messages), AWS hosting in the United States, a DPA on request and no training of external AI models on booking data; the security page says no subprocessor list is published, and the two agree on AWS (22 of 30). No deprecation policy or dated notice, and clause 18.4 allows changes to the service without notice (3 of 20). Providers are named in the privacy notice (AWS, Stripe, Google Analytics, Mixpanel, Hotjar, HubSpot) with US hosting, but there is no list with locations per processor (12 of 20). 15 + 22 + 3 + 12 = 52." }, "scores": { "a": 82, "b": 61 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Nylas", "b": "AI Software (Capacity) UK Ltd, trading as YouCanBookMe", "name": "Vendor" }, { "a": "https://api.us.nylas.com/v3", "b": "https://api.youcanbook.me/v1", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT (SDKs)", "b": "none", "name": "Licence" }, { "a": "38", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2026-09-01", "name": "Last release" }, { "a": "2025-06-23", "b": "2026-03-18", "name": "Terms last updated" }, { "a": "2026-01-06", "b": "2026-03-16", "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": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "181 stars, 281k npm/wk, 104k PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "3/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in every scored category.", "question": "Which is better for AI agents, Nylas Calendar and Scheduler API or YouCanBookMe API?" }, { "answer": "Nylas Calendar and Scheduler API takes an API key or an OAuth sign-in. YouCanBookMe API needs an API key.", "question": "Do Nylas Calendar and Scheduler API and YouCanBookMe API need an API key?" }, { "answer": "Yes. Nylas Calendar and Scheduler API has a hosted endpoint at https://api.us.nylas.com/v3 and YouCanBookMe API at https://api.youcanbook.me/v1.", "question": "Can an agent call Nylas Calendar and Scheduler API and YouCanBookMe API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 72 against 15", "Schema \u0026 documentation, 91 against 10", "Agent ergonomics, 71 against 13", "Security \u0026 auth, 85 against 24", "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 88 against 28", "Transparency \u0026 trust, 82 against 61" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards.", "slug": "nylas-calendar", "watchFor": "Application API keys still reach every grant, and the IAM pages name no calendar permission" }, { "aheadOn": null, "also": null, "goodFor": "A booking-page product for small businesses, closest to calendly and savvycal in scheduling.", "slug": "youcanbookme", "watchFor": "The API reference at ycbm.stoplight.io could not be read without JavaScript, and the help centre's API article sat behind a Cloudflare challenge" } ], "history": { "nylas-calendar": [ { "causes": [ "product", "correction" ], "date": "2026-11-01", "delta": 4.4, "from": 71.1, "fromGrade": "BB", "to": 75.5, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 71, "fromGrade": "BB", "to": 71.1, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 71.3, "fromGrade": "BB", "to": 71, "toGrade": "BB" } ], "youcanbookme": null }, "job": { "capability": "calendar.booking", "name": "Calendar booking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.json", "title": "Acuity Scheduling API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/agenda-hero-vs-nylas-calendar.json", "title": "Agenda Hero vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/agenda-hero-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar.json", "title": "Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.json", "title": "Aurinko Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-nylas-calendar.json", "title": "Cal.com API v2 + MCP vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar.json", "title": "Calendly API + MCP vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar.json", "title": "Cozi Family Organizer vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar.json", "title": "Cronofy API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-nylas-calendar.json", "title": "Google Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar.json", "title": "Microsoft Graph Calendar API vs Nylas Calendar and Scheduler API", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.json", "title": "Nylas Calendar and Scheduler API vs SavvyCal API + MCP", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal" }, { "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler.json", "title": "Nylas Calendar and Scheduler API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.json", "title": "Acuity Scheduling API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme.json", "title": "Aurinko Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme.json", "title": "Cal.com API v2 + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.json", "title": "Calendly API + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/calendly-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme.json", "title": "Cronofy API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.json", "title": "SavvyCal API + MCP vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler.json", "title": "YouCanBookMe API vs Zoom Scheduler API", "url": "https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler" }, { "json": "https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.json", "title": "Apiroc Unified Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.json", "title": "Google Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme" }, { "json": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.json", "title": "Microsoft Graph Calendar API vs YouCanBookMe API", "url": "https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme" } ], "panel": null, "scores": [ { "by": 57, "edge": "nylas-calendar", "key": "reliability", "name": "Reliability", "nylas-calendar": 72, "weight": 16, "youcanbookme": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 81, "edge": "nylas-calendar", "key": "schema", "name": "Schema \u0026 documentation", "nylas-calendar": 91, "weight": 13, "youcanbookme": 10 }, { "by": 58, "edge": "nylas-calendar", "key": "ergonomics", "name": "Agent ergonomics", "nylas-calendar": 71, "weight": 13, "youcanbookme": 13 }, { "by": 61, "edge": "nylas-calendar", "key": "security", "name": "Security \u0026 auth", "nylas-calendar": 85, "weight": 14, "youcanbookme": 24 }, { "by": 10, "edge": "nylas-calendar", "key": "payments", "name": "Payments \u0026 pricing", "nylas-calendar": 40, "weight": 10, "youcanbookme": 30 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 60, "edge": "nylas-calendar", "key": "maintenance", "name": "Maintenance \u0026 community", "nylas-calendar": 88, "weight": 7, "youcanbookme": 28 }, { "by": 21, "edge": "nylas-calendar", "key": "transparency", "name": "Transparency \u0026 trust", "nylas-calendar": 82, "weight": 7, "youcanbookme": 61 } ], "summary": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in every scored category. Both do calendar booking.", "tasks": null, "tutorials": [], "verdicts": { "nylas-calendar": "One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars, and since 6 October IAM keys can limit an agent to one calendar grant with chosen permissions. Event writes take no idempotency key, and the MCP's confirmation step covers email sends, not event changes or deletions.", "youcanbookme": "A booking-page service with a Team-plan REST API over HTTP Basic auth and one account-wide key, SOC 2 Type II and ISO 27001 on its security page, and a 14-day trial without a card. Its API reference renders only by JavaScript and its status page did not resolve for us, so endpoints, limits and incidents are unverified." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme", "json": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.min.md" }, "markdown": "Nylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in every scored category. Both do calendar booking.\n\n- Nylas Calendar and Scheduler API: grade BB, 75.5/100, rank #51 of 1349. Markdown https://www.anchorterminal.com/tools/nylas-calendar.md · JSON https://www.anchorterminal.com/api/v1/tools/nylas-calendar.json\n- YouCanBookMe API: grade F, 22.5/100, rank #1287 of 1349. Markdown https://www.anchorterminal.com/tools/youcanbookme.md · JSON https://www.anchorterminal.com/api/v1/tools/youcanbookme.json\n- Best calendar and scheduling APIs for AI agents: https://www.anchorterminal.com/best/scheduling/index.md\n- All 89 scheduling comparisons: https://www.anchorterminal.com/compare/scheduling/index.md\n\n## Which one, for what\n\n### Nylas Calendar and Scheduler API (BB)\n\nGood for: Products that need read, write and availability across every major provider plus email on one grant, from a handful of users upwards.\n\nAhead on:\n- Reliability, 72 against 15\n- Schema \u0026 documentation, 91 against 10\n- Agent ergonomics, 71 against 13\n- Security \u0026 auth, 85 against 24\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 88 against 28\n- Transparency \u0026 trust, 82 against 61\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Application API keys still reach every grant, and the IAM pages name no calendar permission\n\n### YouCanBookMe API (F)\n\nGood for: A booking-page product for small businesses, closest to calendly and savvycal in scheduling.\n\nWatch for: The API reference at ycbm.stoplight.io could not be read without JavaScript, and the help centre's API article sat behind a Cloudflare challenge\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Nylas Calendar and Scheduler API +81\n\n- Nylas Calendar and Scheduler API (91): OpenAPI 3.1 file at developer.nylas.com/openapi.json with 140 paths and 244 operations on 1 November, 20 of the paths and 34 operations for calendars, events, availability and scheduling (25). llms.txt and Markdown docs (10). Guides say when to use each API, and the MCP page lists each tool with a one-line purpose and no when-not-to guidance (15). Typed parameters in the reference (12). An errors page with a JSON shape (`type`, `message`, `provider_error`, `request_id`) and a retry yes or no for each status code (14). v3 in the path and a dated changelog with 20 entries between 15 September and 30 October 2026 (15). 25+10+15+12+14+15 = 91.\n- YouCanBookMe API (10): The reference lives on Stoplight at ycbm.stoplight.io, which usually renders an OpenAPI file, but our reader got only the workspace shell, and no spec file was found at the usual paths; the help centre article on support.youcanbook.me sat behind a Cloudflare challenge. Scored absent (0 of 25). No llms.txt on youcanbook.me, the help centre or the Stoplight host (0). Descriptions, typed inputs and required fields unread (0 of 20, 0 of 15). The one response we saw is a JSON envelope with `code`, `errors`, `httpCode`, `message` and `status`, and the help centre gives a worked webhook payload (4 of 15). A /v1 path and `x-api-version: 1.18` and `x-api-revision` headers, with a product updates page dated by month and no API changelog (6 of 15). 0 + 0 + 0 + 0 + 4 + 6 = 10.\n\n### Security \u0026 auth: Nylas Calendar and Scheduler API +61\n\n- Nylas Calendar and Scheduler API (85): Nylas IAM, launched 6 October 2026, issues API keys bound to one grant, workspace, application or organisation with roles and permissions. Every new IAM key expires, keys can be disabled or rotated, and the IAM guide (re-read 1 November) shows principals and credentials created and rotated through a public /v3/iam API once a first management key is made in the Dashboard. End users connect through OAuth with scopes the app picks. Application keys still reach every grant, so 1 is held back as for nylas-email, and 1 more because the IAM pages name no calendar permission, as nylas-notetaker holds back for Notetaker (28). A principal can be bound to one grant with read permissions, the agent security page shows a scheduling agent limited to reading calendars and creating events, and anything outside the binding answers 403. The MCP confirmation step covers email sends only, so creating, updating or deleting an event needs no confirmation. 3 below nylas-email's 17, which has the send confirmation (14). The MCP and agent security docs say event descriptions and locations can carry hidden instructions and tell agents to treat calendar content as untrusted (13). IAM Access Activity records allowed and denied API, authentication and MCP requests for 400 days with links to request logs, and Dashboard logs are kept 14 days. Requests made with an application key appear only in the logs (13). SOC 2 Type II, ISO 27001 and 27701, CSA STAR, an annual penetration test and a private bug bounty with security@nylas.com, per the 1 October check, and an RFC 9116 security.txt on developer.nylas.com valid to 1 August 2027. www.nylas.com still has none. nylas-email scores this 17 (17). 28+14+13+13+17 = 85.\n- YouCanBookMe API (24): One account-wide API key sent as the HTTP Basic password with the account ID or email, generated and deleted by the Account Owner only; no scopes, expiry or per-user keys are documented (10 of 30). No read-only mode or confirmation step found (0 of 20). The API and webhooks carry names, answers and notes written by people who book, with no injection guidance (2 of 15). No audit log or per-call visibility found (0 of 15). SOC 2 Type II and ISO/IEC 27001:2022 (certificate 20/3433, 20 February 2024) and third-party penetration tests on the security page, but no security.txt (404), bug bounty or disclosure policy (12 of 20). 10 + 0 + 2 + 0 + 12 = 24.\n\n### Maintenance \u0026 community: Nylas Calendar and Scheduler API +60\n\n- Nylas Calendar and Scheduler API (88): Changelog entries up to 30 October 2026, the last calendar-specific one on 22 October with event webhook, recurring cancellation and Microsoft availability fixes (30). 20 dated changelog entries between 15 September and 30 October (20). Public dated changelog, open SDK repositories with commits to 30 September (Python) and 13 October (Node), and support (15). Current official SDKs (15). nylas-python v6.18.0 on 30 September 2026. The Node SDK's package.json is still 8.4.0 (24 June 2026) with unreleased commits on main to 13 October (8). 30+20+15+15+8 = 88.\n- YouCanBookMe API (28): Read as a closed service. The newest product update is dated September 2026 (registered SMS numbers), within 90 days but not 30, taking the month's first day (20 of 30). The previous entry is November 2025, so fewer than three in 90 days (0 of 20). A help centre, a community forum at forum.youcanbook.me and one-to-one support for paid users, with a product updates page that carries no API items (8 of 15). No official SDKs found (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28.\n\n### Agent ergonomics: Nylas Calendar and Scheduler API +58\n\n- Nylas Calendar and Scheduler API (71): 38 MCP tools with no toolsets found on 1 November (5), plus 5 for `limit` and `select` field selection on the REST API (10). Page tokens and time filters on event lists (18). Typed errors with a request ID and a provider error passed through, and a retry table (18). The MCP needs a confirmation call before sending mail, but event create, update and delete need none, event writes have no idempotency key and we found no tool annotations (10). Official SDKs in Node, Python and more (15). 10+18+18+10+15 = 71.\n- YouCanBookMe API (13): Response sizing, field selection and pagination are in the unread reference (3 of 25, 0 of 20). The error envelope names a machine code and a message an agent can branch on (8 of 20). No idempotency key or safe-retry guidance found (0 of 20). No official SDK, and the required parameters are unread (2 of 15). 3 + 0 + 8 + 0 + 2 = 13.\n\n### Reliability: Nylas Calendar and Scheduler API +57\n\n- Nylas Calendar and Scheduler API (72): Atlassian Statuspage at status-v3.nylas.com with US and EU components (20). In the 90 days from 3 August the history feed names no calendar incident. Incidents hit IMAP message reads (6 August), US message sync latency (11 August), EWS attachments (14 August), Microsoft send and read through Exchange Online (31 August to 1 September), Notetaker Teams joins (4 September), IMAP retrieval (10 September), IMAP sync (17 September) and Microsoft 365 sign-in for Sandbox applications on shared credentials (from 22 October), each limited to one provider, product or non-production surface, so partial. The exception is 19 August, delayed or missing webhooks for all providers in the US and EU from 09:11 to 14:34 PDT, mitigated by recovering the sync state of affected grants. Calendar event webhooks come from the same provider grant sync, so it counts here as one major, as for nylas-email (10). 200 requests a second per grant for calendar and 50 a second per application for grant, auth and webhook endpoints, plus the provider limits behind them, re-read on 1 November (15). 429s separate Nylas limits from provider limits and pass on the provider's Retry-After, Google's included since 22 October, and the errors page says which codes to retry with exponential backoff. Idempotency keys cover email send only, not event writes (10). The pricing page lists a 99.99 per cent availability SLA for annual Enterprise contracts, with terms in the customer agreement, which nylas-email scores 7 (7). GA (10). 20+10+15+10+7+10 = 72.\n- YouCanBookMe API (15): Read with the hosted lines. The help page links a status page at www.youcanbookmestatus.com, but the host did not resolve from our reader with or without www on 3 November 2026, so it is scored as not established rather than as a finding about the vendor (0). No readable history (5). No rate limit with a number in the help centre articles, the pricing page or the API's own error response; the API reference could not be read (0). No 429 or retry guidance and no idempotency key found (0). No SLA, and the terms say the service is not guaranteed to be available 100 per cent of the time (0). The API reports version 1.18 in its headers and is sold on the Team plan, so generally available (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.\n\n### Transparency \u0026 trust: Nylas Calendar and Scheduler API +21\n\n- Nylas Calendar and Scheduler API (82): Closed service under Californian law, with MIT SDKs (15). The privacy policy keeps customer data for the life of the account plus two months and lets EEA customers pick UK or US data centres, per the 1 October check and as nylas-email read it on 1 November. A sub-processor page dated 28 August 2026, with changes announced on the status page (24). v2 deprecation documented and a dated changelog, but no deprecation policy found. The 10 October changelog capped availability ranges at 732 days on the day it took effect (10). Sub-processors listed, AWS and GCP named as hosts, US and EU regions (18). 15+24+10+18 = 67.\n- YouCanBookMe API (61): Closed service with terms (18 March 2026) naming AI Software (Capacity) UK Ltd under English law, which bar data-mining and robot tools without consent and let the company end membership without notice for a breach (15 of 30). The privacy notice (16 March 2026) states retention periods (24 months for booking data by default, 7 years for support messages), AWS hosting in the United States, a DPA on request and no training of external AI models on booking data; the security page says no subprocessor list is published, and the two agree on AWS (22 of 30). No deprecation policy or dated notice, and clause 18.4 allows changes to the service without notice (3 of 20). Providers are named in the privacy notice (AWS, Stripe, Google Analytics, Mixpanel, Hotjar, HubSpot) with US hosting, but there is no list with locations per processor (12 of 20). 15 + 22 + 3 + 12 = 52.\n\n## Score by category\n\n| Category | Weight | Nylas Calendar and Scheduler API | YouCanBookMe API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 15 | Nylas Calendar and Scheduler API +57 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 91 | 10 | Nylas Calendar and Scheduler API +81 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 13 | Nylas Calendar and Scheduler API +58 |\n| Security \u0026 auth | 14% (17.5 this run) | 85 | 24 | Nylas Calendar and Scheduler API +61 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Nylas Calendar and Scheduler API +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 88 | 28 | Nylas Calendar and Scheduler API +60 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 82 | 61 | Nylas Calendar and Scheduler API +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75.5 · BB** | **22.5 · F** | |\n\n## Facts side by side\n\n| Fact | Nylas Calendar and Scheduler API | YouCanBookMe API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Nylas | AI Software (Capacity) UK Ltd, trading as YouCanBookMe |\n| Hosted endpoint | `https://api.us.nylas.com/v3` | `https://api.youcanbook.me/v1` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | MIT (SDKs) | none |\n| Tools exposed | 38 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-10-30 | 2026-09-01 |\n| Terms last updated | 2025-06-23 | 2026-03-18 |\n| Privacy policy last updated | 2026-01-06 | 2026-03-16 |\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 | not found in the text | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 181 stars, 281k npm/wk, 104k PyPI/wk | none |\n| Agent reviews | 3/5 (2) | none |\n\n## How the scores have moved\n\n### Nylas Calendar and Scheduler API\n\n- +4.4 on 1 November 2026: product, correction\n- +0.1 on 27 October 2026: checklist\n- -0.3 on 8 October 2026: checklist\n\n### YouCanBookMe API\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Nylas Calendar and Scheduler API.** One schema across Google, Microsoft 365, Exchange EWS, iCloud and virtual calendars, and since 6 October IAM keys can limit an agent to one calendar grant with chosen permissions. Event writes take no idempotency key, and the MCP's confirmation step covers email sends, not event changes or deletions.\n\n**YouCanBookMe API.** A booking-page service with a Team-plan REST API over HTTP Basic auth and one account-wide key, SOC 2 Type II and ISO 27001 on its security page, and a 14-day trial without a card. Its API reference renders only by JavaScript and its status page did not resolve for us, so endpoints, limits and incidents are unverified.\n\n## Before you call either\n\n### Nylas Calendar and Scheduler API\n\n1. Address calendar calls to /v3/grants/\u003cgrant_id\u003e, one grant per connected account\n2. Use an IAM API key bound to the one grant the agent needs rather than the application key\n3. List events in the window before retrying a create, since event writes have no idempotency key\n4. Keep availability requests within 732 days, the cap since 10 October 2026\n5. On 429, use the passed-through `Retry-After` if present, otherwise back off per grant\n\n### YouCanBookMe API\n\n1. Ask the Account Owner for the account ID and API key, since Administrators and Contributors cannot generate one, and send them as HTTP Basic credentials\n2. Read the API reference at ycbm.stoplight.io in a browser before planning calls; its endpoints and parameters were not readable to us\n3. Treat the key as full account access and keep it out of logs, since no scoped or read-only key is documented\n4. Expect a JSON error body with `code`, `message` and `status` on failures, and check for an existing booking before repeating a create, since no idempotency key is documented\n5. Use booking-page webhooks for booking, reschedule, cancel, reminder, follow-up and no-show events instead of polling\n\n## Questions\n\n### Which is better for AI agents, Nylas Calendar and Scheduler API or YouCanBookMe API?\n\nNylas Calendar and Scheduler API scores 75.5 (BB) on agent readiness against YouCanBookMe API's 22.5 (F), and leads in every scored category.\n\n### Do Nylas Calendar and Scheduler API and YouCanBookMe API need an API key?\n\nNylas Calendar and Scheduler API takes an API key or an OAuth sign-in. YouCanBookMe API needs an API key.\n\n### Can an agent call Nylas Calendar and Scheduler API and YouCanBookMe API without installing anything?\n\nYes. Nylas Calendar and Scheduler API has a hosted endpoint at https://api.us.nylas.com/v3 and YouCanBookMe API at https://api.youcanbook.me/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nylas-calendar\", \"b\": \"youcanbookme\"}`. From a terminal: `anchor compare nylas-calendar youcanbookme`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nylas-calendar.json and https://www.anchorterminal.com/api/v1/tools/youcanbookme.json\n\n## Other comparisons with Nylas Calendar and Scheduler API or YouCanBookMe API\n\n- [Acuity Scheduling API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-nylas-calendar.md)\n- [Agenda Hero vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/agenda-hero-vs-nylas-calendar.md)\n- [Apiroc Unified Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/apiroc-vs-nylas-calendar.md)\n- [Aurinko Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-nylas-calendar.md)\n- [Cal.com API v2 + MCP vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cal-com-vs-nylas-calendar.md)\n- [Calendly API + MCP vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/calendly-vs-nylas-calendar.md)\n- [Cozi Family Organizer vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cozi-vs-nylas-calendar.md)\n- [Cronofy API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/cronofy-vs-nylas-calendar.md)\n- [Google Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/google-calendar-api-vs-nylas-calendar.md)\n- [Microsoft Graph Calendar API vs Nylas Calendar and Scheduler API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-nylas-calendar.md)\n- [Nylas Calendar and Scheduler API vs SavvyCal API + MCP](https://www.anchorterminal.com/compare/nylas-calendar-vs-savvycal.md)\n- [Nylas Calendar and Scheduler API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/nylas-calendar-vs-zoom-scheduler.md)\n- [Acuity Scheduling API vs YouCanBookMe API](https://www.anchorterminal.com/compare/acuity-scheduling-vs-youcanbookme.md)\n- [Aurinko Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/aurinko-calendar-vs-youcanbookme.md)\n- [Cal.com API v2 + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/cal-com-vs-youcanbookme.md)\n- [Calendly API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/calendly-vs-youcanbookme.md)\n- [Cronofy API vs YouCanBookMe API](https://www.anchorterminal.com/compare/cronofy-vs-youcanbookme.md)\n- [SavvyCal API + MCP vs YouCanBookMe API](https://www.anchorterminal.com/compare/savvycal-vs-youcanbookme.md)\n- [YouCanBookMe API vs Zoom Scheduler API](https://www.anchorterminal.com/compare/youcanbookme-vs-zoom-scheduler.md)\n- [Apiroc Unified Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/apiroc-vs-youcanbookme.md)\n- [Google Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/google-calendar-api-vs-youcanbookme.md)\n- [Microsoft Graph Calendar API vs YouCanBookMe API](https://www.anchorterminal.com/compare/microsoft-graph-calendar-vs-youcanbookme.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Nylas Calendar and Scheduler API vs YouCanBookMe API", "url": "" } ], "description": "Nylas Calendar and Scheduler scores 75.5 (BB) to YouCanBookMe's 22.5 (F) for calendar booking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Nylas Calendar and Scheduler API BB 75.5", "YouCanBookMe API F 22.5", "scores" ], "h1": "Nylas Calendar and Scheduler API vs YouCanBookMe API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/nylas-calendar-vs-youcanbookme", "published": "2026-10-01", "section": "tools", "title": "Nylas Calendar and Scheduler vs YouCanBookMe for AI agents (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/nylas-calendar-vs-youcanbookme" }, "tokens": { "markdown": 5250, "slim": 3230 }, "version": 1 }