Calendly vs SavvyCal

Agent ops

1. ai-native userMy agent can check availability, book, reschedule, and cancel meetings end to end through the API or MCP — no dashboard needed

   weight 3 · round to Calendly
   Calendly~partialprobed6/10

   Calendly has an official MCP server and REST API documented explicitly for AI agents to check availability and book meetings end-to-end (calendly-docs-5,6,24,25,34), and webhooks report on cancellations/reschedules. However, the MCP supported-tools list only shows event-type creation as an example, and there's no explicit documentation confirming an agent can directly reschedule or cancel an existing booking via the API/MCP (only that webhooks notify when a human does so). Missing for 10: explicit MCP/API tool for canceling or rescheduling an existing scheduled event, and independent/hands-on confirmation of full booking-to-cancellation agent workflow.

   • [claimed-docs] “It translates natural-language commands (e.g., "Book a 30-minute meeting with Sam next Tuesday") into structured Calendly API calls with no …”
   • [claimed-docs] “Enable AI assistants or agents in your product to **book meetings end‑to‑end** via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “Calendly users can retrieve information about availability for a specific event type”
   • [claimed-docs] “Enable AI assistants or agents in your product to book meetings end‑to‑end via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “Calendly MCP uses Dynamic Client Registration (DCR), which means **you do not need to pre-register an OAuth application**”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [probe] “official MCP server documented at https://developer.calendly.com/docs/mcp/calendly-mcp-server”

   proof ↗⚑ flag

   SavvyCal~partialprobed3/10

   SavvyCal has a documented REST API with OAuth/PAT auth and a named 'Meetings API' (savvycal-docs-5,45,50,53,54,61), suggesting programmatic meeting management exists, but there is no evidence of specific endpoints for checking availability, booking, rescheduling, or canceling meetings, and no MCP server is mentioned anywhere. Probes confirm no discoverable OpenAPI spec or llms.txt, undermining agent-readiness. missing for 10: explicit API endpoints/docs for availability check, book, reschedule, cancel; any MCP server or agent-specific integration; independent confirmation of end-to-end API scheduling flow.

   • [claimed-docs] “OAuth 2.0: OAuth2 ... HTTP: Bearer Auth ... Personal access token authentication”
   • [claimed-docs] “Personal access token authentication”
   • [claimed-docs] “OAuth 2.0 authorization code flow ... Personal access token authentication”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... Personal access token authentication ... Bearer format: pt_secret_XXXXXXXXX”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

