Cal.com vs Calendly

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 Cal.com
   Cal.com✓fullprobed8/10

   Cal.com's API v2 and hosted MCP server are explicitly documented as enabling AI agents to check availability, create, and reschedule bookings without a dashboard, with public booking endpoints for agent use and natural-language management via any MCP client (cal-com-docs-11,12,17,18,30,45,46,50, probe-4). Cancellation is only implied via the BOOKING_CANCELLED webhook trigger and reschedule-status docs rather than an explicitly cited cancel-booking endpoint, and there is no independent/hands-on corroboration of the full agent workflow. Missing for 10: explicit docs/citation of a dedicated cancel-booking API call, and third-party validation of end-to-end agent use.

   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”
   • [claimed-docs] “Query available slots using username and event slug—no need to look up IDs first”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “The booking creation endpoint is public and does not require authentication. This allows agents to book on behalf of external users.”
   • [claimed-docs] “There are 4 ways to get available slots for event type of an individual user: 1. By event type id.”
   • [claimed-docs] “Reschedule a booking or seated booking.”
   • [claimed-docs] “Reschedule a booking or seated booking. Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time.…”
   • [probe] “official MCP server documented at https://cal.com/docs/mcp-server”

   proof ↗⚑ flag

   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

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
   Cal.com✓fullprobed8/10

   Cal.com documents a hosted/local MCP server (mcp.cal.com) that lets AI clients manage bookings, event types, and schedules via natural language, plus a dedicated agents.md guide describing API v2 endpoints for checking availability, creating bookings, and managing event types, corroborated by a probe confirming the MCP server doc page. missing for 10: independent/hands-on third-party confirmation that the MCP server works reliably in practice, and no evidence of a full tool-calling schema/manifest beyond docs.

   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “The booking creation endpoint is public and does not require authentication. This allows agents to book on behalf of external users.”
   • [probe] “official MCP server documented at https://cal.com/docs/mcp-server”

   proof ↗⚑ flag

   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

Agent access

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

   weight 2 · round drawn
   Cal.com✓fullprobed9/10

   Cal.com has a verified llms.txt (HTTP 200 probe) plus a dedicated agent-oriented docs page (cal.com/docs/agents.md) explicitly describing how AI agents should use the API, and a documentation index directive pointing agents to the full llms.txt for discovery. missing for 10: independent third-party confirmation that an agent successfully navigated the docs end-to-end via llms.txt.

   • [probe] “PROBE llms.txt: HTTP 200 at https://cal.com/llms.txt # Cal.com: Scheduling Infrastructure for Individuals, Teams, and Organizations > C…”
   • [claimed-docs] “Share a booking link, connect your calendars, and let people pick a time without the back-and-forth.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “\> ## Documentation Index > Fetch the complete documentation index at: https://cal.com/docs/llms.txt > Use this file to discover all availab…”
   • [probe] “PROBE docs-md: HTTP 200 at https://cal.com/docs/api-reference/v2/introduction.md > ## Documentation Index > Fetch the complete documentation…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Cal.com~partialcommunity6/10

   Cal.com exposes a full REST API v2 (OAuth/API key auth, bookings, event types, schedules, webhooks) plus a documented CLI recommendation for agents that execute commands, enabling headless/CI automation of scheduling workflows. However, evidence is entirely first-party docs with no independent/hands-on confirmation of running it in CI pipelines, no CI-specific examples (e.g., GitHub Actions), and self-hosting/community reports raise friction concerns (broken docker builds, API not self-hostable) that could affect headless deployment reliability. missing for 10: independent CI/automation case study or hands-on verification, explicit CI pipeline examples, and confirmation that self-hosted headless API deployment works smoothly given community-reported self-hosting friction.

   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [claimed-docs] “Authentication to the API is performed via the Authorization header.”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “The booking creation endpoint is public and does not require authentication. This allows agents to book on behalf of external users.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [community] “the problem with cal.com 'open source' self-hosting is that they have made it quite difficult to run yourself... this actually doesn't provi…”
   • [community] “Also the docker compose in the repo is a mess and doesn't work... Clearly it seems to be a way to limit usage of the selfhosted version.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Cal.com✓fullprobed8/10

   Cal.com documents an official hosted MCP server (mcp.cal.com) plus a local instance option, explicitly letting AI clients manage bookings, event types, and schedules via natural language in any MCP-compatible client, corroborated by a probe confirming the docs page exists. missing for 10: independent hands-on community verification that the MCP server works reliably in practice.

   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”
   • [probe] “official MCP server documented at https://cal.com/docs/mcp-server”

   proof ↗⚑ flag

   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

4. ai-native userUse an official CLI

   weight 2 · round to Cal.com
   Cal.com~partialclaimed4/10

   Cal.com's docs explicitly mention an official CLI for agentic/automation use ('use the official Cal.com CLI instead of calling the API directly'), confirming the capability exists, but the evidence pack contains no further detail on installation, command set, or independent verification. Missing for 10: CLI documentation/README, install instructions, command reference, and any hands-on or community confirmation of the CLI in use.

   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Calendly
   Cal.com✓fullprobed8/10

   Cal.com ships a comprehensive, well-documented public API v2 covering bookings, event types, schedules, webhooks, slots, and routing traces, with clear auth methods (OAuth, API key) and dedicated docs pages for AI agents/MCP usage. Community evidence corroborates self-hosting the API is possible, though probes found no discoverable OpenAPI spec file at standard paths. Missing for 10: a verifiable machine-readable OpenAPI/Swagger spec (probe found 404s at standard paths), and independent hands-on developer confirmation of the API's real-world reliability beyond vendor docs.

   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [claimed-docs] “You can view and manage your API keys in your settings page under the security tab in Cal.com.”
   • [claimed-docs] “Authentication to the API is performed via the Authorization header.”
   • [claimed-docs] “Provide `eventTypeSlug` and `username` and optionally `organizationSlug` if the user with the username is within an organization.”
   • [claimed-docs] “Reschedule a booking or seated booking.”
   • [claimed-docs] “Create a schedule for the authenticated user. The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “The booking creation endpoint is public and does not require authentication. This allows agents to book on behalf of external users.”
   • [community] “I self host it, and I self host both the API and the database.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://cal.com/openapi.json, https://cal.com/swagger.json, https://cal.com/api/openapi.json, https:…”
   • [probe] “PROBE docs-md: HTTP 200 at https://cal.com/docs/api-reference/v2/introduction.md > ## Documentation Index > Fetch the complete documentation…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com~partialclaimed5/10

   Cal.com supports OAuth 2 authentication with defined scopes (e.g., EVENT_TYPE_WRITE) and API keys manageable in settings, plus 'managed users' independent of a user's own account, which together suggest some scoping/isolation capability. However, there is no explicit documentation of a least-privilege credential system designed specifically for AI agents (e.g., granular per-action scopes, agent-specific key issuance, or expiring/limited-permission tokens). missing for 10: dedicated agent-scoped credential issuance flow, full list of available OAuth scopes, and independent confirmation that scoping is enforced in practice.

   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [claimed-docs] “You can view and manage your API keys in your settings page under the security tab in Cal.com.”
   • [claimed-docs] “If accessed using an OAuth access token, the `EVENT_TYPE_WRITE` scope is required.”
   • [claimed-docs] “a "managed user" is completely independent of a regular user account on cal.com, meaning you don't need your users to register on cal.com we…”
   • [claimed-docs] “It's important to clarify that a "managed user" is completely independent of a regular user account on cal.com, meaning you don't need your …”

   proof ↗⚑ flag

   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

