Calendly vs Motion

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

   Motion—none0/10

   Motion's API docs mention creating/updating projects and tasks, but no evidence pack item shows meeting-specific endpoints for checking availability, booking, rescheduling, or canceling meetings via API, nor any MCP server. Meeting scheduling features (daily limits, templates, calendar merging) are described as dashboard/product features, not API-exposed agent actions.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Set daily limits and watch Motion enforce them automatically. When you hit your threshold, your calendar becomes unbookable—no more accident…”
   • [claimed-docs] “Build a template for every scenario. Client calls, board meetings, team all hands, sales demos—create a custom template for each with specif…”

   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

   Motion—none0/10

   Motion documents a general REST API for tasks/projects (motion-docs-1, motion-docs-29) but no evidence of an MCP server or agent tool-calling surface exposing availability, bookings, or event types specifically for AI agents. The axis applies since a scheduling SaaS could plausibly ship such an interface, but nothing in the evidence pack shows one exists.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”

   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

   Motion~partialclaimed6/10

   Motion has a live llms.txt file (motion-docs-1, motion-docs-34) and API docs/cookbooks (motion-docs-2, motion-docs-28, motion-docs-29) that an agent could be pointed at, showing basic agent-oriented documentation exists. missing for 10: no explicit agent-facing usage guidance beyond the llms.txt stub, no independent/hands-on confirmation an agent successfully used llms.txt to accomplish tasks, and no dedicated 'for AI agents' onboarding docs beyond API reference.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Usemotion’s AI-powered scheduling, automated prioritization, meeting booking, and workflow automation tailored to each industry’s specific p…”
   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   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

   Motion~partialclaimed3/10

   Motion exposes a REST API for creating/managing tasks and projects (docs-1, docs-29) which could technically be scripted for automation, but there is no evidence of a CLI, headless mode, Docker/container support, or CI-specific documentation/examples showing the product running unattended in a pipeline. Missing for 10: CLI or headless execution mode, explicit CI/CD integration guides, and independent evidence of automated/agentic use via the API.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   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

   Motion—none0/10

   Evidence shows Motion has a REST API and Zapier integration, but there is no mention of MCP server support, allowing MCP clients/tools to be plugged into Motion. Motion is a productivity SaaS product, so publishing an MCP server is a plausible axis, but no evidence confirms it exists.

   • [claimed-docs] “Connect with thousands of the most popular apps using Zapier.”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   proof ↗⚑ 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

   Motion—none0/10

   Motion offers a REST API and Zapier integration, but there is no evidence of an official MCP server or MCP-based agent connectivity anywhere in the evidence pack.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Connect with thousands of the most popular apps using Zapier.”

   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

   Motion—none0/10

   Motion documents a REST API and cookbooks (motion-docs-1, motion-docs-2, motion-docs-29) but nowhere mentions an official CLI tool for AI-native workflows; the evidence pack contains no CLI reference at all.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   proof ↗⚑ 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

   Motion✓fullclaimed7/10

   Motion publishes a documented public API (docs.usemotion.com/api-reference) with endpoint guides and cookbooks, and llms.txt explicitly states API access for creating/updating/managing projects and tasks, supporting programmatic/agentic use. Missing for 10: independent/hands-on developer corroboration of the API in practice, details on auth/rate limits/SDKs, and evidence of AI agents actually integrating via this API.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   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

   Motion—none0/10

   Evidence shows Motion has a general API and 'Permissions & Access Control' as a pricing-tier feature, but nothing documents scoped or least-privilege API credentials/tokens specifically for agent use. Missing for 10: documentation of API key scoping, granular permission levels for tokens, or agent-specific credential issuance.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Permissions & Access Control”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Motion
   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

   Motion~partialclaimed5/10

   Motion has a documented API with reference docs and cookbooks for tasks/projects, which supports building against its API, but there is no evidence of official language-specific SDKs (e.g., Python, JS/TS client libraries), versioning, or authentication/rate-limit details typically expected for 'official SDKs'. missing for 10: dedicated SDK packages (e.g. npm/pypi clients), SDK versioning/release notes, authentication and error-handling guides, independent developer corroboration of SDK usage.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   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

   Motion—none0/10

   No evidence of a webhook subscription mechanism; Motion's docs mention API access, cookbooks, and third-party Zapier integration but nothing about outbound webhooks or event subscriptions. Missing for 10: any documentation of a webhook endpoint, event types, or subscription API.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Connect with thousands of the most popular apps using Zapier.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Motion
   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

   Motion✓fullclaimed7/10

   Motion's docs describe multiple AI-generated insights derived from user data: proactive at-risk task/project warnings, priority highlighting, predictive project completion dates, an AI Search Assistant, and an AI Workflow Builder that infers workflows from SOPs — all directly analyzing the user's tasks/projects/calendar to surface suggestions. missing for 10: independent/hands-on verification of insight accuracy and no detail on how suggestions are surfaced/explained to users beyond marketing copy.

   • [claimed-docs] “Motion analyzes all your work and highlights your #1 priority at any moment—so you stop wasting time evaluating what you need to work on nex…”
   • [claimed-docs] “When Motion thinks a task is at-risk of missing deadline, it proactively warns you days, weeks, or months in advance.”
   • [claimed-docs] “As soon as a project is off-track, Motion alerts you so that you can course-correct before it's too late.”
   • [claimed-docs] “Motion flags at-risk tasks early, so you can address potential delays before they affect your project.”
   • [claimed-docs] “we can predict exactly when a project will finish based on your team's capacity, and all the other ongoing projects.”
   • [claimed-docs] “AI Search Assistant Instantly finds anything - docs, notes, project, task, communication”
   • [claimed-docs] “AI Workflow Builder Automatically builds workflows based on SOPs”

   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

   Motion~partialclaimed6/10

   Motion's vendor docs describe multiple background automations that run without manual intervention—auto-scheduling/reshuffling calendars, auto-blocking recurring tasks, projects advancing on their own as blockers clear, email/voice-to-task capture, and an AI Workflow Builder that auto-builds workflows from SOPs. This directly matches 'autonomous background automation' for a task/calendar-native persona, but all evidence is vendor-authored feature copy with no independent/hands-on confirmation that these automations reliably run unattended over time. Missing for 10: independent verification or user testimonials of autonomous operation, and detail on failure/error handling when automations run without oversight.

   • [claimed-docs] “Motion reshuffles your entire day (and week) in seconds—protecting your time and mental bandwidth from manual reorganization.”
   • [claimed-docs] “Create custom time windows for your tasks and watch Motion slot them in perfectly, ensuring you never miss a deadline.”
   • [claimed-docs] “Create daily, weekly, monthly, or quarterly tasks and Motion's AI Task Manager will block time on your calendar regularly so you get them do…”
   • [claimed-docs] “a project will just move forward by itself when team members complete their blocking tasks. Nothing ever gets stuck - and if it does, Motion…”
   • [claimed-docs] “Forward emails to Motion and we'll automatically schedule them as tasks.”
   • [claimed-docs] “AI Workflow Builder Automatically builds workflows based on SOPs”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Motion~partialclaimed6/10

   Motion offers several built-in AI capabilities (AI Task Manager, AI Project Manager, AI Workflow Builder, AI Search Assistant, AI Meeting Notetaker) that autonomously prioritize, schedule, and flag work, which functions as a form of task delegation to AI. However, evidence shows these as automation features embedded in workflows rather than a conversational assistant interface you explicitly delegate to, and there's no independent corroboration of real-world delegation experience. Missing for 10: a clear conversational/chat-based delegation interface, first-person or independent user accounts of delegating tasks to the assistant, and confirmation of agentic task execution beyond scheduling/alerts.

   • [claimed-docs] “Create custom time windows for your tasks and watch Motion slot them in perfectly, ensuring you never miss a deadline.”
   • [claimed-docs] “a project will just move forward by itself when team members complete their blocking tasks. Nothing ever gets stuck - and if it does, Motion…”
   • [claimed-docs] “As soon as a project is off-track, Motion alerts you so that you can course-correct before it's too late.”
   • [claimed-docs] “AI Search Assistant Instantly finds anything - docs, notes, project, task, communication”
   • [claimed-docs] “AI Workflow Builder Automatically builds workflows based on SOPs”
   • [claimed-docs] “Motion flags at-risk tasks early, so you can address potential delays before they affect your project.”

   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

   Motion~partialclaimed4/10

   Motion offers some natural-language-adjacent entry points—voice task creation via Siri, email-to-task conversion, and an AI workflow builder based on SOPs—but there's no evidence of a conversational/chat interface for operating the full product (projects, scheduling, prioritization) via free-form natural language; the API is a structured REST interface, not NL. missing for 10: dedicated NL chat/command interface, evidence of broad task/project operations via typed natural language, independent hands-on confirmation.

   • [claimed-docs] “Quickly create tasks with your voice, and Motion's AI scheduling algorithm will automatically put them on your calendar.”
   • [claimed-docs] “Forward emails to Motion and we'll automatically schedule them as tasks.”
   • [claimed-docs] “turn Zoom/Meet/Teams meetings or Slack/Teams messages into tasks, or tell Siri to add tasks via voice command.”
   • [claimed-docs] “AI Workflow Builder Automatically builds workflows based on SOPs”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Motion
   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

   Motion~partialclaimed3/10

   There is a reference to an API reference page and cookbooks/examples (motion-docs-28, motion-docs-29, motion-docs-2), suggesting documentation with guides, but no evidence of an interactive, runnable API reference (e.g., try-it console, live code execution) is provided. missing for 10: evidence of interactivity/runnable examples in the API reference, first-party demonstration of a live sandbox or code runner, independent corroboration of hands-on use.

   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   proof ↗⚑ flag

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

   weight 2 · round to Motion
   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

   Motion~partialclaimed4/10

   Motion has a public API reference site (docs.usemotion.com/api-reference/) implying documented endpoints, but no evidence explicitly confirms a downloadable OpenAPI/Swagger spec file or machine-readable schema is provided. Missing for 10: explicit OpenAPI/Swagger JSON or YAML download link, confirmation the API reference is machine-readable/spec-generated, and independent confirmation of spec availability.

   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Motion—none0/10

   No evidence of a sandbox/test environment or non-production API mode is mentioned anywhere in the docs; only production API and feature docs are cited. Missing for 10: any mention of a sandbox environment, test/staging API keys, or mock data mode.

   ⚑ flag

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

   weight 2 · round drawn
   Calendly—none0/10

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

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

   proof ↗⚑ flag

   Motion—none0/10

   Motion has a documented API and cookbooks (motion-docs-1, motion-docs-28, motion-docs-29), so the axis of API governance clearly applies, but no evidence anywhere mentions API versioning scheme, version numbers, or a deprecation policy for breaking changes.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   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 Motion
   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

   Motion~partialclaimed5/10

   Motion's AI calendar/meeting assistant reshuffles schedules and books meetings, but evidence focuses on single-user auto-scheduling and booking links (embed calendar for prospects) rather than multi-attendee cross-calendar optimization that continuously re-evaluates the best slot as all attendees' calendars change. No documented capability for polling multiple attendees' availability and iteratively finding a globally optimal time beyond first available slot. missing for 10: evidence of true multi-attendee negotiation/optimization across all invitees' calendars, evidence of continuous re-optimization after initial booking, and independent/hands-on confirmation of this specific behavior.

   • [claimed-docs] “Motion reshuffles your entire day (and week) in seconds—protecting your time and mental bandwidth from manual reorganization.”
   • [claimed-docs] “Combine all your calendars in one view. Turn all of your calendar accounts—Outlook, Google, iCloud—into one single interface.”
   • [claimed-docs] “Share your schedule anywhere—embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Connect instantly with zero setup. Video conferencing links are automatically added to every meeting, eliminating the pre-meeting scramble f…”

   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 Motion
   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

   Motion✓fullclaimed7/10

   Motion's core value proposition directly matches the story: it auto-schedules tasks into calendar time blocks around deadlines and custom time windows (motion-docs-10, motion-docs-12), reshuffles the whole day/week automatically when things change (motion-docs-3), and proactively flags at-risk deadlines (motion-docs-11, motion-docs-39). Missing for 10: independent/hands-on verification of the re-planning behavior in practice (all evidence is vendor-authored marketing/docs), and no evidence of accuracy/reliability under real-world meeting conflicts.

   • [claimed-docs] “Motion reshuffles your entire day (and week) in seconds—protecting your time and mental bandwidth from manual reorganization.”
   • [claimed-docs] “Create custom time windows for your tasks and watch Motion slot them in perfectly, ensuring you never miss a deadline.”
   • [claimed-docs] “When Motion thinks a task is at-risk of missing deadline, it proactively warns you days, weeks, or months in advance.”
   • [claimed-docs] “Create daily, weekly, monthly, or quarterly tasks and Motion's AI Task Manager will block time on your calendar regularly so you get them do…”
   • [claimed-docs] “Quickly create tasks with your voice, and Motion's AI scheduling algorithm will automatically put them on your calendar.”
   • [claimed-docs] “Motion flags at-risk tasks early, so you can address potential delays before they affect your project.”

   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 Motion
   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

   Motion~partialclaimed6/10

   Motion's AI Calendar explicitly reshuffles the day/week to protect time from conflicts, and its Task Manager auto-blocks recurring (daily/weekly/monthly/quarterly) tasks and reschedules at-risk deadlines rather than dropping them, which matches the 'defend and flexibly move recurring commitments' story. However, no documentation specifically calls out 'recurring focus time blocks' or habit-protection as a distinct feature (only recurring tasks and general rescheduling are described), and there's no independent/hands-on confirmation of this exact conflict-resolution behavior. Missing for 10: explicit recurring focus-time/habit-protection feature docs, third-party or hands-on validation that conflicts trigger rescheduling rather than deletion.

   • [claimed-docs] “Motion reshuffles your entire day (and week) in seconds—protecting your time and mental bandwidth from manual reorganization.”
   • [claimed-docs] “Create custom time windows for your tasks and watch Motion slot them in perfectly, ensuring you never miss a deadline.”
   • [claimed-docs] “When Motion thinks a task is at-risk of missing deadline, it proactively warns you days, weeks, or months in advance.”
   • [claimed-docs] “Create daily, weekly, monthly, or quarterly tasks and Motion's AI Task Manager will block time on your calendar regularly so you get them do…”
   • [claimed-docs] “Motion flags at-risk tasks early, so you can address potential delays before they affect your project.”

   proof ↗⚑ flag

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

   weight 2 · round to Motion
   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

   Motion~partialclaimed3/10

   Motion documents a general API for creating/updating/managing projects and tasks with a full API reference, which could support scripted bulk actions, but no evidence describes batch/bulk endpoints, rate limits for bulk use, or examples of multi-item operations. Missing for 10: explicit bulk/batch API endpoints, documented rate limits or pagination for large-scale operations, and any hands-on example of bulk task/project manipulation.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”

   proof ↗⚑ flag

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

   weight 3 · round to Calendly
   Calendly✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Motion~partialclaimed4/10

   Motion has built-in automated behaviors (task risk alerts, project off-track alerts, meeting caps, auto-scheduling) but these are fixed AI features rather than user-definable trigger→action rules; genuine custom automation appears to require third-party Zapier integration rather than a native rules engine. Missing for 10: a native rule/trigger builder documented with examples, evidence of user-defined conditional logic, and independent confirmation that Zapier-based automations work as described.

   • [claimed-docs] “a project will just move forward by itself when team members complete their blocking tasks. Nothing ever gets stuck - and if it does, Motion…”
   • [claimed-docs] “As soon as a project is off-track, Motion alerts you so that you can course-correct before it's too late.”
   • [claimed-docs] “Put a cap on meeting overload. Set daily limits and watch Motion enforce them automatically.”
   • [claimed-docs] “Connect with thousands of the most popular apps using Zapier.”
   • [claimed-docs] “AI Workflow Builder Automatically builds workflows based on SOPs”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Motion
   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

   Motion~partialclaimed6/10

   Motion natively supports recurring tasks (daily/weekly/monthly/quarterly) that auto-schedule on the calendar, and offers a general task/project API plus an 'AI Workflow Builder' that builds workflows from SOPs, which together provide the building blocks for recurring/automated scheduling. However, there's no explicit documentation confirming the API itself exposes recurrence/cron-like scheduling for AI-native/programmatic workflow orchestration. Missing for 10: explicit API/webhook support for creating recurring jobs programmatically, and independent confirmation of the AI Workflow Builder's recurring capability.

   • [claimed-docs] “Create daily, weekly, monthly, or quarterly tasks and Motion's AI Task Manager will block time on your calendar regularly so you get them do…”
   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “AI Workflow Builder Automatically builds workflows based on SOPs”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Motion—none0/10

   No evidence of versioning, review, or rollback capabilities for automations/workflows in Motion's docs or community feedback; the evidence only covers scheduling, task management, and API access without any version-control features.

   ⚑ 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

   Motion✓fullclaimed7/10

   Motion offers embeddable booking via its AI Calendar so prospects/invitees can pick a slot from live availability directly, and its meeting assistant supports templates, limits, and calendar consolidation to keep availability accurate. Missing for 10: no direct evidence of a standalone shareable 'booking link' (only 'embed on website'), and no independent/hands-on confirmation of the booking flow's reliability.

   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Share your schedule anywhere—embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Build a template for every scenario. Client calls, board meetings, team all hands, sales demos—create a custom template for each with specif…”
   • [claimed-docs] “Combine all your calendars in one view. Turn all of your calendar accounts—Outlook, Google, iCloud—into one single interface.”
   • [claimed-docs] “Set daily limits and watch Motion enforce them automatically. When you hit your threshold, your calendar becomes unbookable—no more accident…”

   proof ↗⚑ flag

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

   weight 2 · round to Motion
   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

   Motion~partialclaimed5/10

   Motion's meeting assistant explicitly supports creating multiple templates with distinct durations, pre-meeting custom questions, and reminders, plus embeddable booking links and daily meeting limits — covering much of the story. However, there is no explicit mention of per-event-type location settings or configurable confirmation/approval rules for bookings. Missing for 10: documented location-per-event-type support, confirmation/approval workflow settings, independent verification of these booking-link features in practice.

   • [claimed-docs] “Build a template for every scenario. Client calls, board meetings, team all hands, sales demos—create a custom template for each with specif…”
   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Share your schedule anywhere—embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Set daily limits and watch Motion enforce them automatically. When you hit your threshold, your calendar becomes unbookable—no more accident…”
   • [claimed-docs] “Put a cap on meeting overload. Set daily limits and watch Motion enforce them automatically.”

   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

   Motion~partialclaimed4/10

   Motion's docs confirm daily meeting caps that make the calendar unbookable once reached (motion-docs-6, motion-docs-38) and booking-link embedding (motion-docs-5, motion-docs-27), but there is no evidence of buffer time before/after meetings, minimum notice requirements, or date-range booking windows. missing for 10: buffer time settings, minimum notice period, date-range window limits, independent verification of these booking-link controls.

   • [claimed-docs] “Set daily limits and watch Motion enforce them automatically. When you hit your threshold, your calendar becomes unbookable—no more accident…”
   • [claimed-docs] “Put a cap on meeting overload. Set daily limits and watch Motion enforce them automatically.”
   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Share your schedule anywhere—embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”

   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

   Motion—none0/10

   Evidence shows Motion's booking/calendar embed lets prospects book time slots, but nowhere does it mention payment collection, Stripe integration, or charging at booking time. Missing for 10: any mention of payment/Stripe integration, paid session booking, or checkout flow at time of scheduling.

   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Share your schedule anywhere—embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”

   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

   Motion—none0/10

   No evidence in the pack addresses timezone detection, display, or DST handling for booking-link invitees; the docs focus on scheduling AI, task/project management, and integrations without mentioning timezone logic.

   ⚑ 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

   Motion~partialclaimed5/10

   Motion docs show it combines multiple calendar accounts (Outlook, Google, iCloud) into one unified interface and auto-schedules tasks/meetings across them, implying busy blocks sync across connected calendars, but there is no explicit documentation confirming two-way busy-block syncing specifically between separate 'work' and 'personal' calendar accounts to keep both in step. missing for 10: explicit documentation of cross-account busy-block sync mechanics, confirmation of two-way conflict prevention across distinct work/personal calendars, and independent/hands-on verification of this specific sync behavior.

   • [claimed-docs] “Combine all your calendars in one view. Turn all of your calendar accounts—Outlook, Google, iCloud—into one single interface.”
   • [claimed-docs] “Motion reshuffles your entire day (and week) in seconds—protecting your time and mental bandwidth from manual reorganization.”

   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

   Motion~partialclaimed6/10

   Motion explicitly supports combining Google, Outlook, and iCloud calendars into one unified view (motion-docs-8), and its AI Calendar/AI Meeting Assistant features are built to auto-schedule and reshuffle time to avoid overlaps (motion-docs-3, motion-docs-6, motion-docs-38). However, there is no explicit documentation of a dedicated cross-calendar conflict-detection mechanism guaranteeing 'never double-booked' across all three providers simultaneously. Missing for 10: explicit conflict-detection/double-booking-prevention documentation, independent verification of multi-calendar sync reliability.

   • [claimed-docs] “Combine all your calendars in one view. Turn all of your calendar accounts—Outlook, Google, iCloud—into one single interface.”
   • [claimed-docs] “Motion reshuffles your entire day (and week) in seconds—protecting your time and mental bandwidth from manual reorganization.”
   • [claimed-docs] “Set daily limits and watch Motion enforce them automatically. When you hit your threshold, your calendar becomes unbookable—no more accident…”
   • [claimed-docs] “Put a cap on meeting overload. Set daily limits and watch Motion enforce them automatically.”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Motion—none0/10

   The evidence pack describes Motion's calendar-combining, meeting-limit, and task-scheduling features but never mentions configurable working-hours schedules, date-specific overrides, or out-of-office periods, which is the core of this story. Since calendar-management is clearly within Motion's product category, this is an applicable but unevidenced capability, not an out-of-category one.

   ⚑ 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

   Motion—none0/10

   Evidence shows Motion has an API for projects/tasks and booking/calendar features, but nothing in the pack describes webhooks or real-time event notifications for booking creation, rescheduling, or cancellation. Missing for 10: any mention of webhook endpoints, event subscriptions, or push notifications for booking lifecycle events.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”

   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

   Motion~partialclaimed4/10

   Motion documents a public API and reference/guides for creating and managing projects and tasks (motion-docs-1, motion-docs-29, motion-docs-2/28), showing a genuine developer API surface exists, but no evidence specifically confirms endpoints for event types, availability, or bookings — the scheduling/booking capability shown (docs-5/27) is an embeddable calendar widget, not documented as a programmatic API a developer could use to build booking into their own product. Missing for 10: explicit API endpoints/docs for event-type creation, availability rules, and booking management, plus any independent developer confirmation of using these endpoints.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Our cookbooks are a great place to get started for fully fleshed out examples!”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”

   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

   Motion—none0/10

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

   ⚑ flag