2. ai-native userAgents can use my scheduling account as a tool — an MCP server or tool-calling surface exposes availability, bookings, and event types

   weight 2 · round to Calendly
   Calendly✓fullprobed9/10

   Calendly ships a first-party MCP server (with DCR OAuth, no pre-registration needed) that exposes tools like event_types-create_event_type and translates natural-language commands into structured API calls, alongside a dedicated Scheduling API for AI agents to book meetings end-to-end and availability endpoints. Missing for 10: independent/hands-on verification of the MCP server's real-world reliability and a fuller listing of all exposed tools beyond the few named.

   • [claimed-docs] “Bring scheduling actions into your AI apps through natural conversation, powered by Calendly MCP.”
   • [claimed-docs] “It translates natural-language commands (e.g., "Book a 30-minute meeting with Sam next Tuesday") into structured Calendly API calls with no …”
   • [claimed-docs] “Enable AI assistants or agents in your product to **book meetings end‑to‑end** via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “Calendly MCP uses Dynamic Client Registration (DCR), which means **you do not need to pre-register an OAuth application**”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type | `POST /event_types`”
   • [probe] “official MCP server documented at https://developer.calendly.com/docs/mcp/calendly-mcp-server”
   • [claimed-docs] “Calendly users can retrieve information about availability for a specific event type”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal offers a REST API, webhooks, and OAuth/PAT auth, but there is no evidence of an MCP server, tool-calling schema, or agent-facing surface; probes for llms.txt and OpenAPI spec both 404, indicating no discoverable machine/agent tool interface.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Calendly
   Calendly✓fullprobed9/10

   Direct probe evidence confirms a live llms.txt at developer.calendly.com/llms.txt with explicit instructions for AI agents, plus markdown-appendable docs pages (.md suffix) confirmed live, all documented and pointing to further agent-oriented docs like the MCP server guide. Missing for 10: independent third-party confirmation that agents actually consume this llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.calendly.com/llms.txt # Calendly | Developer Documentation ## Instructions for AI Agents - F…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.calendly.com/docs/getting-started/overview.md > Calendly developer docs. For page Markdown, app…”
   • [claimed-docs] “Bring scheduling actions into your AI apps through natural conversation, powered by Calendly MCP.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   A direct probe for llms.txt returned a 404, and no evidence indicates any agent-oriented documentation or AI-consumable docs format exists.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Calendly
   Calendly~partialclaimed6/10

   Calendly exposes a REST API with personal access tokens for internal/automated integrations, webhooks for event-driven automation, and an MCP server for programmatic scheduling—all of which can be scripted headlessly outside the UI. However, there is no explicit documentation of running Calendly in a CI pipeline, a CLI tool, or automated test/deploy workflows—automation is inferred from general API/PAT/webhook support rather than CI-specific guidance. Missing for 10: explicit CI/pipeline integration examples, a dedicated CLI or headless mode, and independent confirmation of automated/CI usage.

   • [claimed-docs] “If you're integrating an **internal application** that only your team will use, authenticate with **personal access tokens**.”
   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Enable AI assistants or agents in your product to **book meetings end‑to‑end** via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “Enable AI assistants or agents in your product to book meetings end‑to‑end via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “payloads will be sent in real time to your server endpoint when events are scheduled or canceled by either the host or the invitee”
   • [claimed-docs] “If you need to securely share data from your or your company's Calendly account with an internal or private application”

   proof ↗⚑ flag

   SavvyCal~partialclaimed4/10

   SavvyCal exposes a REST API with OAuth/personal-access-token auth and webhooks (savvycal-docs-1, savvycal-docs-5, savvycal-docs-45) which allows scripted, non-UI automation of scheduling tasks, giving a partial headless-usage path. However there is no CLI, no documented CI/automation runner, and no explicit guidance for unattended CI execution. Missing for 10: a CLI or headless mode, CI-specific documentation/examples, and evidence of unattended/automated execution outside interactive OAuth flows.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... HTTP: Bearer Auth ... Personal access token authentication”
   • [claimed-docs] “Personal access token authentication”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Calendly
   Calendly✓fullprobed8/10

   Calendly documents an official MCP server (calendly-docs-2, calendly-docs-5, calendly-docs-34, calendly-probe-3) that supports natural-language commands translated into API calls, uses OAuth Dynamic Client Registration for easy setup, and exposes supported tools like event_types-create_event_type. This is first-party documentation of a genuine MCP server, not just API/webhook integration. Missing for 10: independent/hands-on community corroboration of the MCP server actually working in practice, and more detail on the full breadth of supported tools.

   • [claimed-docs] “Bring scheduling actions into your AI apps through natural conversation, powered by Calendly MCP.”
   • [claimed-docs] “It translates natural-language commands (e.g., "Book a 30-minute meeting with Sam next Tuesday") into structured Calendly API calls with no …”
   • [claimed-docs] “Calendly MCP uses Dynamic Client Registration (DCR), which means **you do not need to pre-register an OAuth application**”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type | `POST /event_types`”
   • [probe] “official MCP server documented at https://developer.calendly.com/docs/mcp/calendly-mcp-server”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal is a scheduling SaaS, so publishing an official MCP server is a fair, applicable question for its ecosystem, but there is no mention of MCP anywhere in the evidence—only REST API, webhooks, and JS embed integrations are documented. missing for 10: any mention of an MCP server, agent integration, or MCP protocol support.

   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Calendly—none0/10

   Evidence shows Calendly's developer platform (REST API v2, MCP server, webhooks, embeds) but no mention anywhere of an official CLI tool for AI-native or any workflow.

   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Embed API: Our simpler, easy-to-use API that lets you add a Calendly landing or booking page to your website.”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [probe] “official MCP server documented at https://developer.calendly.com/docs/mcp/calendly-mcp-server”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal offers a REST API, webhooks, and JS embed library, but there is no mention anywhere of an official CLI tool for AI-native workflows.

   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Calendly
   Calendly✓fullprobed9/10

   Calendly publishes a documented REST API v2, OAuth/PAT authentication, webhooks, embed API, and an MCP server enabling AI agents to drive scheduling via natural language, all with first-party docs and a probed-live docs endpoint. Missing for 10: independent third-party developer hands-on corroboration of API robustness beyond vendor docs.

   • [claimed-docs] “Programmatically book meetings and read and write Scheduling, Contacts, and Notetaker data.”
   • [claimed-docs] “If you're integrating an **internal application** that only your team will use, authenticate with **personal access tokens**.”
   • [claimed-docs] “If you're integrating a **public application** that many Calendly users will use, authenticate with **OAuth**.”
   • [claimed-docs] “It translates natural-language commands (e.g., "Book a 30-minute meeting with Sam next Tuesday") into structured Calendly API calls with no …”
   • [claimed-docs] “Enable AI assistants or agents in your product to **book meetings end‑to‑end** via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Embed API: Our simpler, easy-to-use API that lets you add a Calendly landing or booking page to your website.”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [claimed-docs] “Calendly MCP uses Dynamic Client Registration (DCR), which means **you do not need to pre-register an OAuth application**”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.calendly.com/llms.txt # Calendly | Developer Documentation ## Instructions for AI Agents - F…”
   • [probe] “official MCP server documented at https://developer.calendly.com/docs/mcp/calendly-mcp-server”

   proof ↗⚑ flag

   SavvyCal✓fullprobed7/10

   SavvyCal documents a public REST API using JSON, OAuth2 and personal access tokens, plus webhooks with HMAC signing and a JS embed library, giving programmatic/agentic control over scheduling. Missing for 10: a discoverable machine-readable OpenAPI spec or llms.txt (probes returned 404) and independent/hands-on corroboration of API completeness.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... HTTP: Bearer Auth ... Personal access token authentication”
   • [claimed-docs] “Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... Personal access token authentication ... Bearer format: pt_secret_XXXXXXXXX”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Calendly—none0/10

   Calendly's docs describe only two broad credential options — personal access tokens (full account access) for internal apps, or OAuth 2.1 for public apps/MCP with dynamic client registration — but no evidence of scopes, granular permission sets, or least-privilege token issuance for agents. No documentation shows an AI-native user can restrict an agent's API/MCP credential to specific resources or actions.

   • [claimed-docs] “If you're integrating an **internal application** that only your team will use, authenticate with **personal access tokens**.”
   • [claimed-docs] “If you're integrating a **public application** that many Calendly users will use, authenticate with **OAuth**.”
   • [claimed-docs] “If you need to securely share data from your or your company's Calendly account with an internal or private application”
   • [claimed-docs] “If you need to provide a way for Calendly members to securely share their Calendly account data with a public application you've built, then…”
   • [claimed-docs] “Calendly MCP uses Dynamic Client Registration (DCR), which means **you do not need to pre-register an OAuth application**”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal's docs show OAuth2 and personal access token authentication for its API, but there is no evidence of scope definitions, granular permissions, or least-privilege credential issuance tailored for an agent use case.

   • [claimed-docs] “OAuth 2.0: OAuth2 ... HTTP: Bearer Auth ... Personal access token authentication”
   • [claimed-docs] “OAuth 2.0 authorization code flow ... Personal access token authentication”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... Personal access token authentication ... Bearer format: pt_secret_XXXXXXXXX”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Calendly~partialprobed4/10

   Calendly's developer docs show a well-documented REST API v2, webhook API, embed API, and an official MCP server for AI agents, but the evidence never mentions any officially maintained client-library SDKs (e.g., language-specific packages) — only raw REST/JSON API guidance and MCP tool references. missing for 10: official SDK packages (Python/Node/etc.), SDK-specific documentation or quickstarts, independent developer confirmation of SDK usage.

   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Embed API: Our simpler, easy-to-use API that lets you add a Calendly landing or booking page to your website.”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [claimed-docs] “If you're integrating an **internal application** that only your team will use, authenticate with **personal access tokens**.”
   • [claimed-docs] “If you're integrating a **public application** that many Calendly users will use, authenticate with **OAuth**.”
   • [claimed-docs] “Calendly MCP uses Dynamic Client Registration (DCR), which means **you do not need to pre-register an OAuth application**”
   • [probe] “official MCP server documented at https://developer.calendly.com/docs/mcp/calendly-mcp-server”

   proof ↗⚑ flag

   SavvyCal~partialprobed4/10

   SavvyCal offers a documented REST API with OAuth/PAT auth, webhooks, and a JavaScript embed library, giving developers programmatic access, but there is no evidence of official language-specific SDKs (e.g., Python, Node, Ruby) beyond the JS embed script, and probes show no OpenAPI spec or llms.txt available for AI tooling. Missing for 10: dedicated official SDK libraries in multiple languages, published OpenAPI/swagger spec, and AI-discoverable docs (llms.txt) that would support agentic building.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “Our JavaScript library allows you to embed your scheduling links on your website (both inline and as a popover).”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Calendly✓fullclaimed8/10

   Calendly documents a full Webhook API with real-time payloads for scheduled/canceled events and signature verification for authenticity, directly enabling event subscription for AI-native/agentic workflows. missing for 10: independent/hands-on developer corroboration of webhook reliability and no explicit example of an AI agent consuming these webhooks end-to-end.

   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “payloads will be sent in real time to your server endpoint when events are scheduled or canceled by either the host or the invitee”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [claimed-docs] “Gain confidence in the authenticity of your webhooks when you use a **webhook signing key**, a unique secret key shared between your applica…”

   proof ↗⚑ flag

   SavvyCal✓fullprobed8/10

   SavvyCal has documented webhook support with HTTP POST notifications on account changes, HMAC-SHA256 signature verification, and setup instructions via Settings > Integrations, enabling event-driven subscription for automation/agent use cases. Missing for 10: no independent/hands-on corroboration or public OpenAPI/webhook schema (openapi probe returned 404s), and no explicit list of subscribable event types.

   • [claimed-docs] “Webhooks allow you to listen for changes in a SavvyCal account and get notified via HTTP POST requests.”
   • [claimed-docs] “SavvyCal signs the request body with a SHA-256 HMAC signature. The signature is included in the x-savvycal-signature header.”
   • [claimed-docs] “SavvyCal signs the request body with a SHA-256 HMAC signature.”
   • [claimed-docs] “Navigate to Settings > Integrations and click the + icon in the Webhooks”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Calendly
   Calendly~partialclaimed5/10

   Calendly's Notetaker/Callie feature provides AI-generated meeting recaps and action items ('Get meeting recaps and action items, plus an AI assistant to help with the work around meetings'; 'Finish the day knowing every meeting was captured, next steps were tracked'), which counts as AI-derived insight from in-product data. However, this is narrow (limited to meeting content) with no evidence of broader AI-generated scheduling insights, pattern analysis, or proactive suggestions across a user's overall Calendly data. Missing for 10: analytics-driven AI insights (e.g., scheduling pattern trends, optimization suggestions), independent/hands-on validation of the recap quality, and any AI insight surfaced outside meeting recaps.

   • [claimed-docs] “Get meeting recaps and action items, plus an AI assistant to help with the work around meetings.”
   • [claimed-docs] “Recordings & transcripts * Shareable meeting recaps * Joins Zoom, Google Meet, Microsoft Teams”
   • [claimed-docs] “Add Callie to any email thread to coordinate scheduling on your behalf without switching tools or sacrificing control.”
   • [claimed-docs] “Finish the day knowing every meeting was captured, next steps were tracked, and follow-ups were handled.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   No evidence of AI-generated insights, analytics, or suggestions surfaced within SavvyCal; the product is a scheduling tool with API/webhook/workflow automation features but nothing about AI-derived insights from user data.

   ⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to SavvyCal
   Calendly~partialclaimed6/10

   Calendly supports background automations via Workflows (automated pre/post-meeting emails and texts, reminders, reschedule requests) and webhook subscriptions that fire in real time on scheduling events, plus routing forms with automated lead-matching logic — all of which run autonomously once configured. However, evidence doesn't show these automation features (Workflows, routing) being programmatically creatable/managed via the API or MCP server, which only documents event-type creation and booking tools, so it's unclear an AI-native user can fully set up such background automations end-to-end via agentic tooling. Missing for 10: MCP/API support for creating or managing Workflows/routing rules autonomously, and independent confirmation that AI agents can configure these automations without manual UI steps.

   • [claimed-docs] “Use Workflows to automate pre- and post-meeting emails and texts to invitees, hosts, and teammates.”
   • [claimed-docs] “Schedule a reminder email in a single click, so recipients who haven't booked yet don't slip through the cracks.”
   • [claimed-docs] “Send a reschedule request when your plans change and let recipients choose a new time.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “Create a routing form that uses basic routing logic (fixed answer responses) to screen and qualify people before they book with you.”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type | `POST /event_types`”
   • [claimed-docs] “Enable AI assistants or agents in your product to book meetings end‑to‑end via Calendly's Scheduling API endpoint.”

   proof ↗⚑ flag

   SavvyCal✓fullclaimed7/10

   SavvyCal's Workflows feature lets users attach multi-action automations to scheduling links that trigger automatically on meeting lifecycle events (booked, canceled, reminders) without manual intervention, and further extend via Zapier for CRM/task automations — this matches autonomous background automation. Missing for 10: independent/hands-on verification of workflow reliability, evidence of conditional/branching logic or scheduled (non-event-triggered) automations, and any AI-specific automation capability.

   • [claimed-docs] “It’s never been easier to send customized meeting lifecycle messages and automate manual tasks with SavvyCal workflows.”
   • [claimed-docs] “Attach workflows to one or more links to save yourself from repetitive work.”
   • [claimed-docs] “Trigger no-code automations with Zapier ... Sync with your CRM, send yourself reminders, create project management to-do’s…the sky’s the lim…”
   • [claimed-docs] “Keep your automations neatly organized with powerful multi-action workflows.”
   • [claimed-docs] “Create or update CRM records, send yourself reminders, or create to-do’s in your project management software.”
   • [claimed-docs] “Customize the timing and content of your reminders to increase attendance. Compose from scratch or pick one of our handy templates.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Calendly
   Calendly~partialclaimed6/10

   Calendly ships a built-in AI assistant called 'Callie' that can be added to email threads to coordinate scheduling, plus AI-generated meeting recaps/action items, matching the story's core ask of delegating tasks to an in-product AI assistant. However, evidence is limited to a few marketing/pricing blurbs with no detailed docs, hands-on walkthrough, or independent corroboration of what tasks it can actually handle end-to-end. Missing for 10: detailed documentation of Callie's task scope/limits, independent or community verification of its real-world behavior, and clarity on how it differs from the separate MCP/agent-facing API.

   • [claimed-docs] “An AI assistant that schedules over email”
   • [claimed-docs] “Add Callie to any email thread to coordinate scheduling on your behalf without switching tools or sacrificing control.”
   • [claimed-docs] “Get meeting recaps and action items, plus an AI assistant to help with the work around meetings.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   The only remotely related item, 'Delegate to an assistant' (savvycal-docs-59), refers to giving a human executive assistant account access on a pricing page, not a built-in AI assistant. No evidence anywhere in the pack of an AI assistant feature users can delegate tasks to within SavvyCal.

   • [claimed-docs] “Delegate to an assistant”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Calendly
   Calendly✓fullprobed8/10

   Calendly ships an official MCP server that explicitly translates natural-language commands (e.g., 'Book a 30-minute meeting with Sam next Tuesday') into structured API calls, plus a Callie AI assistant that coordinates scheduling via email conversation, both first-party documented capabilities. Missing for 10: independent/hands-on validation that the MCP server or Callie reliably handles varied natural-language commands in practice, beyond vendor docs.

   • [claimed-docs] “It translates natural-language commands (e.g., "Book a 30-minute meeting with Sam next Tuesday") into structured Calendly API calls with no …”
   • [claimed-docs] “translates natural-language commands (e.g., "Book a 30-minute meeting with Sam next Tuesday") into structured Calendly API calls”
   • [claimed-docs] “Bring scheduling actions into your AI apps through natural conversation, powered by Calendly MCP.”
   • [claimed-docs] “Add Callie to any email thread to coordinate scheduling on your behalf without switching tools or sacrificing control.”
   • [claimed-docs] “Calendly MCP uses Dynamic Client Registration (DCR), which means **you do not need to pre-register an OAuth application**”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [probe] “official MCP server documented at https://developer.calendly.com/docs/mcp/calendly-mcp-server”

   proof ↗⚑ flag

   SavvyCal—none0/10

   No evidence of any natural-language command interface, AI assistant, or chat-based control for SavvyCal; the evidence only covers scheduling features, REST API, webhooks, and OAuth. Probes for llms.txt and OpenAPI spec both returned 404, further indicating no AI-native interface layer.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Calendly—none0/10

   Evidence shows Calendly has REST API docs, MCP server docs, and markdown-based developer documentation, but nothing describes an interactive API reference with runnable/try-it-now examples (e.g., a Swagger/OpenAPI explorer or live code sandbox).

   ⚑ flag

   SavvyCal—none0/10

   Evidence confirms SavvyCal has a REST API with OAuth/bearer/personal-access-token docs, but nothing describes an interactive reference with runnable/try-it examples, and probes for openapi.json/swagger.json/llms.txt all return 404, suggesting no such interactive spec is discoverable.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Calendly—none0/10

   Evidence describes Calendly's REST API v2, webhooks, embed API, and MCP server, but nowhere mentions a downloadable OpenAPI/Swagger spec or other machine-readable API schema file. The llms.txt and markdown docs are AI-friendly documentation, not a formal API spec artifact.

   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Embed API: Our simpler, easy-to-use API that lets you add a Calendly landing or booking page to your website.”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.calendly.com/llms.txt # Calendly | Developer Documentation ## Instructions for AI Agents - F…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.calendly.com/docs/getting-started/overview.md > Calendly developer docs. For page Markdown, app…”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal documents a REST API with OAuth/PAT auth (savvycal-docs-1, -38, -52), and the API reference format (Bearer Auth listings) suggests it may be generated from an OpenAPI schema, but no evidence shows a downloadable OpenAPI/Swagger spec is actually published. Direct probes for openapi.json, swagger.json, and llms.txt all returned 404, contradicting any claim of a machine-readable spec being available.

   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... Personal access token authentication ... Bearer format: pt_secret_XXXXXXXXX”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Calendly—none0/10

   No evidence of a sandbox, test mode, or non-production environment in Calendly's API/MCP/developer docs; all references point to live scheduling, webhooks, and OAuth against real account data with no mention of test/sandbox credentials or data isolation.

   ⚑ flag

   SavvyCal—none0/10

   No evidence of a sandbox, test mode, or staging environment for the SavvyCal API; docs only cover REST API, OAuth, webhooks and personal access tokens with no mention of test data isolation.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Calendly—none0/10

   Evidence shows Calendly has a REST API v2 (calendly-docs-52) and various API guides, but nothing in the pack documents a versioning scheme, deprecation policy, sunset timeline, or backward-compatibility guarantees for API consumers.

   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   The evidence shows SavvyCal has a REST API with OAuth/PAT authentication, but there is no mention anywhere of API versioning or a documented deprecation policy, and probes for openapi/llms.txt specs failed (404s). Missing for 10: any documentation of API version numbers, changelog, or deprecation/sunset policy.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