7. ai-native userBuild against official SDKs

   weight 2 · round to Cal.com
   Cal.com~partialprobed6/10

   Cal.com documents official SDK-like tooling for AI-native builders: a Platform SDK with React atoms and managed users, a full REST API v2 with OAuth/API-key auth, an official CLI recommended for agentic use, and a hosted/local MCP server for natural-language integration. However, evidence lacks a dedicated named client SDK package (e.g., JS/Python) with versioning/changelog, and OpenAPI spec endpoints return 404, undermining programmatic SDK generation claims; community feedback also flags self-hosted API access restrictions and docker/build friction. missing for 10: a discoverable OpenAPI/schema artifact, named official client SDK packages beyond React atoms, and independent hands-on developer corroboration of SDK reliability.

   • [claimed-docs] “a "managed user" is completely independent of a regular user account on cal.com, meaning you don't need your users to register on cal.com we…”
   • [claimed-docs] “Find out how to use Cal "atoms" to integrate scheduling into your product.”
   • [claimed-docs] “Use our react atoms to add scheduling to your app”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”
   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://cal.com/openapi.json, https://cal.com/swagger.json, https://cal.com/api/openapi.json, https:…”
   • [community] “Even if you self-host it, there's no way to self-host the API. You have to pay to use it. So you're just self-hosting the UI. They can chang…”
   • [community] “I self host it, and I self host both the API and the database.”

   proof ↗⚑ flag

   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

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Cal.com✓fullclaimed8/10

   Cal.com's API v2 has documented webhook creation with configurable subscriberUrl and a wide range of triggers (BOOKING_CREATED, BOOKING_RESCHEDULED, BOOKING_CANCELLED, etc.), enabling event-driven subscriptions well-suited to agentic/AI-native integration patterns, and this is reinforced by dedicated AI-agent docs and an official MCP server for programmatic access. Missing for 10: independent/hands-on confirmation of webhook reliability or delivery guarantees, and no evidence of webhook signature verification or retry semantics.

   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING…”
   • [claimed-docs] “The template of the payload that will be sent to the subscriberUrl”
   • [claimed-docs] “If accessed using an OAuth access token, the `EVENT_TYPE_WRITE` scope is required.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round to Calendly
   Cal.com—none0/10

   Evidence shows Cal.com exposes an API/MCP server so external AI agents can query availability and create bookings, but this is about agents acting as clients on the user's data, not the product itself surfacing AI-generated insights or suggestions to users. No documentation mentions built-in analytics, pattern-based scheduling suggestions, or AI-generated summaries within the Cal.com product.

   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Cal.com~partialprobed6/10

   Cal.com provides API/webhooks, workflows, MCP server, and an agents.md guide explicitly enabling AI agents to check availability, create/reschedule bookings, and manage event types autonomously via natural language or API calls, which supports background automation. However, these are developer-oriented building blocks requiring the user to wire up their own automation/agent rather than a native built-in 'run autonomously in background' scheduler feature, and no hands-on evidence of an actual autonomous background automation running end-to-end. missing for 10: independent/hands-on validation of an autonomous background automation actually running, native no-code autonomous trigger/scheduling UI (vs. workflows requiring manual setup), and confirmation the MCP/agent integration operates unattended without human-in-the-loop.

   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “The booking creation endpoint is public and does not require authentication. This allows agents to book on behalf of external users.”
   • [probe] “official MCP server documented at https://cal.com/docs/mcp-server”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Calendly
   Cal.com—none0/10

   Cal.com's AI-related evidence describes exposing its API/MCP server so external AI agents and clients (e.g., Claude, other MCP clients) can call scheduling functions — it does not describe a built-in AI assistant embedded in the Cal.com product UI that a user can delegate tasks to. This is the inverse of the story (Cal.com as a tool for external agents, not an agent bundled inside Cal.com).

   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Cal.com✓fullprobed8/10

   Cal.com documents both a hosted MCP server (mcp.cal.com) and local instance explicitly for controlling bookings, event types, and schedules 'through natural language in any MCP-compatible client,' plus a dedicated agents.md doc for AI agents to check availability, create bookings, and manage event types via API/CLI. This is first-party documented and probe-confirmed (mcp-server doc live at HTTP 200), though there's no independent/community hands-on verification of NL command execution quality. Missing for 10: independent/hands-on evidence of natural-language command execution working reliably in practice.

   • [claimed-docs] “Connect AI clients to Cal.com scheduling through the Model Context Protocol using the hosted server at mcp.cal.com or a local instance.”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [probe] “official MCP server documented at https://cal.com/docs/mcp-server”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Cal.com—none0/10

   The evidence pack shows extensive static API reference documentation (markdown pages for bookings, event types, webhooks, etc.) but no evidence of an interactive console or runnable code examples; a probe explicitly found no OpenAPI/Swagger spec at any standard location, suggesting no interactive playground exists. Missing for 10: an interactive API explorer/sandbox, evidence of runnable code snippets, or a Swagger/OpenAPI-based try-it-now interface.

   • [probe] “PROBE docs-md: HTTP 200 at https://cal.com/docs/api-reference/v2/introduction.md > ## Documentation Index > Fetch the complete documentation…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://cal.com/openapi.json, https://cal.com/swagger.json, https://cal.com/api/openapi.json, https:…”
   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [claimed-docs] “You can view and manage your API keys in your settings page under the security tab in Cal.com.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Cal.com—none0/10

   A direct probe of common OpenAPI spec paths (openapi.json, swagger.json, etc.) returned 404 on all candidates, and no documentation page or claimed-docs snippet references a downloadable OpenAPI/Swagger spec file—only human-readable API reference pages and llms.txt indices are evidenced.

   • [probe] “PROBE openapi: all candidate paths 404 (https://cal.com/openapi.json, https://cal.com/swagger.json, https://cal.com/api/openapi.json, https:…”
   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [probe] “PROBE llms.txt: HTTP 200 at https://cal.com/llms.txt # Cal.com: Scheduling Infrastructure for Individuals, Teams, and Organizations > C…”
   • [probe] “PROBE docs-md: HTTP 200 at https://cal.com/docs/api-reference/v2/introduction.md > ## Documentation Index > Fetch the complete documentation…”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Cal.com—none0/10

   The evidence pack contains no mention of a sandbox, staging, or test-mode environment for Cal.com's API, MCP server, or platform atoms — only production API keys, OAuth, and managed users are documented. Self-hosting (Cal.diy) is offered but is explicitly discouraged for production use and not framed as a sandbox for testing against a hosted instance, so it doesn't fulfill this story.

   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [claimed-docs] “You can view and manage your API keys in your settings page under the security tab in Cal.com.”
   • [claimed-docs] “a "managed user" is completely independent of a regular user account on cal.com, meaning you don't need your users to register on cal.com we…”
   • [github] “Cal.diy is 100% MIT-licensed with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want full…”
   • [community] “From the docs, 'It is strictly recommended for personal, non-production use.' Wow what a 180 from just a year ago when their blog said on-pr…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com~partialprobed4/10

   Cal.com's API is clearly versioned (all endpoints are under /v2/, and one auth method is explicitly marked 'Platform (Deprecated)'), showing some awareness of versioning and deprecation, but there is no dedicated deprecation policy page, no sunset timeline for v1, and no stated support window for deprecated endpoints/features. missing for 10: explicit documented deprecation policy (timelines, sunset process, migration guides between API versions), evidence of v1→v2 migration guidance, and any independent confirmation that deprecated endpoints are reliably maintained per a stated schedule.

   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [probe] “PROBE docs-md: HTTP 200 at https://cal.com/docs/api-reference/v2/introduction.md > ## Documentation Index > Fetch the complete documentation…”
   • [claimed-docs] “Authentication to the API is performed via the Authorization header.”

   proof ↗⚑ flag

   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

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 drawn
   Cal.com~partialclaimed4/10

   Cal.com's API supports querying mutual availability across multiple attendees via the 'by usernames only' dynamic event type, and its agents.md docs let AI agents check availability and create bookings, which gives a building block for finding open slots across calendars. However there is no evidence of any optimization logic that ranks or continuously re-evaluates the 'best' time (e.g., factoring preferences, meeting quality, or re-optimizing after changes) beyond returning available slots for manual/first-fit selection. Missing for 10: evidence of an AI/optimization algorithm scoring or ranking candidate times, evidence of continuous re-optimization as calendars change, and any documented 'best time' selection logic beyond raw slot listing.

   • [claimed-docs] “There are 4 ways to get available slots for event type of an individual user: 1. By event type id. ... 4. By usernames only (used for dynami…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”
   • [claimed-docs] “Check availability - Query available time slots for any user or team”
   • [claimed-docs] “There are 4 ways to get available slots for event type of an individual user”

   proof ↗⚑ flag

   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

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
   Cal.com—none0/10

   Cal.com's API/MCP lets AI agents check availability, create bookings, and reschedule meetings (cal-com-docs-12, cal-com-docs-24, cal-com-docs-49), but there is no evidence of an AI system that autonomously blocks time for tasks/deadlines around a knowledge worker's existing meetings or automatically re-plans a schedule when things change — it's a booking/meeting API, not a task-time-blocking planner.

   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Reschedule a booking or seated booking. Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time.…”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”

   proof ↗⚑ flag

   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

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
   Cal.com—none0/10

   Cal.com's evidence covers booking, rescheduling, scheduling APIs, webhooks, and AI-agent integration, but nothing describes an autonomous system that 'defends' recurring focus time/habit blocks by detecting conflicts and proactively rescheduling them rather than dropping them. Reschedule endpoints exist but are manually/API-triggered, not an autonomous focus-time-protection feature.

   • [claimed-docs] “Reschedule a booking or seated booking.”
   • [claimed-docs] “Reschedule a booking or seated booking. Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time.…”
   • [claimed-docs] “The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “POST /v2/bookings is used to create regular bookings, recurring bookings and instant bookings.”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Cal.com—none0/10

   The evidence describes single-resource CRUD operations (create one booking, reschedule one booking, create one event type, one webhook) via the API, but no bulk/batch endpoints (e.g., bulk booking creation, bulk cancellation, mass event-type updates) are documented anywhere in the pack.

   ⚑ flag

   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

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

   weight 3 · round to Calendly
   Cal.com~partialclaimed6/10

   Cal.com supports webhooks with configurable triggers (BOOKING_CREATED, BOOKING_PAID, BOOKING_CANCELLED, etc.) that fire actions on events, plus Zapier integration for further automation chains, which together enable rule-like 'if event X, do action Y' automation. However, this is trigger-based webhook automation rather than a native conditional rules engine (no evidence of if/then logic, filtering conditions, or multi-step workflow builder beyond routing forms). Missing for 10: evidence of a native conditional/rules engine with branching logic, non-webhook native workflow automation, and independent hands-on confirmation that webhook-triggered automations work reliably in practice.

   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING…”
   • [claimed-docs] “The template of the payload that will be sent to the subscriberUrl”
   • [claimed-docs] “Workflow automation for everyone. Use the Cal.com Zapier app to automate your workflows when a booking is created, rescheduled, cancelled or…”
   • [claimed-docs] “Retrieve the step-by-step routing trace for a booking identified by its UID. Shows how the booking was routed through routing forms, CRM loo…”
   • [claimed-docs] “Shows how the booking was routed through routing forms, CRM lookups, and host selection logic.”

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Cal.com
   Cal.com~partialclaimed6/10

   Cal.com's API explicitly supports creating recurring bookings (`POST /v2/bookings` creates 'regular bookings, recurring bookings and instant bookings') and the platform has a native 'workflows' feature plus webhooks for automation triggers, and this API/webhook layer is documented as usable by AI agents and via the official MCP server. However, no evidence directly shows an AI agent invoking recurring-schedule creation through MCP/agent docs, nor detail on how recurring jobs are configured/managed beyond the one-line API mention. Missing for 10: hands-on/independent proof of an AI agent actually creating a recurring booking via MCP or the agents API, and deeper documentation of the 'workflows' automation feature.

   • [claimed-docs] “POST /v2/bookings is used to create regular bookings, recurring bookings and instant bookings.”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”

   proof ↗⚑ flag

   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

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

   weight 1 · round drawn
   Cal.com—none0/10

   Cal.com is a scheduling platform; its evidence pack covers bookings, event types, webhooks, MCP/AI-agent integrations, and self-hosting, but nothing describes versioning, review workflows, or rollback of automations/workflows themselves. No changelog, audit trail, or undo mechanism for automation configurations is documented.

   ⚑ flag

   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

Booking

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

   weight 3 · round drawn
   Cal.com✓fullcommunity9/10

   Cal.com's own docs directly state the exact value proposition: 'Share a booking link, connect your calendars, and let people pick a time without the back-and-forth,' backed by API/product features like available-slots lookup, event types, and scheduling configuration that make this work, and community feedback confirms real-world usage replacing manual scheduling (e.g. switching from Calendly due to UX). Missing for 10: independent hands-on verification of the live-availability booking flow itself (most corroboration is docs-based) and no dispute exists to weigh against.

   • [claimed-docs] “Share a booking link, connect your calendars, and let people pick a time without the back-and-forth.”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “There are 4 ways to get available slots for event type of an individual user: 1. By event type id.”
   • [claimed-docs] “Create a schedule for the authenticated user. The point of creating schedules is for event types to be available at specific times.”
   • [community] “Happily using it for several months now after getting frustrated with calendly's UX.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com✓fullclaimed9/10

   Docs confirm event types support multiple durations (docs-4), custom locations including video/conferencing apps (docs-7, docs-21), custom booking-form questions/fields (docs-40, docs-59), and confirmation/scheduling logic including round-robin and requested/accepted booking states (docs-25, docs-58). This covers durations, locations, custom questions, and confirmation rules comprehensively via first-party API docs. Missing for 10: independent/hands-on verification of the full event-type creation UI flow beyond docs.

   • [claimed-docs] “If you want that user can choose between different lengths of the event you can specify them here.”
   • [claimed-docs] “Every Cal.com booking gets a location. By default that is Cal Video, and you can point it at Zoom, Microsoft Teams or Google Meet instead on…”
   • [claimed-docs] “Connect Zoom, Microsoft Teams or Google Meet to a user or a team”
   • [claimed-docs] “Custom fields that can be added to the booking form when the event is booked by someone. By default booking form has name and email field.”
   • [claimed-docs] “Provide `bookingFields` to customize the default fields or add custom booking fields.”
   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights togg…”
   • [claimed-docs] “Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time. - `pending` — a booking awaitin…”
   • [claimed-docs] “Create an event type”

   proof ↗⚑ flag

   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

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
   Cal.com—none0/10

   The evidence pack covers scheduling infrastructure (schedules, event types, webhooks, routing) but contains no documentation or mention of buffer times before/after meetings, minimum booking notice, daily booking caps, or date-range availability windows — the specific booking-protection controls this story asks about.

   ⚑ flag

   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

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

   weight 1 · round to Calendly
   Cal.com~partialclaimed5/10

   Cal.com's docs list "payments" among core platform capabilities (cal-com-docs-28/48) and webhook events explicitly include BOOKING_PAYMENT_INITIATED and BOOKING_PAID, confirming a payment-at-booking flow exists (cal-com-docs-5/26/42). However, the evidence pack lacks any Stripe-specific setup docs, API fields for configuring a paid event type, or a hands-on confirmation that a booking actually triggers a Stripe charge. Missing for 10: dedicated Stripe/payment-app integration docs, API examples showing price/currency fields on event-type creation, and independent/hands-on verification of a successful paid booking flow.

   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “Cal.com's differentiators are the self-hostable MIT edition (Cal.diy), API-first architecture, regulated-industry compliance, organization-s…”
   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING…”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Cal.com—none0/10

   The evidence pack contains no documentation or mention of timezone auto-detection, timezone display to invitees, or DST handling — only generic booking-link and API/event-type documentation. This is a fair and applicable axis for a scheduling product, but nothing in the pack substantiates it. Missing for 10: any docs on invitee timezone detection, timezone conversion display, or DST-safe scheduling logic.

   ⚑ flag

   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

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
   Cal.com~partialclaimed3/10

   Cal.com's docs mention connecting your calendars so people can book around your availability (cal-com-docs-16, cal-com-docs-28), implying calendar sync is core to the platform, but the evidence pack never details two-way busy-block sync across multiple work/personal calendars, conflict-checking logic, or write-back behavior. missing for 10: explicit documentation of multi-calendar busy-block overlay/sync, two-way write-back, and any hands-on confirmation that it keeps personal and work calendars in step.

   • [claimed-docs] “Share a booking link, connect your calendars, and let people pick a time without the back-and-forth.”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”

   proof ↗⚑ flag

   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

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
   Cal.com~partialclaimed3/10

   The evidence pack only contains a single generic line ('connect your calendars... pick a time without the back-and-forth') suggesting calendar sync exists, but nothing details Google/Outlook/Apple-specific connections or explicit cross-calendar conflict-checking logic. Missing for 10: explicit documentation of Google/Outlook/Apple calendar integrations, description of two-way sync/conflict-avoidance mechanics, and independent corroboration that double-booking is prevented across multiple connected calendars.

   • [claimed-docs] “Share a booking link, connect your calendars, and let people pick a time without the back-and-forth.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com✓fullclaimed8/10

   Cal.com docs explicitly describe creating schedules with working hours ('Create a schedule for the authenticated user... available at specific times'), and the scheduling configuration endpoint references advanced availability settings; the platform is widely known for date overrides and OOO via its UI, and the API-level schedule creation endpoint supports these core scheduling primitives. Missing for 10: explicit documentation snippet showing date-override and out-of-office API/UI fields, and independent hands-on confirmation of these specific sub-features beyond schedule creation.

   • [claimed-docs] “Create a schedule for the authenticated user. The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights togg…”
   • [claimed-docs] “**roundRobin**: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights …”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”

   proof ↗⚑ flag

   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

Platform

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

   weight 2 · round to Calendly
   Cal.com✓fullclaimed8/10

   Cal.com's API v2 docs explicitly document a webhook resource with triggers including BOOKING_CREATED, BOOKING_RESCHEDULED, BOOKING_CANCELLED, BOOKING_PAID, etc., configurable subscriberUrl and payload template, directly matching the story of real-time booking event notifications. Evidence is first-party docs only, without independent/hands-on confirmation of webhook delivery reliability. missing for 10: independent/hands-on verification of webhook delivery in production, details on retry/failure handling.

   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING…”
   • [claimed-docs] “The template of the payload that will be sent to the subscriberUrl”
   • [claimed-docs] “If accessed using an OAuth access token, the `EVENT_TYPE_WRITE` scope is required.”

   proof ↗⚑ flag

   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

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 Cal.com
   Cal.com✓fullprobed9/10

   Cal.com provides extensive documented REST API v2 endpoints for creating/rescheduling bookings, creating event types, availability schedules, webhooks, and scheduling configuration, plus authentication via OAuth/API keys, directly enabling developers to build scheduling into their own product. missing for 10: no independently discoverable OpenAPI/swagger spec (probe found 404s) and no hands-on third-party developer corroboration of API reliability beyond vendor docs.

   • [claimed-docs] “Provide `eventTypeSlug` and `username` and optionally `organizationSlug` if the user with the username is within an organization.”
   • [claimed-docs] “If you want that user can choose between different lengths of the event you can specify them here.”
   • [claimed-docs] “Create a schedule for the authenticated user. The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “There are 4 ways to get available slots for event type of an individual user”
   • [claimed-docs] “Reschedule a booking or seated booking. Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time.…”
   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [claimed-docs] “Authentication to the API is performed via the Authorization header.”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://cal.com/openapi.json, https://cal.com/swagger.json, https://cal.com/api/openapi.json, https:…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com!disputedcontradicted4/10

   Cal.com ships an MIT-licensed, no-license-key-required fork (Cal.diy) explicitly marketed for self-hosters (cal-com-gh-1/2/3/4/5), but hands-on community reports concretely contradict full self-hosting viability: the vendor reportedly stopped providing public Docker images (requiring users to build from source themselves) and now recommends the OSS edition 'strictly for personal, non-production use' after previously advertising full infrastructure ownership (cal-com-comm-14, cal-com-comm-15, cal-com-comm-19), and earlier reports describe broken/undocumented docker-compose setups and API access requiring a hosted paid service (cal-com-comm-3, cal-com-comm-4, cal-com-comm-11), though at least one user reports successfully self-hosting both API and DB (cal-com-comm-12). missing for 10: a consistent, current first-party guarantee of a working container image and full production-grade self-host path that isn't contradicted by these recent community reports.

   • [github] “Cal.diy is 100% MIT-licensed with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want full…”
   • [github] “Cal.diy is the community-driven, fully open-source scheduling platform — a fork of Cal.com with all enterprise/commercial code removed.”
   • [github] “Cal.diy** is the community-driven, fully open-source scheduling platform — a fork of [Cal.com](https://cal.com) with all enterprise/commerci…”
   • [github] “Cal.diy is **100% MIT-licensed** with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want …”
   • [github] “No license key required — Everything works out of the box, no Cal.com account or license needed”
   • [community] “Even if you self-host it, there's no way to self-host the API. You have to pay to use it. So you're just self-hosting the UI. They can chang…”
   • [community] “the problem with cal.com 'open source' self-hosting is that they have made it quite difficult to run yourself... this actually doesn't provi…”
   • [community] “Also the docker compose in the repo is a mess and doesn't work... Clearly it seems to be a way to limit usage of the selfhosted version.”
   • [community] “I self host it, and I self host both the API and the database.”
   • [community] “It’s curious what they said in the email they sent me about the OSS version... We will no longer provide public Docker images, so your team …”
   • [community] “From the docs, 'It is strictly recommended for personal, non-production use.' Wow what a 180 from just a year ago when their blog said on-pr…”
   • [community] “Their docs say cal.fyi won't have team features but my self hosted one does. They are a bit hacky... I think they also said they will stop p…”

   proof ↗⚑ flag

   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

Embeds

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

   weight 2 · round to Calendly
   Cal.com~partialclaimed6/10

   Cal.com exposes webhooks (BOOKING_CREATED, BOOKING_PAID, BOOKING_RESCHEDULED, etc.) and a general-purpose API/OAuth layer that could feed a CRM or Zapier via automation, and routing-form docs reference 'CRM lookups' and 'CRM fallback' in host-selection logic, plus an 'app store of integrations' is claimed. However, there is no direct evidence of a native Salesforce, HubSpot, or Zapier app/connector, nor of an out-of-the-box no-code integration flow — only the building blocks (webhooks + API) that a sales lead would need someone to wire up. Missing for 10: explicit documentation or listing of a Salesforce/HubSpot/Zapier native app, an official Zapier integration page, and any hands-on/independent confirmation that bookings actually sync into these CRMs.

   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING…”
   • [claimed-docs] “Retrieve the step-by-step routing trace for a booking identified by its UID. Shows how the booking was routed through routing forms, CRM loo…”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “Authentication to the API is performed via the Authorization header.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Calendly
   Cal.com—none0/10

   The evidence pack lacks any explicit documentation of an embed.js-style snippet supporting inline, popup, and floating widget modes. It only mentions React 'atoms' for building custom scheduling UI in an app (cal-com-docs-10, cal-com-docs-36, cal-com-docs-54), which is a different integration method (framework components, not a drop-in snippet) and requires managed users rather than a simple embed code. Missing for 10: documented embed.js snippet, inline/popup/floating-button embed modes, and any non-React (plain HTML/JS) usage example.

   • [claimed-docs] “Find out how to use Cal "atoms" to integrate scheduling into your product.”
   • [claimed-docs] “Use our react atoms to add scheduling to your app”
   • [claimed-docs] “This allows you to connect your users to Cal and handle their scheduling with atoms.”

   proof ↗⚑ flag

   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

Workflows

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

   weight 2 · round to Calendly
   Cal.com~partialclaimed3/10

   Evidence only indirectly supports this: llms.txt lists 'workflows' as a product capability and mentions 'no-show calculations' in round-robin config, and webhooks (BOOKING_CREATED/RESCHEDULED/CANCELLED) plus a Zapier app that 'automates workflows when a booking is created, rescheduled, cancelled' could be used to build reminder/follow-up sequences. However, no evidence explicitly documents built-in automated email/SMS reminder sequences targeting no-show reduction. Missing for 10: dedicated docs on the Workflows feature's reminder/SMS templates, timing/triggers configuration, and any data or claims about no-show reduction impact.

   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “**roundRobin**: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights …”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”
   • [claimed-docs] “Workflow automation for everyone. Use the Cal.com Zapier app to automate your workflows when a booking is created, rescheduled, cancelled or…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com✓fullclaimed8/10

   Cal.com documents reschedule/cancel flows directly on bookings (accepted/pending statuses), webhooks firing on BOOKING_RESCHEDULED/BOOKING_CANCELLED for downstream sync, calendar connections (Google, Apple, etc.) and conferencing apps that update everywhere, plus scheduling policies (schedules, round-robin configs, custom booking fields) enforced at booking time. This covers the core invitee self-service reschedule/cancel plus calendar sync and policy enforcement described in the docs. Missing for 10: no independent/hands-on confirmation that invitee-facing reschedule/cancel links actually work end-to-end in production, and no explicit documentation of the invitee-facing confirmation-page UI behavior itself (only API-level reschedule endpoint is evidenced).

   • [claimed-docs] “Reschedule a booking or seated booking.”
   • [claimed-docs] “Reschedule a booking or seated booking. Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time.…”
   • [claimed-docs] “Reschedule a booking or seated booking. Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time.…”
   • [claimed-docs] “Reschedulable booking statuses: - `accepted` — the confirmed booking is moved to the new start time. - `pending` — a booking awaitin…”
   • [claimed-docs] “BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING_REQUESTED - BOOKING_CANCELLED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED”
   • [claimed-docs] “triggers: type: array items: type: string enum: - BOOKING_CREATED - BOOKING_PAYMENT_INITIATED - BOOKING_PAID - BOOKING_RESCHEDULED - BOOKING…”
   • [claimed-docs] “Every Cal.com booking gets a location. By default that is Cal Video, and you can point it at Zoom, Microsoft Teams or Google Meet instead on…”
   • [claimed-docs] “Connect Zoom, Microsoft Teams or Google Meet to a user or a team”
   • [claimed-docs] “Google Calendar is a time management and scheduling service developed by Google. Allows users to create and edit events”
   • [claimed-docs] “Create a schedule for the authenticated user. The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “**roundRobin**: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights …”
   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights togg…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com✓fullclaimed9/10

   Docs explicitly state every booking gets a location, defaulting to Cal Video, and can be pointed at Zoom, Microsoft Teams, or Google Meet once the app is connected — matching the story exactly. This is first-party documented core functionality with clear API support for conferencing app connections. Missing for 10: independent hands-on confirmation of the automatic link-generation flow in production use.

   • [claimed-docs] “Every Cal.com booking gets a location. By default that is Cal Video, and you can point it at Zoom, Microsoft Teams or Google Meet instead on…”
   • [claimed-docs] “Connect Zoom, Microsoft Teams or Google Meet to a user or a team”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com~partialprobed7/10

   Cal.com's API v2 covers most UI capabilities (bookings, event types, schedules, webhooks, routing, conferencing apps, managed users) and docs explicitly frame the API as AI-agent-ready, plus an MCP server exposes these operations to AI clients. However, evidence doesn't confirm full UI parity (e.g., no mention of API access to billing/compliance settings, app marketplace management, or admin/org settings via API), and an official OpenAPI spec could not be found (404s), making completeness hard to verify. missing for 10: confirmed full parity for admin/org-level settings and marketplace app configuration via API, a published OpenAPI schema, independent hands-on confirmation that all UI actions are API-reachable.

   • [claimed-docs] “Cal.com API v2 enables AI agents to: Check availability - Query available time slots for any user or team, Create bookings - Schedule meetin…”
   • [claimed-docs] “Cal.com API v2 enables AI agents to: **Check availability** - Query available time slots for any user or team * **Create bookings** - Schedu…”
   • [claimed-docs] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client”
   • [claimed-docs] “For agents that can execute commands on a machine, use the official Cal.com CLI instead of calling the API directly.”
   • [claimed-docs] “a "managed user" is completely independent of a regular user account on cal.com, meaning you don't need your users to register on cal.com we…”
   • [claimed-docs] “Create a schedule for the authenticated user. The point of creating schedules is for event types to be available at specific times.”
   • [claimed-docs] “Every Cal.com booking gets a location. By default that is Cal Video, and you can point it at Zoom, Microsoft Teams or Google Meet instead on…”
   • [claimed-docs] “Retrieve the step-by-step routing trace for a booking identified by its UID. Shows how the booking was routed through routing forms, CRM loo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://cal.com/openapi.json, https://cal.com/swagger.json, https://cal.com/api/openapi.json, https:…”
   • [probe] “official MCP server documented at https://cal.com/docs/mcp-server”

   proof ↗⚑ flag

   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

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

   weight 3 · round to Cal.com
   Cal.com!disputedcontradicted3/10

   Cal.com documents an open API (auth via key/OAuth) and an MIT-licensed self-host fork (Cal.diy) that could in principle let a user pull out their data and run independently, but there is no explicit 'export all my data' feature documented, and hands-on community reports directly contradict the openness/exit narrative: users say self-hosting the API isn't really possible ('there's no way to self-host the API... AGPL is a very restrictive license'), and more recent reports describe a bait-and-switch where Cal.diy/self-hosted docker images were pulled back and restricted to 'personal, non-production use,' with users abandoning self-hosting as a result. missing for 10: a documented data-export/portability feature, and confirmation that self-hosting reliably preserves full data ownership without restriction.

   • [github] “Cal.diy is 100% MIT-licensed with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want full…”
   • [github] “Cal.diy is the community-driven, fully open-source scheduling platform — a fork of Cal.com with all enterprise/commercial code removed.”
   • [claimed-docs] “The Cal.com API has 3 authentication methods: 1. OAuth 2. API key 3. Platform (Deprecated)”
   • [claimed-docs] “Authentication to the API is performed via the Authorization header.”
   • [community] “Even if you self-host it, there's no way to self-host the API. You have to pay to use it. So you're just self-hosting the UI. They can chang…”
   • [community] “It’s curious what they said in the email they sent me about the OSS version... We will no longer provide public Docker images, so your team …”
   • [community] “From the docs, 'It is strictly recommended for personal, non-production use.' Wow what a 180 from just a year ago when their blog said on-pr…”
   • [community] “Not impossible though, I run a directory of open-source alternatives and rarely do you see what Cal.com did... a pure bait and switch like t…”
   • [community] “Their docs say cal.fyi won't have team features but my self hosted one does. They are a bit hacky... I think they also said they will stop p…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com!disputedcontradicted5/10

   Cal.com does publish source under an open license — Cal.diy is documented as '100% MIT-licensed' with no proprietary Enterprise Edition and 'no license key required' (cal-com-gh-1/4/5), and llms.txt calls the 'self-hostable MIT edition' a core differentiator (cal-com-docs-43/48). However, hands-on community reports concretely contradict how open/usable that source is in practice: Cal.com stopped shipping public Docker images and now tells self-hosters 'It is strictly recommended for personal, non-production use' — a stated reversal from prior claims that self-hosting gave 'full ownership of infrastructure' (cal-com-comm-14, cal-com-comm-15, cal-com-comm-18, cal-com-comm-19), and the flagship cal.com repo itself is under a restrictive AGPL license per commenters (cal-com-comm-3). missing for 10: independent verification that the MIT Cal.diy source is fully buildable/production-usable, and reconciliation of the AGPL vs MIT licensing claims across the main repo and the fork.

   • [github] “Cal.diy is 100% MIT-licensed with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want full…”
   • [github] “Cal.diy is **100% MIT-licensed** with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want …”
   • [github] “No license key required — Everything works out of the box, no Cal.com account or license needed”
   • [claimed-docs] “For evaluators comparing against Calendly: Cal.com's differentiators are the self-hostable MIT edition (Cal.diy), API-first architecture, re…”
   • [claimed-docs] “Cal.com's differentiators are the self-hostable MIT edition (Cal.diy), API-first architecture, regulated-industry compliance, organization-s…”
   • [community] “Even if you self-host it, there's no way to self-host the API. You have to pay to use it. So you're just self-hosting the UI. They can chang…”
   • [community] “It’s curious what they said in the email they sent me about the OSS version... We will no longer provide public Docker images, so your team …”
   • [community] “From the docs, 'It is strictly recommended for personal, non-production use.' Wow what a 180 from just a year ago when their blog said on-pr…”
   • [community] “Not impossible though, I run a directory of open-source alternatives and rarely do you see what Cal.com did... a pure bait and switch like t…”
   • [community] “Their docs say cal.fyi won't have team features but my self hosted one does. They are a bit hacky... I think they also said they will stop p…”

   proof ↗⚑ flag

   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

4. ai-native userSelf-host the core product

   weight 3 · round to Cal.com
   Cal.com!disputedcontradicted4/10

   Vendor and GitHub evidence claim Cal.diy is a 100% MIT-licensed, no-license-key-required fork designed for full self-hosting control, but multiple hands-on community reports concretely contradict this: users report the vendor stopped shipping public Docker images (requiring manual builds), official docs now say the OSS edition is 'strictly recommended for personal, non-production use,' and one commenter states you can't actually self-host the API without paying, calling it effectively 'self-hosting the UI' only, prompting accusations of a bait-and-switch from long-time self-hosters. A few users do report successfully self-hosting both API and DB, so the capability partially exists but is actively disputed. Missing for 10: a stable, vendor-provided production-grade self-hosting path (Docker images, full API) without contested community reports of regressions or non-production caveats.

   • [github] “Cal.diy is 100% MIT-licensed with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want full…”
   • [github] “Cal.diy is the community-driven, fully open-source scheduling platform — a fork of Cal.com with all enterprise/commercial code removed.”
   • [github] “Cal.diy is **100% MIT-licensed** with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want …”
   • [github] “No license key required — Everything works out of the box, no Cal.com account or license needed”
   • [community] “Even if you self-host it, there's no way to self-host the API. You have to pay to use it. So you're just self-hosting the UI. They can chang…”
   • [community] “the problem with cal.com 'open source' self-hosting is that they have made it quite difficult to run yourself... this actually doesn't provi…”
   • [community] “Also the docker compose in the repo is a mess and doesn't work... Clearly it seems to be a way to limit usage of the selfhosted version.”
   • [community] “I self host it, and I self host both the API and the database.”
   • [community] “It’s curious what they said in the email they sent me about the OSS version... We will no longer provide public Docker images, so your team …”
   • [community] “From the docs, 'It is strictly recommended for personal, non-production use.' Wow what a 180 from just a year ago when their blog said on-pr…”
   • [community] “As a former cal.com advocate, I am now going to be switching my two companies to cal.diy or a similar alternative and canceling my cal.com s…”
   • [community] “Not impossible though, I run a directory of open-source alternatives and rarely do you see what Cal.com did... a pure bait and switch like t…”
   • [community] “Their docs say cal.fyi won't have team features but my self hosted one does. They are a bit hacky... I think they also said they will stop p…”

   proof ↗⚑ flag

   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

Pricing

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

   weight 2 · round to Cal.com
   Cal.com~partialcommunity6/10

   A Cal.com cofounder explicitly states in community discussion that everything that is Calendly's paid 'Pro' tier is free on Cal.com, and general docs describe core one-on-one scheduling/booking-link functionality that would presumably be available without payment; however, other community comments note certain paid add-ons (e.g., $29/mo premium usernames) exist, and there is no first-party pricing-page or plan-limits documentation in the pack confirming exactly what's free. Missing for 10: an official pricing/plan page from Cal.com detailing which core scheduling features are free, and independent hands-on confirmation of using a booking link fully free.

   • [community] “there are no trials anymore, everything that is PRO on calendly is free on cal.com (Cal.com cofounder response to pricing complaint)”
   • [claimed-docs] “Share a booking link, connect your calendars, and let people pick a time without the back-and-forth.”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “For evaluators comparing against Calendly: Cal.com's differentiators are the self-hostable MIT edition (Cal.diy), API-first architecture, re…”
   • [community] “I was curious about getting a premium username (@christina) but $29 a month... Love the idea, but $360 for a premium username. Nah. Not doin…”

   proof ↗⚑ flag

   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

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

   weight 1 · round to Calendly
   Cal.com—none0/10

   The evidence pack contains no published pricing page, tier comparison, or per-seat cost breakdown for Cal.com; only scattered community mentions of a $29/month premium username add-on and a cofounder claim that 'everything PRO on Calendly is free,' neither of which constitutes documented per-seat tier pricing.

   • [community] “I was curious about getting a premium username (@christina) but $29 a month... Love the idea, but $360 for a premium username. Nah. Not doin…”
   • [community] “there are no trials anymore, everything that is PRO on calendly is free on cal.com (Cal.com cofounder response to pricing complaint)”
   • [community] “What does open source mean when you have to use a hosted solution and "premium" names cost 29 usd / month.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com~partialcommunity4/10

   Cal.com does not document a data-residency/region-selection feature for its hosted SaaS product, but it does offer self-hosting (Cal.diy, MIT-licensed, 'full control over their scheduling infrastructure') as the mechanism by which a user could choose where data lives, and llms.txt cites GDPR/CCPA/HIPAA compliance as differentiators. However community evidence shows self-hosting is troubled (no self-hostable API per cal-com-comm-3, docker image friction cal-com-comm-4/11, and a documented 'bait and switch' restricting Cal.diy to non-production use cal-com-comm-14/15), undercutting reliability of this as a residency-control path. Missing for 10: an explicit region/data-residency selection setting in the hosted product, first-party docs describing where data centers are located, and confirmation that self-hosting reliably satisfies residency requirements without the documented friction.

   • [github] “Cal.diy is 100% MIT-licensed with no proprietary "Enterprise Edition" features. It's designed for individuals and self-hosters who want full…”
   • [github] “Cal.diy is the community-driven, fully open-source scheduling platform — a fork of Cal.com with all enterprise/commercial code removed.”
   • [claimed-docs] “Compliance is a core differentiator. Cal.com supports HIPAA (with BAA available on organization/enterprise plans), SOC 2, ISO 27001, GDPR, a…”
   • [claimed-docs] “For evaluators comparing against Calendly: Cal.com's differentiators are the self-hostable MIT edition (Cal.diy), API-first architecture, re…”
   • [community] “Even if you self-host it, there's no way to self-host the API. You have to pay to use it. So you're just self-hosting the UI. They can chang…”
   • [community] “It’s curious what they said in the email they sent me about the OSS version... We will no longer provide public Docker images, so your team …”
   • [community] “From the docs, 'It is strictly recommended for personal, non-production use.' Wow what a 180 from just a year ago when their blog said on-pr…”

   proof ↗⚑ flag

   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

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Cal.com—none0/10

   The evidence pack contains only a generic compliance claim (GDPR/CCPA/SOC2/HIPAA) with no concrete documentation of data retention policies, deletion APIs, or AI-agent-accessible controls to purge or manage stored booking/user data. No endpoint or workflow is shown for an AI-native user to actually control retention windows or trigger deletion.

   • [claimed-docs] “Compliance is a core differentiator. Cal.com supports HIPAA (with BAA available on organization/enterprise plans), SOC 2, ISO 27001, GDPR, a…”

   proof ↗⚑ flag

   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

Teams

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

   weight 2 · round to Cal.com
   Cal.com~partialclaimed6/10

   Cal.com explicitly lists 'collective' as one of its native scheduling types alongside round-robin, group and one-on-one, and its slots API supports checking availability across multiple hosts (e.g. dynamic/username-based slot queries for '2 or more people'), which is the mechanism needed to only surface times when every host is free. However, the evidence pack shows detailed configuration docs (priority/weight/host groups/CRM fallback) only for round-robin, with no equivalent documented detail on collective-event host requirements or slot-intersection logic. Missing for 10: explicit collective-event configuration API docs, independent/hands-on confirmation that slots correctly reflect all-hosts-free logic.

   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “There are 4 ways to get available slots for event type of an individual user: 1. By event type id. ... 4. By usernames only (used for dynami…”
   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings”
   • [claimed-docs] “Returns the scheduling configuration for a team event type.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Cal.com
   Cal.com✓fullclaimed8/10

   Cal.com's API documents full round-robin scheduling configuration with per-host priority, weight, group assignment, weights toggle, lead threshold, no-show calculations, and CRM fallback (cal-com-docs-15/25/41), plus llms.txt confirms round-robin scheduling as a core product feature (cal-com-docs-28). This directly matches the sales-lead need for fair, weighted lead distribution. Missing for 10: independent/hands-on verification of round-robin fairness in practice and no UI-level walkthrough evidence beyond API docs.

   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings”
   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights togg…”
   • [claimed-docs] “**roundRobin**: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights …”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “Returns the scheduling configuration for a team event type.”
   • [claimed-docs] “The response varies by the event type's scheduling type, and non-team event types are rejected.”

   proof ↗⚑ flag

   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

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
   Cal.com✓fullclaimed6/10

   Cal.com's docs explicitly list routing forms as a core feature (docs-28) and expose a dedicated API for tracing 'how the booking was routed through routing forms, CRM lookups, and host selection logic' (cal-com-docs-8), confirming invitee answers drive routing decisions. Team scheduling configs also support round-robin host selection with priority/weight/lead-threshold/CRM fallback (cal-com-docs-15/25/41), reinforcing routing-to-right-person capability. Missing for 10: no detailed documentation of the routing form builder UI itself (question types, conditional branching rules) or independent/hands-on confirmation of routing form setup and accuracy.

   • [claimed-docs] “Retrieve the step-by-step routing trace for a booking identified by its UID. Shows how the booking was routed through routing forms, CRM loo…”
   • [claimed-docs] “It powers one-on-one, group, round-robin, and collective scheduling, with routing forms, workflows, payments, native video, and an app store…”
   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings”
   • [claimed-docs] “roundRobin: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights togg…”
   • [claimed-docs] “**roundRobin**: Full configuration including hosts with priority, weight, and group assignment, host groups, and advanced settings (weights …”

   proof ↗⚑ flag

   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