Embeds

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

   weight 2 · round to Calendly
   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

   Motion~partialclaimed4/10

   Motion documents a public API for tasks/projects and a Zapier integration that could theoretically bridge to CRMs, but there is no direct evidence of native Salesforce/HubSpot connectors or of booking data flowing automatically into a CRM without manual setup. missing for 10: native Salesforce/HubSpot integration docs, concrete example of booking-to-CRM automation, independent confirmation the Zapier path works reliably for this use case.

   • [claimed-docs] “Connect with thousands of the most popular apps using Zapier.”
   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”
   • [claimed-docs] “Say goodbye to siloed project management tools.”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   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

   Motion~partialclaimed3/10

   Motion's marketing pages mention embedding the AI Calendar on a website so prospects can book time slots, but there's no evidence of a documented snippet, nor of inline/popup/floating widget modes. missing for 10: actual embed code/snippet documentation, confirmation of multiple embed modes (inline, popup, floating), and any developer-facing integration guide beyond a marketing claim.

   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Share your schedule anywhere—embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”

   proof ↗⚑ flag

Workflows

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

   weight 2 · round to Calendly
   Calendly✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Motion~partialclaimed3/10

   Motion's meeting templates support configurable 'reminders' alongside durations and pre-meeting questions, implying some automated reminder capability tied to bookings, but there is no evidence of SMS reminders, multi-step follow-up sequences, or any explicit no-show-reduction framing. missing for 10: SMS reminder channel, explicit follow-up sequence automation, no-show reduction metrics/claims, and independent confirmation the reminders actually fire around bookings.

   • [claimed-docs] “Build a template for every scenario. Client calls, board meetings, team all hands, sales demos—create a custom template for each with specif…”
   • [claimed-docs] “Connect instantly with zero setup. Video conferencing links are automatically added to every meeting, eliminating the pre-meeting scramble f…”
   • [claimed-docs] “AI Meeting Notetaker Takes perfect notes and follows-up with action items for you”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Motion—none0/10

   Evidence covers Motion's meeting booking/embedding and daily meeting limits, but nothing describes invitee-facing reschedule/cancel flows from a confirmation email, policy enforcement on those actions, or cross-calendar sync of such changes.

   • [claimed-docs] “embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Set daily limits and watch Motion enforce them automatically. When you hit your threshold, your calendar becomes unbookable—no more accident…”
   • [claimed-docs] “Share your schedule anywhere—embed Motion's AI Calendar on your website so prospects can book your ideal time slots instantly.”
   • [claimed-docs] “Put a cap on meeting overload. Set daily limits and watch Motion enforce them automatically.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Motion✓fullclaimed8/10

   Motion's docs explicitly state video conferencing links are auto-added to every meeting with zero setup, and mentions Zoom/Meet/Teams integration for turning meetings into tasks, implying support across these platforms. Missing for 10: independent/hands-on confirmation of native video option and explicit per-platform setup details beyond vendor claims.

   • [claimed-docs] “Connect instantly with zero setup. Video conferencing links are automatically added to every meeting, eliminating the pre-meeting scramble f…”
   • [claimed-docs] “turn Zoom/Meet/Teams meetings or Slack/Teams messages into tasks, or tell Siri to add tasks via voice command.”
   • [claimed-docs] “Combine all your calendars in one view. Turn all of your calendar accounts—Outlook, Google, iCloud—into one single interface.”

   proof ↗⚑ flag

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

   weight 2 · round to Calendly
   Calendly~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Motion~partialclaimed4/10

   Motion has a documented API for creating/updating projects and tasks with a reference and cookbooks, but the evidence pack shows no indication that core UI capabilities like AI auto-scheduling, meeting assistant, workflow builder, or project alerts are exposed via API endpoints. Missing for 10: explicit API coverage for AI scheduling/calendar automation, meeting booking, workflow builder, and project alerting, plus any independent confirmation of API-UI parity.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “Explore our guides and examples to integrate Motion.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   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

   Motion—none0/10

   Evidence shows Motion has an API for creating/updating tasks and projects, but there is no mention of bulk data export, open format exports (CSV/JSON dumps), or account-portability/data-takeout features for users wanting to leave the platform. missing for 10: bulk export functionality, open-format data export (CSV/JSON), documented data portability/account closure export process.

   • [claimed-docs] “API access for creating, updating, and managing projects and tasks.”
   • [claimed-docs] “The API reference has a complete guide on all our endpoints.”

   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

   Motion—none0/10

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

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round 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

   Motion—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

   Motion—none0/10

   The evidence pack shows only paid pricing tiers (e.g., credits/seat/month, 'Business AI for power users') and no mention of a free plan or a booking-link feature available without payment; nothing indicates a usable free scheduling/booking capability.

   • [claimed-docs] “For power users and businesses with complex needs”
   • [claimed-docs] “Business AI For power users and businesses with complex needs”
   • [claimed-docs] “15,000 credits/seat/month”

   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

   Motion~partialclaimed4/10

   The pricing page evidence lists tier names (e.g., 'Business AI'), feature bullets (Gantt charts, time tracking, permissions, dashboards) and a usage detail ('15,000 credits/seat/month'), showing Motion does publish some tiered, per-seat plan information. However no evidence pack item shows actual dollar prices per seat/tier, so it's unclear the pricing is fully transparent before talking to sales. Missing for 10: explicit per-tier dollar pricing, seat-cost breakdown, and confirmation no 'contact sales' gating exists for upper tiers.

   • [claimed-docs] “For power users and businesses with complex needs”
   • [claimed-docs] “Business AI For power users and businesses with complex needs”
   • [claimed-docs] “15,000 credits/seat/month”
   • [claimed-docs] “Timeline & Gantt Charts”
   • [claimed-docs] “Time Tracking”
   • [claimed-docs] “Team Capacity Planning”
   • [claimed-docs] “Permissions & Access Control”
   • [claimed-docs] “Advanced Dashboards & Reports”

   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

   Motion—none0/10

   No evidence in the pack addresses data residency, regional storage options, or compliance controls for where data is stored; Motion's docs focus on scheduling, tasks, and API features only.

   ⚑ flag

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

   weight 3 · round drawn
   Calendly—none0/10

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

   ⚑ flag

   Motion—none0/10

   No evidence in the pack addresses data usage for AI training opt-out or any privacy controls regarding model training; all evidence covers scheduling/task/API features and unrelated engineering discussions.

   ⚑ 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

   Motion—none0/10

   The evidence pack contains no mention of data retention policies, deletion controls, export/erasure tools, or privacy/compliance settings for Motion. As a SaaS productivity tool handling user task/calendar data, this axis clearly applies, but there is no documentation or community evidence showing such controls exist.

   ⚑ 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

   Motion—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or opt-out controls for Motion; all docs focus on scheduling/task/project features and unrelated engineering blog discussions.

   ⚑ flag

Teams

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

   weight 2 · round to Calendly
   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

   Motion—none0/10

   No evidence describes collective/multi-host scheduling (i.e., booking links that only surface slots when all required hosts are free); the docs only cover single-host AI calendar booking, meeting assistant templates, and task scheduling. This is a plausible axis for a scheduling product, but nothing in the pack shows a collective-event or team-availability-intersection feature.

   ⚑ 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

   Motion—none0/10

   Motion offers individual AI calendar booking pages and team capacity planning, but there is no evidence of round-robin distribution of inbound meetings across a team, nor any weighting/priority logic for balancing sales lead load.

   ⚑ 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

   Motion—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