Ai calendar

1. knowledge workerAI finds and continuously optimizes the best meeting time across all attendees' calendars, not just the first open slot

   weight 1 · round to Calendly
   Calendly~partialcommunity4/10

   Calendly checks connected calendars for conflicts and can show mutual availability or group polls (calendly-docs-49, calendly-comm-13, calendly-docs-32), and its AI assistant 'Callie' coordinates scheduling over email (calendly-docs-27, calendly-docs-19), but there is no evidence of an AI layer that actively ranks or continuously re-optimizes among multiple valid slots across all attendees rather than surfacing the first mutually free slot. Missing for 10: documented optimization logic (e.g. scoring/ranking slots by preference, time-zone fairness, or meeting fatigue), evidence of 'continuous' re-optimization after initial booking, and independent confirmation that Callie/AI picks anything beyond the first available slot.

   • [claimed-docs] “Sync your calendars so Calendly can check for conflicts before someone books time.”
   • [claimed-docs] “Add Callie to any email thread to coordinate scheduling on your behalf without switching tools or sacrificing control.”
   • [claimed-docs] “An AI assistant that schedules over email”
   • [claimed-docs] “Coordinate time with groups using polls or quickly spin up one-time meeting links.”
   • [community] “I used to work at Calendly. One of the most powerful features we built was the ability to show availability both ways, so if the person book…”
   • [community] “Calendly still has the killer feature of being able to check multiple calendars to find scheduling blocks.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal offers collective/round-robin availability views and 'ranked availability windows' but these are rule-based scheduling features, not an AI system that finds and continuously re-optimizes the best time as calendars change; no evidence of any AI/ML-driven optimization engine is present in the evidence pack.

   • [claimed-docs] “Show collective availability to book any available team member.”
   • [claimed-docs] “Present ranked availability windows to encourage recipients to pick the optimal time (while still remaining flexible).”
   • [claimed-docs] “Show combined availability for your whole team and automatically route each booked meeting to the right person.”

   proof ↗⚑ flag

2. knowledge workerAI schedules my tasks into real calendar blocks around meetings and deadlines, and re-plans automatically when things change

   weight 2 · round drawn
   Calendly—none0/10

   Calendly's evidence covers meeting scheduling, availability sharing, webhooks, routing, and an AI email assistant (Callie) that coordinates meeting times with people — nothing describes AI blocking time for personal tasks/deadlines or automatically re-planning a task schedule around meetings. This is a fair question for a scheduling product but no evidence supports task-level AI planning or replanning.

   • [claimed-docs] “An AI assistant that schedules over email”
   • [claimed-docs] “Add Callie to any email thread to coordinate scheduling on your behalf without switching tools or sacrificing control.”
   • [claimed-docs] “Get meeting recaps and action items, plus an AI assistant to help with the work around meetings.”
   • [claimed-docs] “Use Workflows to automate pre- and post-meeting emails and texts to invitees, hosts, and teammates.”
   • [claimed-docs] “Send a reschedule request when your plans change and let recipients choose a new time.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal is a scheduling-link tool with API/webhooks/workflows, but there is no evidence of AI-driven autonomous task scheduling into calendar blocks or automatic re-planning around deadlines/meetings; its 'workflows' are manual/trigger-based automations, not AI task planning.

   • [claimed-docs] “Budget your time using calendar events, and wire up SavvyCal to honor those preferences.”
   • [claimed-docs] “It’s never been easier to send customized meeting lifecycle messages and automate manual tasks with SavvyCal workflows.”
   • [claimed-docs] “Keep your automations neatly organized with powerful multi-action workflows.”

   proof ↗⚑ flag

