Cal.com vs Reclaim.ai
Cal.com
Cal.com, Inc.
Cal.com wins · 33–9 (9 drawn)
Agent scheduling — stories about agent scheduling in this arenaAgent scheduling
Stories about agent scheduling in this arena
Agent ops
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.comCal.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”
Reclaim.ainone0/10No evidence of a public API or MCP server for programmatic booking/rescheduling/cancellation; the product only documents dashboard, browser extension, and in-app AI assistant features. Probes for an OpenAPI spec returned 404s, and no API/MCP docs appear anywhere in the evidence pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
- [claimed-docs] “Chat with your AI Assistant to plan, prioritize, and optimize your schedule.”
- [claimed-docs] “The Schedule Assistant acts as your control center. It highlights what needs attention and suggests what to do nex”
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 Cal.comCal.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”
Reclaim.ainone0/10No evidence of an MCP server, tool-calling API, or agent-facing surface exposing availability/bookings/event types; probes for OpenAPI/spec endpoints returned 404s, and the AI Assistant feature is a chat UI for the human user, not an agent tool interface.
- [claimed-docs] “Chat with your AI Assistant to plan, prioritize, and optimize your schedule.”
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
- [probe] “PROBE docs-md: HTTP 404 at https://help.reclaim.ai/en/.md”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Cal.comCal.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…”
A direct probe confirms Reclaim's help center serves a live llms.txt at https://help.reclaim.ai/llms.txt returning HTTP 200 with structured markdown links to docs, directly satisfying the story's core ask. Missing for 10: no per-page .md docs variant (404 on docs-md probe) and no independent community confirmation of agents actually consuming the llms.txt file.
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10Reclaim.ai is a calendar-scheduling SaaS with a web/app UI and integrations, but there is no evidence of a CLI, headless mode, or CI/automation runner; probes for API/OpenAPI specs all returned 404s.
ai-native userConnect an agent via an official MCP server
weight 3 · round to Cal.comCal.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”
Reclaim.ainone0/10Reclaim.ai is a scheduling/calendar automation product, not an AI agent/assistant itself, so an official MCP server is a plausible ecosystem integration; however, no evidence in the pack shows any MCP server, API for agent connectivity, or related integration—only calendar/scheduling features and a failed OpenAPI probe.
ai-native userUse an official CLI
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10No evidence of an official CLI for Reclaim.ai; the product surfaces are calendar integrations, web app, Slack/Google add-ons, and chat AI assistant, with no mention of a command-line interface. missing for 10: any documentation or reference to a CLI tool, CLI installation instructions, or CLI-based automation.
ai-native userDrive the product through a documented public API
weight 3 · round to Cal.comCal.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…”
Reclaim.ainone0/10No evidence of a documented public API for Reclaim.ai — the evidence pack only shows product feature docs and community discussion of the scheduling app, and explicit probes for OpenAPI/swagger endpoints all returned 404s.
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to Cal.comCal.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 …”
Reclaim.ainone0/10No evidence of scoped or least-privilege API credential issuance for agents; the OpenAPI probe returned 404s and no docs mention API keys, tokens, or permission scoping. This is a fair question for an AI-native scheduling product with integrations, so it applies but is unmet.
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
ai-native userBuild against official SDKs
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10No evidence of an official SDK for developers to build against; probes for OpenAPI/API specs all returned 404, and all docs reference end-user scheduling features, not developer SDKs.
ai-native userSubscribe to events via webhooks
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10No evidence of a webhooks/event subscription API; probes for OpenAPI/schema endpoints all returned 404, and no docs mention webhooks at all.
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to Reclaim.aiCal.comnone0/10Evidence 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.”
Reclaim documents an AI Assistant chat for planning/prioritizing/optimizing schedules, a Schedule Assistant that 'highlights what needs attention and suggests what to do next', and automatic time analytics across meetings/tasks/work-life balance — all AI-generated insights derived from the user's calendar data inside the product. Missing for 10: independent/hands-on corroboration of the insight quality, and more detail on the analytics/insights UI beyond marketing copy.
- [claimed-docs] “Chat with your AI Assistant to plan, prioritize, and optimize your schedule.”
- [claimed-docs] “The Schedule Assistant acts as your control center. It highlights what needs attention and suggests what to do nex”
- [claimed-docs] “Analyze your time across meetings, tasks, & work-life balance metrics.”
- [claimed-docs] “Reclaim automatically categorizes your events by type in order to perform several important jobs: To automatically sync your status in Slack…”
- [claimed-docs] “Set the priority level for your Habits, Tasks, Smart Meetings, Scheduling Links, and even Google Calendar or Outlook Calendar events from Cr…”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnCal.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”
Reclaim.ai runs continuous background automations—auto-scheduling/rescheduling Tasks, Habits, Focus Time, buffers, and travel time without manual reshuffling—which is a real form of autonomous, persistent automation, and community testimonials corroborate this behavior (e.g., proactive scheduling, hands-off operation). However, this is calendar-domain automation rather than general-purpose 'agentic' automation across arbitrary tasks/tools, and at least one user reported a sync automation not working as expected. missing for 10: evidence of broader/cross-domain autonomous automations beyond calendar scheduling, a clear framework for user-defined custom automations/triggers, and stronger independent verification of reliability at scale.
- [claimed-docs] “Reclaim automatically schedules and reschedules events on your calendar, so you don't have to manually adjust your calendar when conflicts c…”
- [claimed-docs] “Focus Time lets you set a weekly focus goal for heads-down work — and uses AI to flexibly defend the time you need to get things done.”
- [claimed-docs] “Reclaim automatically reschedules it to the next best time. No reshuffling required.”
- [claimed-docs] “Reclaim can automatically add smart buffers between events to ensure you have time to travel, take a break, or chunk up your Task and Habit …”
- [claimed-docs] “Set the priority level for your Habits, Tasks, Smart Meetings, Scheduling Links, and even Google Calendar or Outlook Calendar events from Cr…”
- [community] “Huge fan of Reclaim! ...With Reclaim I'm able to 'trick' myself by having the bot add proactive things to my calendar that I want to do, but…”
- [community] “It didn't worked for me. I've signed up, i have the events created by Reclaim in my calendar, but if I invite myself from another account, n…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to Reclaim.aiCal.comnone0/10Cal.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.”
Reclaim ships a built-in AI Assistant chat feature that lets users delegate planning, prioritizing, and schedule optimization tasks, plus a 'Schedule Assistant' control center that surfaces suggested actions and lets users preview/deploy changes. This matches the story of delegating tasks to an in-product AI assistant. Missing for 10: independent/hands-on user reports specifically about the chat AI Assistant (community evidence predates this feature and focuses on general auto-scheduling), and detail on the full scope of tasks it can autonomously execute versus merely suggest.
- [claimed-docs] “Chat with your AI Assistant to plan, prioritize, and optimize your schedule.”
- [claimed-docs] “The Schedule Assistant acts as your control center. It highlights what needs attention and suggests what to do nex”
- [claimed-docs] “Preview changes in your calendar before deploying them”
ai-native userOperate the product with natural-language commands
weight 2 · round to Cal.comCal.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”
Reclaim advertises an 'AI Assistant' chat interface for planning, prioritizing, and optimizing your schedule, and a 2.0 'Schedule Assistant' that suggests actions — both implying natural-language interaction. However, there's no detailed documentation of command scope, examples of actual NL commands, or independent/hands-on evidence confirming this works reliably as a command interface. Missing for 10: independent corroboration of the AI Assistant's natural-language capabilities, detailed command examples/scope, and hands-on user reports validating it in practice.
- [claimed-docs] “Chat with your AI Assistant to plan, prioritize, and optimize your schedule.”
- [claimed-docs] “The Schedule Assistant acts as your control center. It highlights what needs attention and suggests what to do nex”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnCal.comnone0/10The 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.”
Reclaim.ainone0/10No evidence of an interactive API reference or runnable examples; probes for OpenAPI/swagger specs all returned 404, and no docs mention a developer API console.
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnCal.comnone0/10A 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…”
Reclaim.ainone0/10The probe explicitly checked common OpenAPI/swagger spec paths and all returned 404, and no documentation mentions a downloadable machine-readable API spec; only an llms.txt for docs is present.
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://help.reclaim.ai/llms.txt # Reclaim.ai Help Center > Reclaim.ai Help Center ## Get started with Reclaim…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10No evidence of any versioned API or documented deprecation policy; OpenAPI probes returned 404s and no API documentation appears anywhere in the evidence pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
Ai scheduling — stories about ai scheduling in this arenaAi scheduling
Stories about ai scheduling in this arena
Ai calendar
knowledge workerAI finds and continuously optimizes the best meeting time across all attendees' calendars, not just the first open slot
weight 1 · round to Reclaim.aiCal.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”
Reclaim explicitly markets Smart Meetings as finding the best time across all attendees' schedules, and documents automatic rescheduling of lower-priority events to make room for higher-priority meetings, with priority-based continuous optimization applied across the calendar. Community feedback corroborates the automatic scheduling behavior (throttling, control over free/busy) though one user notes syncing hiccups. Missing for 10: independent hands-on verification specifically of multi-attendee optimization accuracy/quality and no detailed technical explanation of the algorithm across multiple external calendars.
- [claimed-docs] “Find the best time to meet across all attendees' schedules.”
- [claimed-docs] “If a meeting overbooks another lower-priority smart event, Reclaim automatically reschedules it to the next best time. No reshuffling requir…”
- [claimed-docs] “Set the priority level for your Habits, Tasks, Smart Meetings, Scheduling Links, and even Google Calendar or Outlook Calendar events from Cr…”
- [claimed-docs] “Reclaim automatically schedules and reschedules events on your calendar, so you don't have to manually adjust your calendar when conflicts c…”
- [claimed-docs] “automatically offer up lower-priority events scheduled on your calendar (both other Reclaim smart events, as well as non-Reclaim created eve…”
- [community] “Our Habits feature has a lot more control... the throttling of free/busy time... makes things much better for manager-type personas who need…”
knowledge workerAI schedules my tasks into real calendar blocks around meetings and deadlines, and re-plans automatically when things change
weight 2 · round to Reclaim.aiCal.comnone0/10Cal.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…”
Reclaim's core product explicitly auto-schedules Tasks/Habits into calendar blocks around meetings and deadlines using priority levels, and automatically reschedules events when conflicts arise without manual reshuffling (reclaim-docs-7, -32, -33, -34, -29, -12). Community users corroborate this in practice, describing it as reserving time and reducing manual calendar management (reclaim-comm-3, reclaim-comm-4, reclaim-comm-10, reclaim-comm-9), with one user reporting a specific self-invite scenario that didn't trigger rescheduling (reclaim-comm-5). Missing for 10: independent quantitative benchmarks of re-planning reliability and broader third-party testing beyond a few anecdotal community posts.
- [claimed-docs] “Flexibly schedule your tasks in your calendar.”
- [claimed-docs] “Automate the perfect daily plan & manage your smart events.”
- [claimed-docs] “Automatically block flexible time for your Tasks before due dates around everything else you have going on, break up longer projects into ma…”
- [claimed-docs] “Set the priority level for your Habits, Tasks, Smart Meetings, Scheduling Links, and even Google Calendar or Outlook Calendar events from Cr…”
- [claimed-docs] “Reclaim automatically schedules and reschedules events on your calendar, so you don't have to manually adjust your calendar when conflicts c…”
- [claimed-docs] “Reclaim automatically reschedules it to the next best time. No reshuffling required.”
- [claimed-docs] “If a meeting overbooks another lower-priority smart event, Reclaim automatically reschedules it to the next best time. No reshuffling requir…”
- [claimed-docs] “When you reschedule an event by dragging it elsewhere in the calendar, it will automatically be "locked" and get a 🔒 emoji in the title.”
- [community] “Huge fan of Reclaim! ...With Reclaim I'm able to 'trick' myself by having the bot add proactive things to my calendar that I want to do, but…”
- [community] “I second this (Reclaim beta user here) - Reclaim makes me think about my time more, but drag appointment boxes around less.”
- [community] “Reclaim.ai has been an incredibly valuable tool for me and my work... I love Reclaim right now, it serves its purpose very well and stays co…”
- [community] “I've been using this new feature on reclaim and it's been awesome helping me reserve time to keep my commitments and not letting meetings ta…”
- [community] “It didn't worked for me. I've signed up, i have the events created by Reclaim in my calendar, but if I invite myself from another account, n…”
knowledge workerThe product auto-defends recurring focus time and habits, flexibly moving them when conflicts appear instead of dropping them
weight 2 · round to Reclaim.aiCal.comnone0/10Cal.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.”
Reclaim's core Focus Time and Habits features are explicitly documented as AI-defended blocks that flex/reschedule around conflicts rather than being dropped (reclaim-docs-1, reclaim-docs-30, reclaim-docs-31, reclaim-docs-34), reinforced by priority-based auto-scheduling (reclaim-docs-33) and locking behavior. Community testimonials corroborate real-world use of habit/commitment defense (reclaim-comm-1, reclaim-comm-3, reclaim-comm-10). Missing for 10: independent long-term reliability data or edge-case testing showing how conflicts are resolved in practice beyond vendor docs and a few anecdotes.
- [claimed-docs] “Set a Focus Time goal, and let AI defend time to get stuff done.”
- [claimed-docs] “Focus Time lets you set a weekly focus goal for heads-down work — and uses AI to flexibly defend the time you need to get things done.”
- [claimed-docs] “Habits flex around your schedule and adapt as things come up, giving you the time you need without being overly rigid and jamming up your ca…”
- [claimed-docs] “Set the priority level for your Habits, Tasks, Smart Meetings, Scheduling Links, and even Google Calendar or Outlook Calendar events from Cr…”
- [claimed-docs] “Reclaim automatically schedules and reschedules events on your calendar, so you don't have to manually adjust your calendar when conflicts c…”
- [community] “Our Habits feature has a lot more control... the throttling of free/busy time... makes things much better for manager-type personas who need…”
- [community] “Huge fan of Reclaim! ...With Reclaim I'm able to 'trick' myself by having the bot add proactive things to my calendar that I want to do, but…”
- [community] “I've been using this new feature on reclaim and it's been awesome helping me reserve time to keep my commitments and not letting meetings ta…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnCal.comnone0/10The 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.
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Cal.comCal.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.”
Reclaim ships several built-in automated behaviors that resemble simple rule-trigger-action patterns — e.g. hashtags like #reclaim_free, #reclaim_busy, #needs_travel that change scheduling behavior on tagged events, priority levels (P1-P4) that drive auto-scheduling decisions, and automatic buffer/travel-time insertion and rescheduling on conflicts. However, these are fixed, product-defined automations rather than a general-purpose rule engine where an AI-native user can define arbitrary custom triggers and actions across event types. Missing for 10: a documented user-configurable rule/trigger-action builder (e.g. 'if event has property X, do Y'), support for custom event-based automations beyond the handful of built-in hashtags/priorities, and any API/webhook-based automation hooks.
- [claimed-docs] “Set the priority level for your Habits, Tasks, Smart Meetings, Scheduling Links, and even Google Calendar or Outlook Calendar events from Cr…”
- [claimed-docs] “Reclaim automatically schedules and reschedules events on your calendar, so you don't have to manually adjust your calendar when conflicts c…”
- [claimed-docs] “you can set a smart No-Meeting Day using the hashtag #reclaim_free. Reclaim will mark the day as busy for new meeting invitations, but keep …”
- [claimed-docs] “add the hashtag #reclaim_busy to it. This will tell Reclaim's scheduler to treat that time as busy, despite it being marked as free.”
- [claimed-docs] “If you want to add travel time to an event that Reclaim has failed to add travel time automatically, simply add the hashtag #needs_travel to…”
- [claimed-docs] “Reclaim can automatically add smart buffers between events to ensure you have time to travel, take a break, or chunk up your Task and Habit …”
- [claimed-docs] “When you reschedule an event by dragging it elsewhere in the calendar, it will automatically be "locked" and get a 🔒 emoji in the title.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnCal.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”
Reclaim's Habits and recurring Tasks features let users define recurring routines that the AI auto-schedules and re-flexes around the calendar week over week, and priorities/auto-rescheduling keep them running without manual intervention (reclaim-docs-4, reclaim-docs-31, reclaim-docs-33, reclaim-docs-34), with community confirmation that Habits offer real control for recurring commitments (reclaim-comm-1, reclaim-comm-10). However this is calendar-event recurrence, not general 'workflow' automation (e.g., multi-step or cross-tool automated jobs) — missing for 10: evidence of broader workflow/automation beyond calendar-based recurring tasks, and any API/triggered job scheduling for developers.
- [claimed-docs] “Find the best times for your recurring routines.”
- [claimed-docs] “Habits flex around your schedule and adapt as things come up, giving you the time you need without being overly rigid and jamming up your ca…”
- [claimed-docs] “Set the priority level for your Habits, Tasks, Smart Meetings, Scheduling Links, and even Google Calendar or Outlook Calendar events from Cr…”
- [claimed-docs] “Reclaim automatically schedules and reschedules events on your calendar, so you don't have to manually adjust your calendar when conflicts c…”
- [community] “Our Habits feature has a lot more control... the throttling of free/busy time... makes things much better for manager-type personas who need…”
- [community] “I've been using this new feature on reclaim and it's been awesome helping me reserve time to keep my commitments and not letting meetings ta…”
ai-native userVersion, review, and roll back my automations
weight 1 · round to Reclaim.aiCal.comnone0/10Cal.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.
Reclaim's 2.0 Schedule Assistant lets users 'preview changes in your calendar before deploying them' (docs-52), which offers a thin form of review before automation changes are applied, and locking events (docs-37, docs-41) provides a manual override, but there is no evidence of true automation versioning, change history, or a rollback mechanism for scheduling rules/priorities themselves. Missing for 10: version history of automation rules, ability to roll back to a prior automation configuration, audit trail of automated schedule changes.
- [claimed-docs] “Preview changes in your calendar before deploying them”
- [claimed-docs] “When you reschedule an event by dragging it elsewhere in the calendar, it will automatically be "locked" and get a 🔒 emoji in the title.”
- [claimed-docs] “By default, Reclaim will automatically lock your Smart Meetings at 4am in your local timezone at the beginning of the day so that they don't…”
Booking links — stories about booking links in this arenaBooking links
Stories about booking links in this arena
Booking
founderShare a booking link where invitees pick a time from my live availability — no back-and-forth email
weight 3 · round to Cal.comCal.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.”
Reclaim's Scheduling Links feature is directly documented as sharing availability so invitees can book from live calendar data across one or many calendars, with automatic conflict-avoidance and rescheduling of lower-priority events to keep availability accurate (reclaim-docs-2, reclaim-docs-49, reclaim-docs-17, reclaim-docs-29, reclaim-docs-23, reclaim-docs-35). This matches the founder story of a self-serve booking link replacing email back-and-forth. Missing for 10: independent/hands-on user confirmation specifically of the booking-link flow (community evidence covers other Reclaim features, not scheduling links directly) and no evidence on booking page customization/embedding.
- [claimed-docs] “Share your availability using smart meeting controls.”
- [claimed-docs] “Scheduling Links enable you to send links to you and your team's availability, allowing others to book time across one, or many, calendars.”
- [claimed-docs] “automatically offer up lower-priority events scheduled on your calendar (both other Reclaim smart events, as well as non-Reclaim created eve…”
- [claimed-docs] “If a meeting overbooks another lower-priority smart event, Reclaim automatically reschedules it to the next best time. No reshuffling requir…”
- [claimed-docs] “a powerful way to make sure people who go to book time with you always see your true availability across multiple calendars”
- [claimed-docs] “Free events are shown as available times to others when they book time with you.”
founderOffer multiple event types with their own durations, locations, custom questions, and confirmation rules
weight 2 · round to Cal.comDocs 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”
Reclaim.ainone0/10Reclaim's Scheduling Links docs describe sharing availability and smart rescheduling around priorities, but nothing in the evidence pack describes creating multiple distinct event types each with their own duration, location, custom questions, or confirmation rules — the core of this story.
- [claimed-docs] “Share your availability using smart meeting controls.”
- [claimed-docs] “Reclaim automatically reschedules it to the next best time. No reshuffling required.”
- [claimed-docs] “automatically offer up lower-priority events scheduled on your calendar (both other Reclaim smart events, as well as non-Reclaim created eve…”
- [claimed-docs] “Scheduling Links enable you to send links to you and your team's availability, allowing others to book time across one, or many, calendars.”
Booking controls
knowledge workerProtect my calendar with buffers before and after meetings, minimum notice, daily booking caps, and date-range windows
weight 2 · round to Reclaim.aiCal.comnone0/10The 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.
Reclaim documents robust buffer-time features (travel time before/after meetings, decompression time, spacing between tasks/habits) and scheduling-link availability sharing, but the evidence pack has no mention of configurable minimum notice, daily booking caps, or date-range windows for scheduling links. missing for 10: minimum notice period settings, daily booking caps, date-range windows for booking links, independent confirmation of these specific link controls.
- [claimed-docs] “Auto-schedule breaks & travel across your meetings & work sessions.”
- [claimed-docs] “Reclaim can automatically add smart buffers between events to ensure you have time to travel, take a break, or chunk up your Task and Habit …”
- [claimed-docs] “Reclaim can add free space between your Tasks and Habits to prevent them from being scheduled back-to-back and break up your focused work.”
- [claimed-docs] “Travel Time: auto-add time before and after events with a location.”
- [claimed-docs] “Reclaim can automatically add travel time before and after events on your main account's primary calendar”
- [claimed-docs] “Decompression Time: auto-add time after meetings to take a break.”
- [claimed-docs] “Share your availability using smart meeting controls.”
- [claimed-docs] “Scheduling Links enable you to send links to you and your team's availability, allowing others to book time across one, or many, calendars.”
founderCollect payment (e.g. via Stripe) at the moment of booking for paid sessions
weight 1 · round to Cal.comCal.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…”
Reclaim.ainone0/10No evidence anywhere in the pack of Stripe integration or payment collection at booking; scheduling links features cover availability and auto-rescheduling only, not payments.
- [claimed-docs] “Share your availability using smart meeting controls.”
- [claimed-docs] “Reclaim automatically reschedules it to the next best time. No reshuffling required.”
- [claimed-docs] “automatically offer up lower-priority events scheduled on your calendar (both other Reclaim smart events, as well as non-Reclaim created eve…”
knowledge workerInvitees always see slots in their own time zone — detection, display, and DST handling are automatic
weight 3 · round drawnCal.comnone0/10The 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.
Calendar management — stories about calendar management in this arenaCalendar management
Stories about calendar management in this arena
Calendars
knowledge workerBusy blocks sync between my work and personal calendars automatically so all my schedules stay in step
weight 2 · round drawnCal.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…”
Reclaim.aidisputedcontradicted6/10Reclaim's Calendar Sync feature is documented extensively as creating 'synced copies' of events across source/destination calendars so busy blocks stay in sync automatically (reclaim-docs-8, reclaim-docs-13, reclaim-docs-18, reclaim-docs-23, reclaim-docs-50), which directly matches the story. However, a hands-on community report describes the sync failing to reflect changes when tested across accounts ('I've signed up... but if I invite myself from another account, nothing happens' — reclaim-comm-5), a concrete contradiction of the claimed automatic behavior. Missing for 10: independent verification that sync reliably works across real work/personal accounts, resolution of the reported failure case, and clearer documentation on cross-provider (e.g., Exchange/Outlook) sync reliability.
- [claimed-docs] “Automatically defend time for events across all of your schedules.”
- [claimed-docs] “Calendar Sync takes events from a source calendar - we call these source events - and creates smart copies of them on a destination calendar…”
- [claimed-docs] “Synced copies stay up-to-date as the source events change, so you never have to worry about manually updating or adding events across calend…”
- [claimed-docs] “a powerful way to make sure people who go to book time with you always see your true availability across multiple calendars”
- [claimed-docs] “Reclaim's Calendar Sync feature is a powerful way to make sure people who go to book time with you always see your true availability across …”
- [community] “It didn't worked for me. I've signed up, i have the events created by Reclaim in my calendar, but if I invite myself from another account, n…”
knowledge workerConnect several calendars (Google, Outlook, Apple) and every one is checked for conflicts so I never get double-booked
weight 3 · round to Reclaim.aiThe 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.”
Reclaim's Calendar Sync explicitly creates 'synced copies' across calendars so double-booking is avoided and true availability is reflected, and docs confirm native Google and Outlook support (reclaim-docs-8,13,18,23,50,46,47). Apple/iCloud support exists but only via a workaround using shared calendar sync to Google Calendar, not a first-class integration (reclaim-docs-48), and one hands-on community report describes cross-account invites not being caught (reclaim-comm-5), while older community comments raised doubts about Exchange/O365 coverage (reclaim-comm-6,7). missing for 10: native first-class Apple Calendar integration, current independent confirmation that conflict detection works reliably across all three calendar types simultaneously.
- [claimed-docs] “Automatically defend time for events across all of your schedules.”
- [claimed-docs] “Calendar Sync takes events from a source calendar - we call these source events - and creates smart copies of them on a destination calendar…”
- [claimed-docs] “Synced copies stay up-to-date as the source events change, so you never have to worry about manually updating or adding events across calend…”
- [claimed-docs] “a powerful way to make sure people who go to book time with you always see your true availability across multiple calendars”
- [claimed-docs] “Reclaim's Calendar Sync feature is a powerful way to make sure people who go to book time with you always see your true availability across …”
- [claimed-docs] “install our Google Calendar and Gmail Add-on to get the power of Reclaim directly in Google or Outlook's web UI, and/or add our Slack integr…”
- [claimed-docs] “Reclaim is designed to be a calendar assistant that works with your Google or Outlook calendar (not replace it).”
- [claimed-docs] “you can use a shared calendar (via iCloud, or another external calendar service) and sync events from that calendar to another Google Calend…”
- [community] “It didn't worked for me. I've signed up, i have the events created by Reclaim in my calendar, but if I invite myself from another account, n…”
- [community] “In can't tell if it has Exchange support. I assume not. To get into many of the Fortune 500, you'll need O365 and Exchange.”
- [community] “I love it. At least, the idea, without having tried it yet. The moment you support Office365 calendars, you can have all my money.”
knowledge workerDefine availability schedules with working hours, date overrides, and out-of-office periods
weight 2 · round to Cal.comCal.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…”
Reclaim provides dedicated OOO/vacation handling (reclaim-docs-38) and schedule overrides via hashtags like #reclaim_free/#reclaim_busy for exception periods (reclaim-docs-43, reclaim-docs-44), plus availability-based scheduling links (reclaim-docs-2, reclaim-docs-49, reclaim-docs-23). However, there's no explicit documentation of a dedicated 'working hours' settings screen or true date-specific override calendar (beyond hashtag hacks), missing for 10: explicit working-hours configuration UI, granular date-override scheduling beyond hashtags, and independent verification of these settings working reliably.
- [claimed-docs] “you may also want Reclaim to continue scheduling your Tasks and Habits during that period of time. Reclaim supports both of these use cases.”
- [claimed-docs] “you can set a smart No-Meeting Day using the hashtag #reclaim_free. Reclaim will mark the day as busy for new meeting invitations, but keep …”
- [claimed-docs] “add the hashtag #reclaim_busy to it. This will tell Reclaim's scheduler to treat that time as busy, despite it being marked as free.”
- [claimed-docs] “Share your availability using smart meeting controls.”
- [claimed-docs] “Scheduling Links enable you to send links to you and your team's availability, allowing others to book time across one, or many, calendars.”
- [claimed-docs] “a powerful way to make sure people who go to book time with you always see your true availability across multiple calendars”
Developer platform — stories about developer platform in this arenaDeveloper platform
Stories about developer platform in this arena
Platform
developerWebhooks notify my systems in real time when bookings are created, rescheduled, or canceled
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10No evidence of any webhook capability for booking/reschedule/cancel events; probes for OpenAPI/API docs returned 404s and no webhook documentation appears anywhere in the evidence pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://help.reclaim.ai/openapi.json, https://help.reclaim.ai/swagger.json, https://help.reclaim.ai/…”
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.comCal.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:…”
Reclaim.ainone0/10No evidence of a documented REST API for managing event types, availability, or bookings; probes for OpenAPI/Swagger specs all returned 404, and no docs mention a public API or SDK for developers.
developerSelf-host the full scheduling engine from source or a container image under an open-source license
weight 2 · round to Cal.comCal.comdisputedcontradicted4/10Cal.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…”
Embeds integrations — stories about embeds integrations in this arenaEmbeds integrations
Stories about embeds integrations in this arena
Embeds
sales leadBookings flow into my CRM and automation stack (Salesforce, HubSpot, Zapier) without manual copying
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10The evidence pack details Reclaim's calendar sync (Google/Outlook), Slack status sync, and task-tool integrations (Todoist, Asana, ClickUp, Linear, Jira, Google Tasks), but contains no mention of Salesforce, HubSpot, Zapier, or any CRM/automation-platform integration for sales bookings. Since Reclaim is a scheduling tool, this CRM/automation-flow axis is a fair question, but no evidence supports it being delivered.
developerEmbed the booking experience in my own site — inline, popup, or floating widget — with a documented snippet
weight 2 · round drawnCal.comnone0/10The 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.”
Reclaim.ainone0/10No evidence of an embeddable booking widget (inline/popup/floating) or documented snippet for websites; Scheduling Links only refer to sharable links, not embeds. Missing for 10: any mention of embed code, widget SDK, iframe, or JS snippet for embedding booking on external sites.
Meeting workflows — stories about meeting workflows in this arenaMeeting workflows
Stories about meeting workflows in this arena
Workflows
sales leadAutomated reminder and follow-up sequences (email/SMS) fire around every booking to cut no-shows
weight 2 · round to Cal.comEvidence 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…”
founderInvitees can reschedule or cancel from their confirmation, with my policies enforced and calendars updated everywhere
weight 2 · round to Cal.comCal.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…”
Reclaim.ainone0/10The evidence describes Reclaim's own AI-driven rescheduling of lower-priority events and Calendar Sync propagating changes, but there is no documentation of an invitee-facing reschedule/cancel action from a booking confirmation, nor of policies (e.g., notice windows, buffers) being enforced when an invitee makes that change. This is a reasonable ask for a scheduling-link product, but no evidence supports it.
- [claimed-docs] “Reclaim automatically reschedules it to the next best time. No reshuffling required.”
- [claimed-docs] “If a meeting overbooks another lower-priority smart event, Reclaim automatically reschedules it to the next best time. No reshuffling requir…”
- [claimed-docs] “Scheduling Links enable you to send links to you and your team's availability, allowing others to book time across one, or many, calendars.”
founderEvery booking gets a video conference link automatically (Zoom, Google Meet, Teams, or native video)
weight 2 · round to Cal.comDocs 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…”
Reclaim.ainone0/10The evidence pack covers Reclaim's scheduling, buffers, calendar sync, tasks, and priorities extensively, but there is no mention anywhere of automatic video conference link generation (Zoom, Google Meet, Teams, or native video) for bookings or scheduling links. Missing for 10: any documentation of video conferencing integration or auto-added meeting links to bookings/scheduling links.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Cal.comCal.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”
Reclaim.ainone0/10The evidence pack contains no documentation of a public API at all — probes for OpenAPI/swagger specs at help.reclaim.ai all returned 404, and no docs items reference API endpoints or programmatic parity with the UI. Without any evidence of an API existing, there's no basis to claim API/UI feature parity.
ai-native userExport all of my data in open formats and leave
weight 3 · round to Cal.comCal.comdisputedcontradicted3/10Cal.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…”
Reclaim.ainone0/10No evidence of any data export/portability feature or open-format export capability; evidence only covers scheduling/calendar automation features, and API/openapi probes returned 404s, suggesting no documented export mechanism.
ai-native userRead the product's source under an open license
weight 2 · round to Cal.comCal.comdisputedcontradicted5/10Cal.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…”
Reclaim.ainone0/10Reclaim.ai is a closed-source SaaS scheduling product; no evidence of any open-source license or public source repository is present in the evidence pack. This is a fair axis to ask (any product could open-source components), but nothing indicates it does, so verdict is none.
ai-native userSelf-host the core product
weight 3 · round to Cal.comCal.comdisputedcontradicted4/10Vendor 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…”
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Pricing
founderThe free tier covers real individual scheduling — a usable booking link without a paid plan
weight 2 · round to Cal.comA 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…”
Docs confirm a free 'Lite' tier exists for a single user with 'essential smart time blocking features' (reclaim-docs-16/28), and Scheduling Links are documented as a core feature (reclaim-docs-2, reclaim-docs-49), but no evidence explicitly states that Scheduling Links/booking links are included in the free Lite tier versus gated behind a paid plan. Missing for 10: explicit confirmation that booking/scheduling links work on the free tier, and independent hands-on confirmation of a usable free booking link.
- [claimed-docs] “Lite is available for any single user at no cost to help you take back control of your calendar with essential smart time blocking features.”
- [claimed-docs] “Lite** is available for any single user at no cost to help you take back control of your calendar with essential smart time blocking feature…”
- [claimed-docs] “Share your availability using smart meeting controls.”
- [claimed-docs] “Scheduling Links enable you to send links to you and your team's availability, allowing others to book time across one, or many, calendars.”
founderPublished per-seat pricing tells me exactly what each tier costs and includes before I talk to sales
weight 1 · round to Reclaim.aiCal.comnone0/10The 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.”
Evidence confirms Reclaim has a dedicated pricing/plans doc and that the Lite tier is free for a single user, but no evidence pack content shows actual per-seat dollar prices or feature breakdowns for paid tiers. Missing for 10: explicit price points for Starter/Business/Enterprise tiers, per-seat cost breakdown, and feature comparison table across tiers.
- [claimed-docs] “Lite is available for any single user at no cost to help you take back control of your calendar with essential smart time blocking features.”
- [claimed-docs] “Lite** is available for any single user at no cost to help you take back control of your calendar with essential smart time blocking feature…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to Cal.comCal.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…”
Reclaim.ainone0/10No evidence anywhere in the pack that Reclaim.ai offers data residency/region selection options; all documentation covers scheduling features with no mention of data storage location controls. Missing for 10: any mention of data residency, regional hosting, or storage location choice.
ai-native userControl data retention and deletion
weight 2 · round drawnCal.comnone0/10The 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…”
Reclaim.ainone0/10No evidence pack items address data retention, deletion, export, or privacy controls for user data; all citations focus on scheduling/calendar features and community sentiment unrelated to data governance. missing for 10: data retention policy documentation, account/data deletion mechanism, data export tools, privacy/GDPR compliance controls.
Team scheduling — stories about team scheduling in this arenaTeam scheduling
Stories about team scheduling in this arena
Teams
sales leadOffer collective events that only show slots when every required host is free
weight 2 · round to Cal.comCal.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.”
Reclaim's Scheduling Links let a sales lead share "you and your team's availability" so bookers can pick slots "across one, or many" calendars (reclaim-docs-49), and Smart Meetings claim to find times that work for all attendees (reclaim-docs-5), which is directionally aligned with collective event scheduling. However, there is no explicit documentation of a distinct 'collective' event type or of logic that strictly shows only slots where every required host is simultaneously free (vs. round-robin or single-host links). missing for 10: explicit product terminology/config for collective events, confirmation that all-hosts-free logic is enforced, independent/hands-on verification of this specific behavior.
- [claimed-docs] “Scheduling Links enable you to send links to you and your team's availability, allowing others to book time across one, or many, calendars.”
- [claimed-docs] “Find the best time to meet across all attendees' schedules.”
- [claimed-docs] “Reclaim's Calendar Sync feature is a powerful way to make sure people who go to book time with you always see your true availability across …”
sales leadInbound meetings distribute across my team round-robin, with weighting or priority so load stays fair
weight 2 · round to Cal.comCal.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.”
Reclaim.ainone0/10Reclaim's evidence covers individual scheduling, priorities, buffers, scheduling links, and calendar sync, but there is no mention of round-robin distribution, lead routing, or weighted/priority-based load balancing across a sales team's inbound meetings — that is a distinct sales-scheduling capability not evidenced here.
sales leadA routing form qualifies invitees and sends them to the right person or team based on their answers
weight 1 · round to Cal.comCal.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 …”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableCal.comn/aCal.com's AI-native positioning is entirely about exposing itself AS an MCP server/tool provider (mcp.cal.com, API v2 for agents) so that external AI agents can call Cal.com's scheduling tools — the evidence shows no agentic host/orchestration role within Cal.com where a user would plug external MCP servers into Cal.com itself to extend its own capabilities. This story describes the client-side 'consume other tools' direction, which is a different axis (and the inverse of what Cal.com's docs describe), so it is a category mismatch for this SaaS scheduling product's documented architecture.
- [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] “letting you manage bookings, event types, schedules, and more through natural language in any MCP-compatible client.”
Reclaim.ainone0/10No evidence that Reclaim.ai supports plugging in MCP servers or any tool-use protocol; the product integrates with calendars, task apps, and Slack, but there's nothing about MCP client capability. Missing for 10: any mention of MCP support, tool-plugin architecture, or third-party tool invocation.
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableCal.comnone0/10The 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…”
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableCal.comn/aCal.com is a scheduling platform, not an AI model provider or AI product with training data policies; the evidence pack shows only scheduling/API/compliance features (GDPR, SOC2, HIPAA) with no mention of AI model training opt-outs. This axis is a category error for a scheduling infrastructure product.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableCal.comn/aCal.com is a scheduling SaaS/platform, and the evidence pack has no mention of telemetry opt-out or usage-tracking controls; this axis is really an AI-agent/tool privacy-posture question about a client SDK or agent framework, not a fair question for this kind of scheduling product's evidence pack. Given no product feature ever surfaces around telemetry toggles, treat as category mismatch rather than a documented absence.
Reclaim.ainone0/10No evidence in the pack addresses telemetry/usage-tracking opt-out settings or privacy controls for Reclaim.ai; documentation focuses entirely on scheduling features, and one community comment even expresses discomfort about handing calendar data to the company with no rebuttal about opt-out mechanisms.
- [community] “I may not be the target demo (I'm a solo founder) but I would never give another company my schedule to analyze and optimize... time managem…”