Calendly vs Reclaim.ai

Agent ops

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

   weight 3 · round to Calendly
   Calendly~partialprobed6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Calendly
   Calendly✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Reclaim.ai✓fullprobed7/10

   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.

   • [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…”
   • [probe] “PROBE docs-md: HTTP 404 at https://help.reclaim.ai/en/.md”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   Reclaim.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.

   • [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”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Calendly—none0/10

   All evidence describes Calendly *exposing* an MCP server so external AI agents can call Calendly's tools (docs-2, docs-5, docs-34, docs-35, probe-3) — this is the opposite direction from the story, which asks whether Calendly itself can plug in and consume external MCP servers' tools. No evidence shows Calendly (or its Callie assistant) acting as an MCP client that ingests third-party MCP servers.

   ⚑ flag

   Reclaim.ai—none0/10

   No 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.

   ⚑ flag

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

   weight 3 · round to Calendly
   Calendly✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   Reclaim.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.

   • [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”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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.

   ⚑ flag

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

   weight 3 · round to Calendly
   Calendly✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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.

   • [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”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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/…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Calendly
   Calendly~partialprobed4/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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.

   • [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”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Calendly
   Calendly✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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/…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Reclaim.ai
   Calendly~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Reclaim.ai✓fullclaimed7/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialcommunity6/10

   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…”

   proof ↗⚑ flag

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

   weight 3 · round to Reclaim.ai
   Calendly~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai✓fullclaimed7/10

   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”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialclaimed5/10

   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”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   No 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/…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   The 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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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/…”

   proof ↗⚑ flag

Ai calendar

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

   weight 1 · round to Reclaim.ai
   Calendly~partialcommunity4/10

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

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

   proof ↗⚑ flag

   Reclaim.ai✓fullcommunity8/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round to Reclaim.ai
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Reclaim.ai✓fullcommunity8/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round to Reclaim.ai
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai✓fullcommunity9/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   Reclaim's docs describe automating scheduling, priorities, and syncing for individual tasks/habits/meetings, but there is no evidence of a bulk-operations capability (e.g., editing, rescheduling, or updating many items at once via a single command or API call).

   ⚑ flag

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

   weight 3 · round to Calendly
   Calendly✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialclaimed5/10

   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.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Reclaim.ai
   Calendly~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialcommunity6/10

   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…”

   proof ↗⚑ flag

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

   weight 1 · round to Reclaim.ai
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai~partialclaimed2/10

   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…”

   proof ↗⚑ flag

Booking

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

   weight 3 · round to Calendly
   Calendly✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   Reclaim.ai✓fullclaimed7/10

   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.”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   Reclaim'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.”

   proof ↗⚑ flag

Booking controls

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

   weight 2 · round to Calendly
   Calendly~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialclaimed4/10

   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.”

   proof ↗⚑ flag

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

   weight 1 · round to Calendly
   Calendly~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   No evidence describes time zone detection, display in invitee's local time, or DST handling for Scheduling Links; docs mention 'true availability across calendars' and lock times 'in your local timezone' but never address invitee-side timezone conversion or DST correctness.

   ⚑ flag

Calendars

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

   weight 2 · round to Calendly
   Calendly✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai!disputedcontradicted6/10

   Reclaim'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…”

   proof ↗⚑ flag

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

   weight 3 · round to Calendly
   Calendly✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialcommunity6/10

   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.”

   proof ↗⚑ flag

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

   weight 2 · round to Reclaim.ai
   Calendly~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialclaimed7/10

   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”

   proof ↗⚑ flag

Platform

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

   weight 2 · round to Calendly
   Calendly✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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/…”

   proof ↗⚑ flag

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

   weight 3 · round to Calendly
   Calendly✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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.

   • [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”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   Reclaim.ai is a closed-source SaaS scheduling product with no evidence of any open-source license, source availability, or container image for self-hosting; all evidence points to a hosted proprietary service.

   ⚑ flag

Embeds

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

   weight 2 · round to Calendly
   Calendly~partialclaimed7/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   The 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.

   ⚑ flag

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

   weight 2 · round to Calendly
   Calendly✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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.

   ⚑ flag

Workflows

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

   weight 2 · round to Calendly
   Calendly✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   Reclaim.ai is a calendar/scheduling automation tool focused on smart time-blocking, buffers, and scheduling links; no evidence anywhere in the pack mentions automated reminder or follow-up sequences via email/SMS to reduce no-shows.

   ⚑ flag

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

   weight 2 · round to Calendly
   Calendly✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   The 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.”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   The 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.

   ⚑ flag

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

   weight 2 · round to Calendly
   Calendly~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   The 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.

   • [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”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   No 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.

   • [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”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   Reclaim.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.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

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

   ⚑ flag

Pricing

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

   weight 2 · round to Calendly
   Calendly~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialclaimed4/10

   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.”

   proof ↗⚑ flag

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

   weight 1 · round to Calendly
   Calendly~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialclaimed3/10

   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…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   No 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.

   ⚑ flag

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

   weight 3 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   No evidence of any AI-training opt-out, data-usage policy, or privacy controls for AI model training; evidence only covers scheduling features and general product feedback.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   No 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.

   ⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Reclaim.ai—none0/10

   No 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…”

   proof ↗⚑ flag

Teams

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

   weight 2 · round drawn
   Calendly~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Reclaim.ai~partialclaimed5/10

   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 …”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   Reclaim'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.

   ⚑ flag

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

   weight 1 · round to Calendly
   Calendly✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Reclaim.ai—none0/10

   Evidence covers scheduling links, calendar sync, and availability sharing, but there is no mention of a routing form feature that qualifies invitees via questions and routes them to different people/teams — this is a distinct capability from simple scheduling links.

   ⚑ flag