3. knowledge workerThe product auto-defends recurring focus time and habits, flexibly moving them when conflicts appear instead of dropping them

   weight 2 · round drawn
   Calendly—none0/10

   Calendly's evidence covers meeting booking, availability sync, conflict-checking during booking, workflows, and reminders, but nothing describes automatically defending or rescheduling recurring focus-time/habit blocks when conflicts arise. This is a plausible scheduling-tool capability, so the axis applies, but no feature in the pack matches it.

   ⚑ flag

   SavvyCal—none0/10

   SavvyCal's evidence covers scheduling links, availability, round robin, workflows, and payments, but there is no mention of auto-defending recurring focus time/habits or dynamically rescheduling blocked time when conflicts arise. The 'budget your time using calendar events' feature (docs-12) is the closest but only describes honoring preferences during booking, not proactive conflict-driven rescheduling of habits.

   • [claimed-docs] “Budget your time using calendar events, and wire up SavvyCal to honor those preferences.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Calendly—none0/10

   All documented API, MCP, and workflow capabilities (booking a single event, creating one event type, single webhook payloads, single embed) operate on individual items; no evidence of any batch/bulk endpoints, bulk import/export, or multi-item automation operations. missing for 10: bulk API endpoints, batch MCP tools, bulk event-type/contact management, and any documented mass-operation feature.

   • [claimed-docs] “Enable AI assistants or agents in your product to **book meetings end‑to‑end** via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type | `POST /event_types`”
   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal exposes a REST API and webhooks, which could in principle support bulk operations, but no evidence describes any batch/bulk endpoints, batch scheduling actions, or bulk update/import/export capability across links, meetings, or contacts.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Calendly
   Calendly✓fullclaimed7/10

   Calendly's native Workflows feature lets users automate pre- and post-meeting emails/texts triggered by scheduling events (booking, cancellation, reminders), and Routing Forms add conditional logic to trigger different flows; webhooks further let external systems react to scheduling events in real time. This directly matches 'rules that trigger actions on events,' though evidence is first-party docs/marketing rather than independent hands-on confirmation of Workflow behavior. Missing for 10: independent/hands-on validation of Workflows automation in practice, and richer detail on conditional/branching rule depth beyond fixed-answer routing.

   • [claimed-docs] “Use Workflows to automate pre- and post-meeting emails and texts to invitees, hosts, and teammates.”
   • [claimed-docs] “Schedule a reminder email in a single click, so recipients who haven't booked yet don't slip through the cracks.”
   • [claimed-docs] “Send a reschedule request when your plans change and let recipients choose a new time.”
   • [claimed-docs] “Create a routing form that uses basic routing logic (fixed answer responses) to screen and qualify people before they book with you.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “payloads will be sent in real time to your server endpoint when events are scheduled or canceled by either the host or the invitee”
   • [claimed-docs] “Gain confidence in the authenticity of your webhooks when you use a **webhook signing key**, a unique secret key shared between your applica…”

   proof ↗⚑ flag

   SavvyCal~partialclaimed7/10

   SavvyCal's Workflows feature lets users attach multi-action automations to scheduling links that trigger on meeting lifecycle events (booked, reminder, follow-up), and webhooks plus Zapier extend this to external CRM/task actions, which is genuine event-driven automation. However the evidence shows this is scoped to meeting-lifecycle triggers rather than general conditional rule logic (if/then branching) across arbitrary events. Missing for 10: documented conditional/branching rule syntax, evidence of custom trigger conditions beyond meeting stages, and independent/hands-on confirmation of workflow reliability.

   • [claimed-docs] “It’s never been easier to send customized meeting lifecycle messages and automate manual tasks with SavvyCal workflows.”
   • [claimed-docs] “Attach workflows to one or more links to save yourself from repetitive work.”
   • [claimed-docs] “Keep your automations neatly organized with powerful multi-action workflows.”
   • [claimed-docs] “Create or update CRM records, send yourself reminders, or create to-do’s in your project management software.”
   • [claimed-docs] “Trigger no-code automations with Zapier ... Sync with your CRM, send yourself reminders, create project management to-do’s…the sky’s the lim…”
   • [claimed-docs] “Webhooks allow you to listen for changes in a SavvyCal account and get notified via HTTP POST requests.”
   • [claimed-docs] “Navigate to Settings > Integrations and click the + icon in the Webhooks”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Calendly
   Calendly~partialclaimed4/10

   Calendly's 'Workflows' feature automates recurring pre-/post-meeting communications (reminders, follow-ups) and webhooks provide real-time triggers for scheduled/canceled events, giving some automation-depth for meeting-related processes. However, there is no evidence of general-purpose recurring job/task scheduling (e.g., cron-like recurring workflows or recurring event automation for arbitrary AI-agent tasks) beyond meeting-centric communications. missing for 10: evidence of recurring event/meeting scheduling itself, evidence of AI agents configuring recurring workflows via API/MCP, independent confirmation of Workflows reliability for automation beyond marketing copy.

   • [claimed-docs] “Use Workflows to automate pre- and post-meeting emails and texts to invitees, hosts, and teammates.”
   • [claimed-docs] “Schedule a reminder email in a single click, so recipients who haven't booked yet don't slip through the cracks.”
   • [claimed-docs] “Send a reschedule request when your plans change and let recipients choose a new time.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “payloads will be sent in real time to your server endpoint when events are scheduled or canceled by either the host or the invitee”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal's 'workflows' feature (docs-15/16/25/26) triggers actions based on meeting lifecycle events (booking, reminders, CRM updates), not on a recurring/cron-like schedule independent of a meeting trigger; there is no evidence of scheduling arbitrary recurring jobs or workflows for AI-native automation.

   • [claimed-docs] “It’s never been easier to send customized meeting lifecycle messages and automate manual tasks with SavvyCal workflows.”
   • [claimed-docs] “Attach workflows to one or more links to save yourself from repetitive work.”
   • [claimed-docs] “Keep your automations neatly organized with powerful multi-action workflows.”
   • [claimed-docs] “Create or update CRM records, send yourself reminders, or create to-do’s in your project management software.”
   • [claimed-docs] “Trigger no-code automations with Zapier ... Sync with your CRM, send yourself reminders, create project management to-do’s…the sky’s the lim…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Calendly—none0/10

   No evidence anywhere in the pack of automation versioning, change history, review/approval workflows, or rollback for Workflows, routing forms, or event types; Calendly's docs cover API/MCP/webhooks/embeds but nothing about tracking or reverting automation configurations over time.

   ⚑ flag

   SavvyCal—none0/10

   SavvyCal offers workflows/automations (docs-15, docs-16, docs-25) but there is no evidence of any version history, change review, diffing, or rollback capability for these automations or workflows.

   ⚑ flag

Booking

1. founderShare a booking link where invitees pick a time from my live availability — no back-and-forth email

   weight 3 · round drawn
   Calendly✓fullcommunity9/10

   Calendly's core product is exactly this: shareable booking links/pages showing live availability (synced across calendars) that invitees can pick from without email back-and-forth, corroborated by extensive docs (event types, embed pages, calendar sync/conflict checking) and strong community testimony confirming it eliminates scheduling ping-pong. Missing for 10: no first-party quantitative data on conversion/adoption beyond anecdotal community praise.

   • [claimed-docs] “Calendly offers pre-built event types that make scheduling easy for everyone.”
   • [claimed-docs] “Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and daily limits.”
   • [claimed-docs] “Make it easy for people to schedule from your website, LinkedIn, email, and beyond without extra steps or manual coordination.”
   • [claimed-docs] “Sync your calendars so Calendly can check for conflicts before someone books time.”
   • [claimed-docs] “To use the link to initialize an embed, replace the `myLink` variable with the landing page link or event type link found in the `scheduling…”
   • [community] “I recently went through an Amazon interview round and had to send my availability three times because none of my slots worked; with a Calend…”
   • [community] “I have used Calendly at work for the last 3 years. It's a lifesaver for scheduling two or more people with moderately busy schedules.”
   • [community] “Calendly still has the killer feature of being able to check multiple calendars to find scheduling blocks.”
   • [community] “I used to work at Calendly. One of the most powerful features we built was the ability to show availability both ways, so if the person book…”

   proof ↗⚑ flag

   SavvyCal✓fullclaimed9/10

   SavvyCal's core product is booking links that show live availability, embeddable via widget/hyperlink/JS, with calendar overlay so invitees pick a mutual time without email back-and-forth. This is well documented across multiple first-party pages. Missing for 10: independent/third-party hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Adjust the colors, banner image, and avatar that appear on your links to match your unique style.”
   • [claimed-docs] “Host your scheduling links on your own custom domain, for a professional white-labeled booking experience.”
   • [claimed-docs] “Recipients can even overlay their calendar on top of your link to spot ideal times at a glance!”
   • [claimed-docs] “The recipient can view their calendar events on top of your scheduling link, to save them the hassle of clicking back and forth.”
   • [claimed-docs] “Let visitors schedule time without ever leaving your website. Trigger your embedded link via hyperlink, the floating button, or a JavaScript…”
   • [claimed-docs] “Generate a snippet of text to propose times in just seconds. Recipients can pick a time to meet in just two clicks.”

   proof ↗⚑ flag

2. founderOffer multiple event types with their own durations, locations, custom questions, and confirmation rules

   weight 2 · round to SavvyCal
   Calendly!disputedcontradicted4/10

   Docs show Calendly supports creating distinct event types (one-on-one, group, round-robin) with custom durations, availability rules, and templates (docs-16, docs-56, docs-45, docs-38, docs-42), but a hands-on community report states Calendly explicitly refused to add manual confirmation/approval rules for bookings, directly contradicting the 'confirmation rules' part of the story (calendly-comm-9). Custom-question configuration is only vaguely implied via 'admin controls' rather than directly documented. missing for 10: explicit documentation of custom booking questions per event type, and confirmation/approval workflow support that isn't contradicted by community evidence.

   • [claimed-docs] “Calendly offers pre-built event types that make scheduling easy for everyone.”
   • [claimed-docs] “Whether you're booking one-on-one appointments, multi-host sales demos, or group classes, Calendly offers pre-built event types that make sc…”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type | `POST /event_types`”
   • [claimed-docs] “Round-robin & team scheduling”
   • [claimed-docs] “Only get booked when you want to be. Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and …”
   • [community] “x.ai used to have manual confirmation before shutting down. We tried to raise this with Calendly but they refused: their answer was that man…”

   proof ↗⚑ flag

   SavvyCal~partialclaimed4/10

   Evidence confirms SavvyCal supports multiple customizable scheduling links (branding, payment integration, booking limits, workflows attached to links), implying separate 'event types' per link, but nothing in the pack explicitly documents per-link duration settings, location options, custom intake questions, or confirmation/approval rules. missing for 10: explicit docs on setting duration per link, location fields, custom questions builder, and confirmation-required vs auto-confirm booking rules.

   • [claimed-docs] “Connect your link to a corresponding product in your Stripe account and require payment before reserving the meeting time.”
   • [claimed-docs] “Limit how many meetings are allowed on a per-day, week, and month basis.”
   • [claimed-docs] “Attach workflows to one or more links to save yourself from repetitive work.”
   • [claimed-docs] “Adjust the colors, banner image, and avatar that appear on your links to match your unique style.”
   • [claimed-docs] “Host your scheduling links on your own custom domain, for a professional white-labeled booking experience.”
   • [claimed-docs] “Prevent meeting overload and cap quantity per day, week, and month.”

   proof ↗⚑ flag

Booking controls

1. knowledge workerProtect my calendar with buffers before and after meetings, minimum notice, daily booking caps, and date-range windows

   weight 2 · round to Calendly
   Calendly~partialcommunity6/10

   Docs explicitly confirm 'meeting buffers, custom schedules, and daily limits' as availability controls (calendly-docs-15, calendly-docs-42), directly supporting buffers and daily booking caps. However, the evidence pack never explicitly mentions minimum notice periods or date-range scheduling windows, and one community comment (calendly-comm-15) notes users historically requested daily-hour limits, suggesting some availability controls were incomplete at some point. Missing for 10: explicit documentation of minimum-notice settings, explicit documentation of date-range/window limits, and independent confirmation these specific sub-features work as described.

   • [claimed-docs] “Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and daily limits.”
   • [claimed-docs] “Only get booked when you want to be. Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and …”
   • [community] “There's a long list of simple features that calend.ly users have been asking for a long time... Top of my list: limit the total number of ho…”

   proof ↗⚑ flag

   SavvyCal~partialclaimed5/10

   SavvyCal explicitly documents daily/weekly/monthly booking caps (docs-11, docs-36) and 'budget your time' calendar-based preferences that could relate to buffers/notice (docs-12), but there is no explicit mention of configurable pre/post-meeting buffers, minimum notice period, or date-range availability windows in the evidence pack. missing for 10: explicit buffer-before/after-meeting settings, minimum notice period configuration, and date-range window limits.

   • [claimed-docs] “Limit how many meetings are allowed on a per-day, week, and month basis.”
   • [claimed-docs] “Prevent meeting overload and cap quantity per day, week, and month.”
   • [claimed-docs] “Budget your time using calendar events, and wire up SavvyCal to honor those preferences.”

   proof ↗⚑ flag

2. founderCollect payment (e.g. via Stripe) at the moment of booking for paid sessions

   weight 1 · round to SavvyCal
   Calendly~partialclaimed6/10

   Calendly's marketing docs confirm native Stripe/PayPal integration for collecting payment at booking, including charging upfront and selling packages, which directly supports this founder story. However, there is no deeper first-party documentation of the paid-session setup flow, no API/developer docs for payment collection, and no independent or hands-on evidence confirming it works reliably in practice. Missing for 10: developer-level docs on the payments API/webhook flow, independent/hands-on confirmation of the paid booking experience, and edge-case handling (refunds, failed payments).

   • [claimed-docs] “Charge upfront for meetings, sell packages, and send invoices with payment features that make it easy to get paid.”
   • [claimed-docs] “Connect Stripe, PayPal”

   proof ↗⚑ flag

   SavvyCal✓fullclaimed8/10

   SavvyCal's docs explicitly describe connecting a Stripe product to a scheduling link and requiring payment before reserving the meeting time, plus Stripe Tax support for sales tax/VAT/GST and native management of offerings/pricing within SavvyCal. This directly matches the founder story of collecting payment at booking. Missing for 10: independent/hands-on verification of the payment flow (all evidence is vendor docs) and no detail on payment failure/refund handling.

   • [claimed-docs] “Connect your link to a corresponding product in your Stripe account and require payment before reserving the meeting time.”
   • [claimed-docs] “Calculate and collect sales tax, VAT, and GST with the click of a button (powered by Stripe Tax).”
   • [claimed-docs] “You don’t even have to leave SavvyCal to create new offerings or adjust your prices. Do it all natively within SavvyCal.”
   • [claimed-docs] “Connect your Stripe account to collect payments on your scheduling links. Collect sales tax if needed & accept any payment method available …”

   proof ↗⚑ flag

3. knowledge workerInvitees always see slots in their own time zone — detection, display, and DST handling are automatic

   weight 3 · round drawn
   Calendly—none0/10

   No evidence in the pack addresses time-zone detection, display, or DST handling for invitees on booking pages; the pack covers API/MCP/embed/webhook features and general community sentiment, none of which speak to time zone automation.

   ⚑ flag

   SavvyCal—none0/10

   No evidence pack item mentions time zone detection, display, or DST handling for invitees; the docs focus on API, webhooks, embedding, team scheduling, and payments but never address time zone automation.

   ⚑ flag

Calendars

1. knowledge workerBusy blocks sync between my work and personal calendars automatically so all my schedules stay in step

   weight 2 · round to Calendly
   Calendly✓fullcommunity8/10

   Calendly's core scheduling engine explicitly connects and syncs multiple calendars (work/personal) to check for conflicts before allowing bookings, per docs-15/42/49, and this is independently corroborated as a 'killer feature' in community discussion (comm-6). One user reports a specific failure mode when a Google Calendar is manually disabled (comm-10), which is a minor caveat rather than a systemic contradiction. Missing for 10: no first-party detail on sync latency/two-way write-back mechanics or handling of edge-case calendar disconnections beyond the one anecdotal failure.

   • [claimed-docs] “Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and daily limits.”
   • [claimed-docs] “Only get booked when you want to be. Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and …”
   • [claimed-docs] “Sync your calendars so Calendly can check for conflicts before someone books time.”
   • [community] “Calendly still has the killer feature of being able to check multiple calendars to find scheduling blocks.”
   • [community] “Every time I try to use Calendly, it fails because I've disabled Google Calendar from my Google Account.”

   proof ↗⚑ flag

   SavvyCal~partialclaimed5/10

   SavvyCal's docs reference including external/multiple calendars in availability checks and budgeting time via calendar events, implying busy blocks from connected calendars feed into scheduling, but no evidence explicitly describes connecting a personal AND work calendar and syncing busy blocks automatically between them for an individual user's own scheduling link. missing for 10: explicit documentation of multi-calendar (work+personal) connection and automatic busy-block sync for a single user, plus independent/hands-on confirmation.

   • [claimed-docs] “Include external calendars when showing team availability.”
   • [claimed-docs] “Budget your time using calendar events, and wire up SavvyCal to honor those preferences.”
   • [claimed-docs] “Allow recipients to overlay their calendar on top of yours to easily find mutual availability.”
   • [claimed-docs] “The recipient can view their calendar events on top of your scheduling link, to save them the hassle of clicking back and forth.”

   proof ↗⚑ flag

2. knowledge workerConnect several calendars (Google, Outlook, Apple) and every one is checked for conflicts so I never get double-booked

   weight 3 · round to Calendly
   Calendly✓fullcommunity8/10

   Calendly explicitly advertises connecting multiple calendars and syncing them to check for conflicts before booking (calendly-docs-15, calendly-docs-42, calendly-docs-49), and this is independently corroborated by long-time users calling multi-calendar conflict checking a 'killer feature' (calendly-comm-6) and describing two-way availability checks (calendly-comm-13). Missing for 10: explicit naming of Google/Outlook/Apple as the three supported providers in one place, and a hands-on report confirming zero double-booking across all three simultaneously (one community note shows failure if a user disables Google Calendar integration, calendly-comm-10, though this is a config issue rather than a conflict-detection failure).

   • [claimed-docs] “Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and daily limits.”
   • [claimed-docs] “Only get booked when you want to be. Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and …”
   • [claimed-docs] “Sync your calendars so Calendly can check for conflicts before someone books time.”
   • [community] “Calendly still has the killer feature of being able to check multiple calendars to find scheduling blocks.”
   • [community] “I used to work at Calendly. One of the most powerful features we built was the ability to show availability both ways, so if the person book…”
   • [community] “Every time I try to use Calendly, it fails because I've disabled Google Calendar from my Google Account.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   The evidence pack covers API/webhooks, round-robin scheduling, payments, and workflows, but contains no mention of connecting multiple external calendars (Google/Outlook/Apple) or cross-calendar conflict checking for double-booking prevention — the closest items reference 'external calendars' only in the context of team availability aggregation, not personal multi-calendar conflict-checking.

   • [claimed-docs] “Include external calendars when showing team availability.”

   proof ↗⚑ flag

3. knowledge workerDefine availability schedules with working hours, date overrides, and out-of-office periods

   weight 2 · round to Calendly
   Calendly~partialclaimed5/10

   Calendly docs confirm core availability configuration — connecting multiple calendars, custom schedules, meeting buffers, and daily limits (calendly-docs-15, calendly-docs-42, calendly-docs-49) — which covers 'working hours' definition and calendar-conflict checking. However, the evidence pack never explicitly mentions date-specific overrides or out-of-office period settings, so that part of the story is unevidenced. Missing for 10: explicit documentation of date overrides (one-off schedule changes for specific days) and out-of-office/vacation period support.

   • [claimed-docs] “Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and daily limits.”
   • [claimed-docs] “Only get booked when you want to be. Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and …”
   • [claimed-docs] “Sync your calendars so Calendly can check for conflicts before someone books time.”

   proof ↗⚑ flag

   SavvyCal~partialclaimed3/10

   Evidence only tangentially references availability settings — 'preset work hours' for round-robin links and 'budget your time using calendar events' to honor scheduling preferences — but there is no explicit documentation of a full availability-schedule builder with working hours, date overrides, or dedicated out-of-office periods. missing for 10: explicit docs on defining weekly working-hour schedules, date-specific overrides, and out-of-office blocking.

   • [claimed-docs] “Budget your time using calendar events, and wire up SavvyCal to honor those preferences.”
   • [claimed-docs] “Team members can set custom availability for each round robin scheduling link or default to their preset work hours.”
   • [claimed-docs] “Limit how many meetings are allowed on a per-day, week, and month basis.”
   • [claimed-docs] “Prevent meeting overload and cap quantity per day, week, and month.”

   proof ↗⚑ flag

Platform

1. developerWebhooks notify my systems in real time when bookings are created, rescheduled, or canceled

   weight 2 · round to Calendly
   Calendly✓fullclaimed9/10

   Calendly's docs explicitly describe a Webhook API/webhook subscriptions that send real-time payloads to a developer's endpoint when meetings are scheduled, canceled, or rescheduled by host or invitee, plus signing keys for verifying authenticity. Missing for 10: independent/hands-on developer corroboration of webhook reliability or latency in production use.

   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “payloads will be sent in real time to your server endpoint when events are scheduled or canceled by either the host or the invitee”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [claimed-docs] “Gain confidence in the authenticity of your webhooks when you use a **webhook signing key**, a unique secret key shared between your applica…”

   proof ↗⚑ flag

   SavvyCal✓fullclaimed8/10

   SavvyCal docs explicitly describe webhooks for listening to account changes via HTTP POST, with HMAC-SHA256 signature verification and setup instructions via Settings > Integrations. Missing for 10: explicit enumeration of specific event types (booking created/rescheduled/canceled) and independent/hands-on confirmation of real-time delivery reliability.

   • [claimed-docs] “Webhooks allow you to listen for changes in a SavvyCal account and get notified via HTTP POST requests.”
   • [claimed-docs] “SavvyCal signs the request body with a SHA-256 HMAC signature. The signature is included in the x-savvycal-signature header.”
   • [claimed-docs] “SavvyCal signs the request body with a SHA-256 HMAC signature.”
   • [claimed-docs] “Navigate to Settings > Integrations and click the + icon in the Webhooks”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”

   proof ↗⚑ flag

2. developerA documented REST API lets me manage event types, availability, and bookings programmatically — enough to build scheduling into my own product

   weight 3 · round to Calendly
   Calendly✓fullclaimed8/10

   Calendly publishes a documented REST v2 API for event types, availability, and bookings, with OAuth/PAT authentication, webhooks for real-time booking events, and embed/API guides for building scheduling into external products (calendly-docs-3,4,7,9,24,52,54). This directly matches the developer story of programmatic scheduling management. Missing for 10: independent/hands-on developer corroboration of the REST API itself (community evidence only covers end-user scheduling UX, not API integration experience) and no mention of rate limits or SDKs.

   • [claimed-docs] “If you're integrating an **internal application** that only your team will use, authenticate with **personal access tokens**.”
   • [claimed-docs] “If you're integrating a **public application** that many Calendly users will use, authenticate with **OAuth**.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “Effectively share available meeting times from an external application to increase the probability of meetings being booked and enhance the …”
   • [claimed-docs] “Calendly users can retrieve information about availability for a specific event type”
   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [claimed-docs] “Gain confidence in the authenticity of your webhooks when you use a **webhook signing key**, a unique secret key shared between your applica…”

   proof ↗⚑ flag

   SavvyCal~partialprobed6/10

   SavvyCal documents a REST API with OAuth2/personal-access-token auth and a 'SavvyCal Meetings API' plus webhooks and a JS embed library, indicating programmatic access to scheduling functionality. However, the evidence never specifies concrete endpoints for event types, availability, or bookings, and probes show no discoverable OpenAPI/swagger spec or llms.txt, leaving the exact API surface unconfirmed. Missing for 10: explicit endpoint/resource documentation for event types, availability, and bookings, and a machine-readable API spec (404s on openapi.json/swagger.json).

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... HTTP: Bearer Auth ... Personal access token authentication”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... Personal access token authentication ... Bearer format: pt_secret_XXXXXXXXX”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

3. developerSelf-host the full scheduling engine from source or a container image under an open-source license

   weight 2 · round drawn
   Calendly—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   SavvyCal—none0/10

   SavvyCal is a hosted SaaS scheduling product; evidence shows only a REST API, webhooks, and JS embed for integration, with a page listing 'open-source contributions' but no self-hostable engine, source release, or container image. No evidence of any self-hosting capability under an open-source license.

   • [claimed-docs] “Here are some of our contributions to the community”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”

   proof ↗⚑ flag

Embeds

1. sales leadBookings flow into my CRM and automation stack (Salesforce, HubSpot, Zapier) without manual copying

   weight 2 · round to Calendly
   Calendly~partialclaimed7/10

   Calendly's docs show real CRM-touching integration: routing forms auto-match leads to Salesforce/HubSpot owners, report on conversions from HubSpot/Marketo/Pardot forms, and webhooks/REST API push scheduling data to external systems in real time, which underpins tools like Zapier. However, no evidence explicitly documents a native Zapier app/connector or two-way CRM record sync, so the story is only partially evidenced. Missing for 10: explicit Zapier integration documentation, and evidence of automatic write-back of booking data into Salesforce/HubSpot records (beyond lead-owner matching).

   • [claimed-docs] “Automatically look up and match known leads to assigned account owners from Salesforce and HubSpot.”
   • [claimed-docs] “Import third party forms into Calendly and simply build scheduling routes from visible or hidden fields — as well as Salesforce ownership st…”
   • [claimed-docs] “Report on conversion rates to see the percentage of scheduled meetings coming from Calendly, HubSpot, Marketo, or Pardot forms.”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “payloads will be sent in real time to your server endpoint when events are scheduled or canceled by either the host or the invitee”
   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”

   proof ↗⚑ flag

   SavvyCal~partialclaimed6/10

   SavvyCal explicitly supports Zapier for CRM syncing and workflow automations (create/update CRM records), plus webhooks and a REST API for custom integrations, which together enable bookings to flow into CRM/automation stacks without manual copying. However, there is no evidence of native, first-party Salesforce or HubSpot integrations — only generic Zapier and webhook/API-based paths, which require setup/configuration rather than a turnkey connection. Missing for 10: dedicated Salesforce/HubSpot native integrations, documented pre-built Zaps or CRM field-mapping templates, and independent case studies confirming reliable no-manual-copy CRM sync in practice.

   • [claimed-docs] “Trigger no-code automations with Zapier ... Sync with your CRM, send yourself reminders, create project management to-do’s…the sky’s the lim…”
   • [claimed-docs] “Create or update CRM records, send yourself reminders, or create to-do’s in your project management software.”
   • [claimed-docs] “Trigger no-code automations with Zapier Sync with your CRM, send yourself reminders, create project management to-do’s…the sky’s the limit.”
   • [claimed-docs] “Webhooks allow you to listen for changes in a SavvyCal account and get notified via HTTP POST requests.”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”

   proof ↗⚑ flag

2. developerEmbed the booking experience in my own site — inline, popup, or floating widget — with a documented snippet

   weight 2 · round drawn
   Calendly✓fullclaimed8/10

   Calendly's official docs explicitly document the Embed API with three embed types, including code snippets like Calendly.initInlineWidget({url: myLink}) and instructions to swap in the scheduling_url, covering inline, popup, and floating widget use cases. missing for 10: no explicit popup/floating widget code snippet shown (only inline snippet included), and no independent/hands-on developer corroboration of the embed snippet working as documented.

   • [claimed-docs] “You can display the scheduling page for users of your app when you initialize [one of three embed types]”
   • [claimed-docs] “You can display the scheduling page for users of your app when you initialize one of three embed types”
   • [claimed-docs] “Embed Calendly in your product”
   • [claimed-docs] “To use the link to initialize an embed, replace the `myLink` variable with the landing page link or event type link found in the `scheduling…”
   • [claimed-docs] “To initilize an **inline** embed, use `Calendly.initInlineWidget({url: myLink});`”
   • [claimed-docs] “Embed API: Our simpler, easy-to-use API that lets you add a Calendly landing or booking page to your website.”

   proof ↗⚑ flag

   SavvyCal✓fullclaimed8/10

   SavvyCal documents a JavaScript embed library supporting inline, popover, and floating widget embeds, plus hyperlink/JS-call triggers, matching the story closely (savvycal-docs-2, savvycal-docs-18, savvycal-docs-49, savvycal-docs-52). Missing for 10: a directly-quoted code snippet in the evidence pack and independent/hands-on confirmation of the embed working on a third-party site.

   • [claimed-docs] “Our JavaScript library allows you to embed your scheduling links on your website (both inline and as a popover).”
   • [claimed-docs] “Display scheduling links inline, via a floating widget, or triggered based clicking a hyperlink.”
   • [claimed-docs] “Let visitors schedule time without ever leaving your website. Trigger your embedded link via hyperlink, the floating button, or a JavaScript…”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”

   proof ↗⚑ flag

Workflows

1. sales leadAutomated reminder and follow-up sequences (email/SMS) fire around every booking to cut no-shows

   weight 2 · round to Calendly
   Calendly✓fullclaimed8/10

   Calendly's Workflows feature explicitly automates pre- and post-meeting emails and texts to invitees, hosts, and teammates, including one-click reminder emails and reschedule requests, directly matching the no-show-reduction use case sales leads need. This is documented first-party (docs-12,13,14) and supported by broader automated-communication feature docs, though evidence lacks independent/community corroboration specifically on SMS reminders or no-show reduction outcomes. Missing for 10: independent/hands-on verification of SMS reminders and measurable no-show impact.

   • [claimed-docs] “Use Workflows to automate pre- and post-meeting emails and texts to invitees, hosts, and teammates.”
   • [claimed-docs] “Schedule a reminder email in a single click, so recipients who haven't booked yet don't slip through the cracks.”
   • [claimed-docs] “Send a reschedule request when your plans change and let recipients choose a new time.”
   • [claimed-docs] “Send personalized emails with your scheduling link without switching between Calendly and your inbox.”

   proof ↗⚑ flag

   SavvyCal~partialclaimed6/10

   SavvyCal's Workflows feature explicitly supports sending customized 'meeting lifecycle messages' with adjustable timing and content designed 'to minimize no-shows,' plus Zapier integration for further automation (e.g., SMS via third-party apps). However, native SMS reminders are not documented—only email-based workflow messages and templates are described, with SMS presumably requiring Zapier/CRM integration rather than being built-in. missing for 10: native SMS reminder capability, evidence of automatic sequencing/multi-touch cadence beyond single reminders, independent confirmation of no-show reduction impact.

   • [claimed-docs] “It’s never been easier to send customized meeting lifecycle messages and automate manual tasks with SavvyCal workflows.”
   • [claimed-docs] “Attach workflows to one or more links to save yourself from repetitive work.”
   • [claimed-docs] “Keep your automations neatly organized with powerful multi-action workflows.”
   • [claimed-docs] “Customize your timing and content to minimize no-shows. Compose from scratch or pick one of our handy templates.”
   • [claimed-docs] “Customize the timing and content of your reminders to increase attendance. Compose from scratch or pick one of our handy templates.”
   • [claimed-docs] “Trigger no-code automations with Zapier ... Sync with your CRM, send yourself reminders, create project management to-do’s…the sky’s the lim…”
   • [claimed-docs] “Trigger no-code automations with Zapier Sync with your CRM, send yourself reminders, create project management to-do’s…the sky’s the limit.”

   proof ↗⚑ flag

2. founderInvitees can reschedule or cancel from their confirmation, with my policies enforced and calendars updated everywhere

   weight 2 · round to Calendly
   Calendly✓fullclaimed7/10

   Calendly's docs confirm invitees can reschedule or cancel meetings, with webhooks firing in real time for both host- and invitee-initiated scheduling changes (calendly-docs-54, calendly-docs-7/23), and calendar sync/conflict-checking plus buffers, custom schedules, and daily limits are documented as ongoing availability policies (calendly-docs-15, calendly-docs-42, calendly-docs-49). This supports the core story of invitee self-service reschedule/cancel with policy enforcement and calendar updates propagating via webhooks/integrations. Missing for 10: explicit documentation of the confirmation-page reschedule/cancel UI itself, explicit statement that scheduling policies (buffers, limits) are re-validated at reschedule time, and independent/hands-on confirmation that calendars update everywhere after an invitee reschedules.

   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [claimed-docs] “When you [create a webhook subscription], payloads will be sent in real time to your server endpoint when events are scheduled or canceled b…”
   • [claimed-docs] “payloads will be sent in real time to your server endpoint when events are scheduled or canceled by either the host or the invitee”
   • [claimed-docs] “Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and daily limits.”
   • [claimed-docs] “Only get booked when you want to be. Connect multiple calendars and fine-tune your availability with meeting buffers, custom schedules, and …”
   • [claimed-docs] “Sync your calendars so Calendly can check for conflicts before someone books time.”
   • [claimed-docs] “Send a reschedule request when your plans change and let recipients choose a new time.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   The evidence pack contains no mention of invitee-initiated rescheduling or cancellation from a confirmation, nor any statement about policy enforcement or calendar sync on such changes. While this is a plausible feature for a scheduling product like SavvyCal, no documentation, webhook event, or feature page in the pack addresses it. Missing for 10: any mention of reschedule/cancel links in confirmations, policy enforcement on changes, or calendar update propagation across all attendees.

   ⚑ flag

3. founderEvery booking gets a video conference link automatically (Zoom, Google Meet, Teams, or native video)

   weight 2 · round to Calendly
   Calendly✓fullclaimed8/10

   Calendly's pricing/docs explicitly state bookings can join Zoom, Google Meet, and Microsoft Teams with recordings & transcripts, confirming automatic video-conference link generation across major providers and native options. Missing for 10: independent hands-on confirmation of the auto-link-attachment flow and any explicit mention of a native Calendly video option beyond the third-party integrations.

   • [claimed-docs] “Recordings & transcripts * Shareable meeting recaps * Joins Zoom, Google Meet, Microsoft Teams”
   • [claimed-docs] “Joins Zoom, Google Meet, Microsoft Teams”
   • [claimed-docs] “Recordings & transcripts”
   • [claimed-docs] “Get meeting recaps and action items, plus an AI assistant to help with the work around meetings.”

   proof ↗⚑ flag

   SavvyCal~partialclaimed5/10

   Evidence shows automatic video link creation for specific providers (Zoom rooms, Google Meet links, Whereby rooms) tied to round-robin scheduling, implying similar support elsewhere, but there's no explicit mention of Teams integration or a general 'native video' option, and no confirmation this applies uniformly to all booking types beyond round-robin links. missing for 10: Microsoft Teams video link support, native/built-in video conferencing option, and confirmation this auto-generation applies to all booking link types (not just round-robin).

   • [claimed-docs] “Automatically create unique Zoom rooms for new events.”
   • [claimed-docs] “Add Meet links to your Google Calendar events.”
   • [claimed-docs] “Attach Whereby meeting rooms to calendar invites.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Calendly
   Calendly~partialclaimed6/10

   Calendly's REST API v2, MCP server, webhooks, and embed API cover core scheduling actions (create event types, book meetings, read availability, contacts, notetaker data) and even expose an AI-native MCP interface for natural-language booking. However, many UI-only features (routing forms with Salesforce/HubSpot logic, Workflows automations, payments/invoicing, admin/team templates, polls) are not shown to have corresponding API/MCP endpoints, so full UI-API parity is not evidenced. Missing for 10: documented API/MCP coverage for routing forms, workflows, payments, admin controls, and team templates; independent confirmation of full parity.

   • [claimed-docs] “Programmatically book meetings and read and write Scheduling, Contacts, and Notetaker data.”
   • [claimed-docs] “It translates natural-language commands (e.g., "Book a 30-minute meeting with Sam next Tuesday") into structured Calendly API calls with no …”
   • [claimed-docs] “Enable AI assistants or agents in your product to **book meetings end‑to‑end** via Calendly's Scheduling API endpoint.”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type”
   • [claimed-docs] “event\_types-create\_event\_type | Create a new event type | `POST /event_types`”
   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”
   • [claimed-docs] “Embed API: Our simpler, easy-to-use API that lets you add a Calendly landing or booking page to your website.”
   • [claimed-docs] “Webhook API: Our friendly, lightweight API that lets you automatically receive Calendly data with webhook subscriptions anytime invitees sch…”
   • [claimed-docs] “Create a routing form that uses basic routing logic (fixed answer responses) to screen and qualify people before they book with you.”
   • [claimed-docs] “Use Workflows to automate pre- and post-meeting emails and texts to invitees, hosts, and teammates.”
   • [claimed-docs] “Charge upfront for meetings, sell packages, and send invoices with payment features that make it easy to get paid.”

   proof ↗⚑ flag

   SavvyCal~partialprobed3/10

   SavvyCal ships a documented REST API, OAuth/personal-access-token auth, webhooks, and a JS embed library, showing genuine API-based access to core scheduling functions, but there is no evidence the API covers the full breadth of UI features (round-robin, meeting polls, workflows, Stripe payment links, custom branding) and probes for an OpenAPI spec/llms.txt both 404, suggesting incomplete or undocumented API surface parity. missing for 10: evidence that advanced UI features (round robin, polls, workflows, payments, branding) are fully exposed via API, a public OpenAPI/schema reference, and independent confirmation of parity.

   • [claimed-docs] “The SavvyCal API adheres to REST conventions. Our API communicates in JSON format and uses OAuth access tokens to authenticate requests.”
   • [claimed-docs] “We offer several ways to integrate with our product, including a REST API, webhooks, and a JavaScript embed library.”
   • [claimed-docs] “OAuth 2.0: OAuth2 ... HTTP: Bearer Auth ... Personal access token authentication”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.savvycal.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.savvycal.com/openapi.json, https://developers.savvycal.com/swagger.json, https://…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Calendly—none0/10

   Evidence shows a REST API for reading/writing specific Scheduling/Contacts/Notetaker data for building integrations, but nothing about a bulk data-export tool, open-format full account export, or data portability/account deletion workflow for a user wanting to leave the platform.

   • [claimed-docs] “Programmatically book meetings and read and write Scheduling, Contacts, and Notetaker data.”
   • [claimed-docs] “The Calendly API v2 is REST-based and has predictable resource-oriented URLs.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   There is no evidence of a bulk data export feature or open-format data portability (e.g., CSV/JSON export of bookings, contacts, workflows) that would let a user take all their data and leave; the API exists for integration, not for full data export, and no explicit export/GDPR-style data-download feature is documented.

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Calendly—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   SavvyCal—none0/10

   SavvyCal is a closed proprietary SaaS scheduling product; the only related evidence is a page mentioning unspecified 'contributions to the community,' not the product's own source code under an open license.

   • [claimed-docs] “Here are some of our contributions to the community”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Calendly—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   SavvyCal—none0/10

   SavvyCal is a hosted SaaS scheduling product with no evidence of a self-hostable core; only an 'open-source contributions' page is mentioned, not a self-hostable server offering.

   • [claimed-docs] “Here are some of our contributions to the community”

   proof ↗⚑ flag

Pricing

1. founderThe free tier covers real individual scheduling — a usable booking link without a paid plan

   weight 2 · round to Calendly
   Calendly~partialcommunity5/10

   Evidence confirms Calendly offers free sign-up with no credit card required (calendly-docs-40, calendly-docs-60) and community reports actually using the free tier for real one-on-one scheduling (calendly-comm-2, calendly-comm-3), but a user also notes a feature they relied on was pulled from the free tier, prompting a switch (calendly-comm-17) — showing the free tier is usable but its scope can shrink over time. There's no first-party pricing doc explicitly enumerating what the free plan includes/excludes for individual scheduling. Missing for 10: explicit vendor documentation of free-tier feature scope/limits, and independent corroboration that a booking link works fully without any paid upgrade over time.

   • [claimed-docs] “Sign up with Google Sign up with Microsoft ... No credit card required”
   • [claimed-docs] “Sign up with email • No credit card required”
   • [community] “I recently went through an Amazon interview round and had to send my availability three times because none of my slots worked; with a Calend…”
   • [community] “I have used Calendly at work for the last 3 years. It's a lifesaver for scheduling two or more people with moderately busy schedules.”
   • [community] “I was using the Calendly free tier, and when a feature I wanted was moved off the free tier, it took me all of 30 minutes to move to zcal.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   The evidence pack contains no mention of a free tier, free plan details, or what a basic booking link includes without payment; only feature and API docs are present, with no pricing-plan breakdown. Missing for 10: any documentation of a free plan's scope/limits, evidence that a usable booking link exists without payment, and confirmation of no-cost individual scheduling.

   ⚑ flag

2. founderPublished per-seat pricing tells me exactly what each tier costs and includes before I talk to sales

   weight 1 · round to Calendly
   Calendly~partialcommunity6/10

   The pricing page evidence lists many per-tier feature inclusions (recordings/transcripts, AI assistant, payments, round-robin, integrations) suggesting a public plan/feature comparison, and community comments (calendly-comm-7, calendly-comm-8) corroborate specific per-seat dollar figures ($8/$12/$16/$20 per user/month) exist publicly. However, the vendor evidence pack itself never quotes explicit dollar amounts per tier, only feature lists, so a founder can infer likely tiering but can't fully verify exact current prices from the cited docs alone. missing for 10: vendor-sourced explicit per-tier dollar pricing, confirmation that all feature/price details are current and consistent across sources.

   • [claimed-docs] “Recordings & transcripts * Shareable meeting recaps * Joins Zoom, Google Meet, Microsoft Teams”
   • [claimed-docs] “An AI assistant that schedules over email”
   • [claimed-docs] “Charge upfront for meetings, sell packages, and send invoices with payment features that make it easy to get paid.”
   • [claimed-docs] “Coordinate time with groups using polls or quickly spin up one-time meeting links.”
   • [claimed-docs] “Connect Stripe, PayPal”
   • [claimed-docs] “Round-robin & team scheduling”
   • [claimed-docs] “Recordings & transcripts”
   • [claimed-docs] “Joins Zoom, Google Meet, Microsoft Teams”
   • [claimed-docs] “Get meeting recaps and action items, plus an AI assistant to help with the work around meetings.”
   • [claimed-docs] “Customizable booking page”
   • [community] “We pay 16/20 USD (yearly/monthly) per user per month to Calendly, and the only reason we pay for their Teams plan is that 'Round Robin' even…”
   • [community] “Calendly is $8/user/month for essentials tier and $12/month for professional tier.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   No evidence pack items reference pricing tiers, per-seat cost, or plan feature comparisons; only savvycal.com/pricing is mentioned once in passing (docs-59) without any pricing details. This is an applicable axis for a SaaS scheduling product, but no evidence shows published per-seat pricing.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Calendly—none0/10

   No evidence in the pack mentions data residency, regional data storage options, or any control over where Calendly stores customer data; the docs cover API/OAuth/MCP/webhooks but never data residency settings.

   ⚑ flag

   SavvyCal—none0/10

   No evidence anywhere in the pack of data residency options, regional storage selection, or data localization controls for SavvyCal; the evidence covers scheduling features and API auth only.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Calendly—none0/10

   No evidence in the pack addresses AI training data opt-out or any privacy controls around model training use of user data; Calendly's docs focus on scheduling, API, MCP, and integrations, not data-use/training policies.

   ⚑ flag

   SavvyCal—none0/10

   No evidence in the pack addresses AI training data usage, opt-out controls, or any privacy policy statement regarding AI model training; SavvyCal is a scheduling product and this specific privacy commitment is unevidenced.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Calendly—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or an ability for AI-native users to configure how long Calendly data (scheduling, contacts, transcripts) is retained or to trigger deletion. Docs cover API/MCP access, webhooks, embeds, and scheduling features, but nothing on retention/deletion settings. Missing for 10: documented data retention policy, user/admin-facing deletion controls, API/MCP endpoints for purging data, and any independent confirmation of these controls working.

   ⚑ flag

   SavvyCal—none0/10

   No evidence found addressing data retention policies, deletion controls, or privacy/data lifecycle management for SavvyCal; the evidence pack covers scheduling features, API auth, and webhooks only.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Calendly—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings for Calendly; documentation focuses on scheduling, API, MCP, webhooks, and authentication, not privacy/telemetry controls.

   ⚑ flag

   SavvyCal—none0/10

   No evidence pack items mention telemetry, usage tracking, analytics opt-out, or privacy controls of this kind; SavvyCal's docs focus on API/webhooks/scheduling features only.

   ⚑ flag

Teams

1. sales leadOffer collective events that only show slots when every required host is free

   weight 2 · round to SavvyCal
   Calendly~partialcommunity5/10

   Docs mention 'multi-host sales demos' and 'Round-robin & team scheduling' plus general team-scheduling admin tools, implying multi-host event types exist, and community notes Calendly can check multiple calendars for scheduling blocks. However, no evidence explicitly describes a 'Collective' event type or confirms the mechanic of only showing slots when every required host is free (as opposed to round-robin, which is a different distribution logic). Missing for 10: explicit documentation of the Collective event type, confirmation of the all-hosts-free slot filtering logic, and independent/hands-on verification.

   • [claimed-docs] “Whether you're booking one-on-one appointments, multi-host sales demos, or group classes, Calendly offers pre-built event types that make sc…”
   • [claimed-docs] “Round-robin & team scheduling”
   • [claimed-docs] “Standardize scheduling with team templates, admin controls, routing forms, meeting distribution tools, and integrations that fold scheduling…”
   • [community] “Calendly still has the killer feature of being able to check multiple calendars to find scheduling blocks.”

   proof ↗⚑ flag

   SavvyCal✓fullclaimed8/10

   SavvyCal explicitly documents collective scheduling links that show combined availability across multiple teammates, only surfacing slots where the whole group is free ('Show combined availability for you and any number of teammates that allow recipients to book a time with your selected group'; 'Combine your availability with multiple colleagues on scheduling links'), distinct from its round-robin (any-available-host) mode. Missing for 10: independent/hands-on corroboration beyond vendor marketing pages and explicit confirmation of 'required host' logic vs optional overlay.

   • [claimed-docs] “Show combined availability for you and any number of teammates that allow recipients to book a time with your selected group.”
   • [claimed-docs] “Combine your availability with multiple colleagues on scheduling links.”
   • [claimed-docs] “Show collective availability to book any available team member.”
   • [claimed-docs] “Show combined availability for your whole team and automatically route each booked meeting to the right person.”

   proof ↗⚑ flag

2. sales leadInbound meetings distribute across my team round-robin, with weighting or priority so load stays fair

   weight 2 · round drawn
   Calendly~partialcommunity6/10

   Calendly explicitly advertises 'Round-robin & team scheduling' and 'meeting distribution tools' plus automatic lead-to-owner matching via routing forms, and community confirms round-robin scheduling is a real, paid-tier feature (calendly-comm-7 notes teams pay specifically for Round Robin). However, no evidence describes weighting or priority-based distribution logic to keep load 'fair' beyond simple round-robin rotation. Missing for 10: documented weighting/priority controls within round-robin, evidence of fairness/load-balancing configuration, and independent confirmation of how ties or capacity differences are handled.

   • [claimed-docs] “Round-robin & team scheduling”
   • [claimed-docs] “Standardize scheduling with team templates, admin controls, routing forms, meeting distribution tools, and integrations that fold scheduling…”
   • [claimed-docs] “Standardize scheduling with team templates, admin controls, routing forms, meeting distribution tools”
   • [claimed-docs] “Automatically look up and match known leads to assigned account owners from Salesforce and HubSpot.”
   • [community] “We pay 16/20 USD (yearly/monthly) per user per month to Calendly, and the only reason we pay for their Teams plan is that 'Round Robin' even…”

   proof ↗⚑ flag

   SavvyCal~partialclaimed6/10

   SavvyCal has dedicated round-robin/pooling features that distribute meetings across team members either by cycling (equal distribution) or random selection for max availability, explicitly marketed for sales use cases. However, there is no evidence of configurable weighting or priority levels among team members (e.g., unequal load ratios) beyond binary equal/random distribution. Missing for 10: explicit weighted/priority-based distribution controls, admin-configurable ratios per rep, and independent confirmation of fairness enforcement over time.

   • [claimed-docs] “Show combined availability for your whole team and automatically route each booked meeting to the right person.”
   • [claimed-docs] “The choice is yours — randomly select who the meeting gets booked with for maximum availability or cycle through team members for equal dist…”
   • [claimed-docs] “Automatically distribute meetings across team members fairly.”
   • [claimed-docs] “Round robin pooling Automatically distribute meetings across team members fairly.”
   • [claimed-docs] “Distribute meetings across a pool of organizers. Perfect for sales and customer support.”
   • [claimed-docs] “Team members can set custom availability for each round robin scheduling link or default to their preset work hours.”

   proof ↗⚑ flag

3. sales leadA routing form qualifies invitees and sends them to the right person or team based on their answers

   weight 1 · round to Calendly
   Calendly✓fullclaimed7/10

   Calendly's routing forms explicitly qualify invitees via basic routing logic and screen/route them to the right person or team, including Salesforce/HubSpot lead-to-owner matching and team distribution tools. Missing for 10: independent/hands-on validation of routing form accuracy, conditional branching depth, and conversion reporting beyond vendor docs.

   • [claimed-docs] “Automatically look up and match known leads to assigned account owners from Salesforce and HubSpot.”
   • [claimed-docs] “Create a routing form that uses basic routing logic (fixed answer responses) to screen and qualify people before they book with you.”
   • [claimed-docs] “Standardize scheduling with team templates, admin controls, routing forms, meeting distribution tools, and integrations that fold scheduling…”
   • [claimed-docs] “Standardize scheduling with team templates, admin controls, routing forms, meeting distribution tools”
   • [claimed-docs] “Import third party forms into Calendly and simply build scheduling routes from visible or hidden fields — as well as Salesforce ownership st…”
   • [claimed-docs] “Report on conversion rates to see the percentage of scheduled meetings coming from Calendly, HubSpot, Marketo, or Pardot forms.”

   proof ↗⚑ flag

   SavvyCal—none0/10

   SavvyCal documents round-robin and collective team scheduling that automatically distributes meetings across team members, but there is no evidence of a routing/qualification form that asks invitees questions and branches them to different people or teams based on their answers. Missing for 10: any mention of conditional routing forms, question-based qualification logic, or answer-driven assignment to specific reps/teams.

   • [claimed-docs] “Show combined availability for your whole team and automatically route each booked meeting to the right person.”
   • [claimed-docs] “The choice is yours — randomly select who the meeting gets booked with for maximum availability or cycle through team members for equal dist…”
   • [claimed-docs] “Automatically distribute meetings across team members fairly.”
   • [claimed-docs] “Distribute meetings across a pool of organizers. Perfect for sales and customer support.”

   proof ↗⚑ flag