[ { "productId": "cal-com", "storyId": "agent-books-meeting", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com's API v2 and hosted MCP server are explicitly documented as enabling AI agents to check availability, create, and reschedule bookings without a dashboard, with public booking endpoints for agent use and natural-language management via any MCP client (cal-com-docs-11,12,17,18,30,45,46,50, probe-4). Cancellation is only implied via the BOOKING_CANCELLED webhook trigger and reschedule-status docs rather than an explicitly cited cancel-booking endpoint, and there is no independent/hands-on corroboration of the full agent workflow. Missing for 10: explicit docs/citation of a dedicated cancel-booking API call, and third-party validation of end-to-end agent use.", "evidenceIds": [ "cal-com-docs-11", "cal-com-docs-12", "cal-com-docs-17", "cal-com-docs-18", "cal-com-docs-30", "cal-com-docs-45", "cal-com-docs-46", "cal-com-docs-2", "cal-com-docs-3", "cal-com-docs-24", "cal-com-probe-4" ] }, { "productId": "cal-com", "storyId": "agent-scheduling-tool", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com documents a hosted/local MCP server (mcp.cal.com) that lets AI clients manage bookings, event types, and schedules via natural language, plus a dedicated agents.md guide describing API v2 endpoints for checking availability, creating bookings, and managing event types, corroborated by a probe confirming the MCP server doc page. missing for 10: independent/hands-on third-party confirmation that the MCP server works reliably in practice, and no evidence of a full tool-calling schema/manifest beyond docs.", "evidenceIds": [ "cal-com-docs-11", "cal-com-docs-30", "cal-com-docs-49", "cal-com-docs-12", "cal-com-docs-17", "cal-com-docs-31", "cal-com-docs-45", "cal-com-docs-46", "cal-com-probe-4" ] }, { "productId": "cal-com", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Cal.com has a verified llms.txt (HTTP 200 probe) plus a dedicated agent-oriented docs page (cal.com/docs/agents.md) explicitly describing how AI agents should use the API, and a documentation index directive pointing agents to the full llms.txt for discovery. missing for 10: independent third-party confirmation that an agent successfully navigated the docs end-to-end via llms.txt.", "evidenceIds": [ "cal-com-probe-1", "cal-com-docs-16", "cal-com-docs-12", "cal-com-docs-45", "cal-com-intdir-1", "cal-com-probe-2" ] }, { "productId": "cal-com", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Cal.com exposes an API/MCP server so external AI agents can query availability and create bookings, but this is about agents acting as clients on the user's data, not the product itself surfacing AI-generated insights or suggestions to users. No documentation mentions built-in analytics, pattern-based scheduling suggestions, or AI-generated summaries within the Cal.com product.", "evidenceIds": [ "cal-com-docs-12", "cal-com-docs-17", "cal-com-docs-30", "cal-com-docs-49" ] }, { "productId": "cal-com", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Cal.com provides API/webhooks, workflows, MCP server, and an agents.md guide explicitly enabling AI agents to check availability, create/reschedule bookings, and manage event types autonomously via natural language or API calls, which supports background automation. However, these are developer-oriented building blocks requiring the user to wire up their own automation/agent rather than a native built-in 'run autonomously in background' scheduler feature, and no hands-on evidence of an actual autonomous background automation running end-to-end. missing for 10: independent/hands-on validation of an autonomous background automation actually running, native no-code autonomous trigger/scheduling UI (vs. workflows requiring manual setup), and confirmation the MCP/agent integration operates unattended without human-in-the-loop.", "evidenceIds": [ "cal-com-docs-11", "cal-com-docs-12", "cal-com-docs-17", "cal-com-docs-30", "cal-com-docs-45", "cal-com-docs-46", "cal-com-probe-4" ] }, { "productId": "cal-com", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Cal.com's AI-related evidence describes exposing its API/MCP server so external AI agents and clients (e.g., Claude, other MCP clients) can call scheduling functions — it does not describe a built-in AI assistant embedded in the Cal.com product UI that a user can delegate tasks to. This is the inverse of the story (Cal.com as a tool for external agents, not an agent bundled inside Cal.com).", "evidenceIds": [ "cal-com-docs-11", "cal-com-docs-12", "cal-com-docs-30", "cal-com-docs-45", "cal-com-docs-49" ] }, { "productId": "cal-com", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Cal.com exposes a full REST API v2 (OAuth/API key auth, bookings, event types, schedules, webhooks) plus a documented CLI recommendation for agents that execute commands, enabling headless/CI automation of scheduling workflows. However, evidence is entirely first-party docs with no independent/hands-on confirmation of running it in CI pipelines, no CI-specific examples (e.g., GitHub Actions), and self-hosting/community reports raise friction concerns (broken docker builds, API not self-hostable) that could affect headless deployment reliability. missing for 10: independent CI/automation case study or hands-on verification, explicit CI pipeline examples, and confirmation that self-hosted headless API deployment works smoothly given community-reported self-hosting friction.", "evidenceIds": [ "cal-com-docs-13", "cal-com-docs-20", "cal-com-docs-45", "cal-com-docs-46", "cal-com-docs-12", "cal-com-comm-4", "cal-com-comm-11" ] }, { "productId": "cal-com", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Cal.com's AI-native positioning is entirely about exposing itself AS an MCP server/tool provider (mcp.cal.com, API v2 for agents) so that external AI agents can call Cal.com's scheduling tools — the evidence shows no agentic host/orchestration role within Cal.com where a user would plug external MCP servers into Cal.com itself to extend its own capabilities. This story describes the client-side 'consume other tools' direction, which is a different axis (and the inverse of what Cal.com's docs describe), so it is a category mismatch for this SaaS scheduling product's documented architecture.", "evidenceIds": [ "cal-com-docs-11", "cal-com-docs-12", "cal-com-docs-30", "cal-com-docs-49" ] }, { "productId": "cal-com", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com documents an official hosted MCP server (mcp.cal.com) plus a local instance option, explicitly letting AI clients manage bookings, event types, and schedules via natural language in any MCP-compatible client, corroborated by a probe confirming the docs page exists. missing for 10: independent hands-on community verification that the MCP server works reliably in practice.", "evidenceIds": [ "cal-com-docs-11", "cal-com-docs-30", "cal-com-docs-49", "cal-com-probe-4" ] }, { "productId": "cal-com", "storyId": "agentic-nl-commands", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com documents both a hosted MCP server (mcp.cal.com) and local instance explicitly for controlling bookings, event types, and schedules 'through natural language in any MCP-compatible client,' plus a dedicated agents.md doc for AI agents to check availability, create bookings, and manage event types via API/CLI. This is first-party documented and probe-confirmed (mcp-server doc live at HTTP 200), though there's no independent/community hands-on verification of NL command execution quality. Missing for 10: independent/hands-on evidence of natural-language command execution working reliably in practice.", "evidenceIds": [ "cal-com-docs-11", "cal-com-docs-30", "cal-com-docs-49", "cal-com-docs-12", "cal-com-docs-45", "cal-com-probe-4" ] }, { "productId": "cal-com", "storyId": "agentic-official-cli", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Cal.com's docs explicitly mention an official CLI for agentic/automation use ('use the official Cal.com CLI instead of calling the API directly'), confirming the capability exists, but the evidence pack contains no further detail on installation, command set, or independent verification. Missing for 10: CLI documentation/README, install instructions, command reference, and any hands-on or community confirmation of the CLI in use.", "evidenceIds": [ "cal-com-docs-45" ] }, { "productId": "cal-com", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com ships a comprehensive, well-documented public API v2 covering bookings, event types, schedules, webhooks, slots, and routing traces, with clear auth methods (OAuth, API key) and dedicated docs pages for AI agents/MCP usage. Community evidence corroborates self-hosting the API is possible, though probes found no discoverable OpenAPI spec file at standard paths. Missing for 10: a verifiable machine-readable OpenAPI/Swagger spec (probe found 404s at standard paths), and independent hands-on developer confirmation of the API's real-world reliability beyond vendor docs.", "evidenceIds": [ "cal-com-docs-13", "cal-com-docs-14", "cal-com-docs-20", "cal-com-docs-1", "cal-com-docs-3", "cal-com-docs-6", "cal-com-docs-5", "cal-com-docs-12", "cal-com-docs-46", "cal-com-comm-12", "cal-com-probe-3", "cal-com-probe-2" ] }, { "productId": "cal-com", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Cal.com supports OAuth 2 authentication with defined scopes (e.g., EVENT_TYPE_WRITE) and API keys manageable in settings, plus 'managed users' independent of a user's own account, which together suggest some scoping/isolation capability. However, there is no explicit documentation of a least-privilege credential system designed specifically for AI agents (e.g., granular per-action scopes, agent-specific key issuance, or expiring/limited-permission tokens). missing for 10: dedicated agent-scoped credential issuance flow, full list of available OAuth scopes, and independent confirmation that scoping is enforced in practice.", "evidenceIds": [ "cal-com-docs-13", "cal-com-docs-14", "cal-com-docs-60", "cal-com-docs-9", "cal-com-docs-47" ] }, { "productId": "cal-com", "storyId": "agentic-sdks", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Cal.com documents official SDK-like tooling for AI-native builders: a Platform SDK with React atoms and managed users, a full REST API v2 with OAuth/API-key auth, an official CLI recommended for agentic use, and a hosted/local MCP server for natural-language integration. However, evidence lacks a dedicated named client SDK package (e.g., JS/Python) with versioning/changelog, and OpenAPI spec endpoints return 404, undermining programmatic SDK generation claims; community feedback also flags self-hosted API access restrictions and docker/build friction. missing for 10: a discoverable OpenAPI/schema artifact, named official client SDK packages beyond React atoms, and independent hands-on developer corroboration of SDK reliability.", "evidenceIds": [ "cal-com-docs-9", "cal-com-docs-10", "cal-com-docs-36", "cal-com-docs-45", "cal-com-docs-11", "cal-com-docs-13", "cal-com-probe-3", "cal-com-comm-3", "cal-com-comm-12" ] }, { "productId": "cal-com", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com's API v2 has documented webhook creation with configurable subscriberUrl and a wide range of triggers (BOOKING_CREATED, BOOKING_RESCHEDULED, BOOKING_CANCELLED, etc.), enabling event-driven subscriptions well-suited to agentic/AI-native integration patterns, and this is reinforced by dedicated AI-agent docs and an official MCP server for programmatic access. Missing for 10: independent/hands-on confirmation of webhook reliability or delivery guarantees, and no evidence of webhook signature verification or retry semantics.", "evidenceIds": [ "cal-com-docs-5", "cal-com-docs-26", "cal-com-docs-42", "cal-com-docs-52", "cal-com-docs-60", "cal-com-docs-12", "cal-com-docs-11" ] }, { "productId": "cal-com", "storyId": "ai-meeting-time-optimization", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Cal.com's API supports querying mutual availability across multiple attendees via the 'by usernames only' dynamic event type, and its agents.md docs let AI agents check availability and create bookings, which gives a building block for finding open slots across calendars. However there is no evidence of any optimization logic that ranks or continuously re-evaluates the 'best' time (e.g., factoring preferences, meeting quality, or re-optimizing after changes) beyond returning available slots for manual/first-fit selection. Missing for 10: evidence of an AI/optimization algorithm scoring or ranking candidate times, evidence of continuous re-optimization as calendars change, and any documented 'best time' selection logic beyond raw slot listing.", "evidenceIds": [ "cal-com-docs-38", "cal-com-docs-12", "cal-com-docs-17", "cal-com-docs-50", "cal-com-docs-23" ] }, { "productId": "cal-com", "storyId": "ai-task-autoschedule", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Cal.com's API/MCP lets AI agents check availability, create bookings, and reschedule meetings (cal-com-docs-12, cal-com-docs-24, cal-com-docs-49), but there is no evidence of an AI system that autonomously blocks time for tasks/deadlines around a knowledge worker's existing meetings or automatically re-plans a schedule when things change — it's a booking/meeting API, not a task-time-blocking planner.", "evidenceIds": [ "cal-com-docs-12", "cal-com-docs-24", "cal-com-docs-49", "cal-com-docs-17" ] }, { "productId": "cal-com", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows extensive static API reference documentation (markdown pages for bookings, event types, webhooks, etc.) but no evidence of an interactive console or runnable code examples; a probe explicitly found no OpenAPI/Swagger spec at any standard location, suggesting no interactive playground exists. Missing for 10: an interactive API explorer/sandbox, evidence of runnable code snippets, or a Swagger/OpenAPI-based try-it-now interface.", "evidenceIds": [ "cal-com-probe-2", "cal-com-probe-3", "cal-com-docs-13", "cal-com-docs-14" ] }, { "productId": "cal-com", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "A direct probe of common OpenAPI spec paths (openapi.json, swagger.json, etc.) returned 404 on all candidates, and no documentation page or claimed-docs snippet references a downloadable OpenAPI/Swagger spec file—only human-readable API reference pages and llms.txt indices are evidenced.", "evidenceIds": [ "cal-com-probe-3", "cal-com-docs-13", "cal-com-probe-1", "cal-com-probe-2" ] }, { "productId": "cal-com", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no mention of a sandbox, staging, or test-mode environment for Cal.com's API, MCP server, or platform atoms — only production API keys, OAuth, and managed users are documented. Self-hosting (Cal.diy) is offered but is explicitly discouraged for production use and not framed as a sandbox for testing against a hosted instance, so it doesn't fulfill this story.", "evidenceIds": [ "cal-com-docs-13", "cal-com-docs-14", "cal-com-docs-9", "cal-com-gh-1", "cal-com-comm-15" ] }, { "productId": "cal-com", "storyId": "api-versioning-policy", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Cal.com's API is clearly versioned (all endpoints are under /v2/, and one auth method is explicitly marked 'Platform (Deprecated)'), showing some awareness of versioning and deprecation, but there is no dedicated deprecation policy page, no sunset timeline for v1, and no stated support window for deprecated endpoints/features. missing for 10: explicit documented deprecation policy (timelines, sunset process, migration guides between API versions), evidence of v1→v2 migration guidance, and any independent confirmation that deprecated endpoints are reliably maintained per a stated schedule.", "evidenceIds": [ "cal-com-docs-13", "cal-com-probe-2", "cal-com-docs-20" ] }, { "productId": "cal-com", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence describes single-resource CRUD operations (create one booking, reschedule one booking, create one event type, one webhook) via the API, but no bulk/batch endpoints (e.g., bulk booking creation, bulk cancellation, mass event-type updates) are documented anywhere in the pack.", "evidenceIds": [] }, { "productId": "cal-com", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Cal.com supports webhooks with configurable triggers (BOOKING_CREATED, BOOKING_PAID, BOOKING_CANCELLED, etc.) that fire actions on events, plus Zapier integration for further automation chains, which together enable rule-like 'if event X, do action Y' automation. However, this is trigger-based webhook automation rather than a native conditional rules engine (no evidence of if/then logic, filtering conditions, or multi-step workflow builder beyond routing forms). Missing for 10: evidence of a native conditional/rules engine with branching logic, non-webhook native workflow automation, and independent hands-on confirmation that webhook-triggered automations work reliably in practice.", "evidenceIds": [ "cal-com-docs-5", "cal-com-docs-26", "cal-com-docs-42", "cal-com-docs-52", "cal-com-intdir-7", "cal-com-docs-8", "cal-com-docs-53" ] }, { "productId": "cal-com", "storyId": "automation-scheduled-jobs", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Cal.com's API explicitly supports creating recurring bookings (`POST /v2/bookings` creates 'regular bookings, recurring bookings and instant bookings') and the platform has a native 'workflows' feature plus webhooks for automation triggers, and this API/webhook layer is documented as usable by AI agents and via the official MCP server. However, no evidence directly shows an AI agent invoking recurring-schedule creation through MCP/agent docs, nor detail on how recurring jobs are configured/managed beyond the one-line API mention. Missing for 10: hands-on/independent proof of an AI agent actually creating a recurring booking via MCP or the agents API, and deeper documentation of the 'workflows' automation feature.", "evidenceIds": [ "cal-com-docs-37", "cal-com-docs-28", "cal-com-docs-30", "cal-com-docs-49", "cal-com-docs-12", "cal-com-docs-5", "cal-com-docs-26" ] }, { "productId": "cal-com", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Cal.com is a scheduling platform; its evidence pack covers bookings, event types, webhooks, MCP/AI-agent integrations, and self-hosting, but nothing describes versioning, review workflows, or rollback of automations/workflows themselves. No changelog, audit trail, or undo mechanism for automation configurations is documented.", "evidenceIds": [] }, { "productId": "cal-com", "storyId": "booking-link-self-serve", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Cal.com's own docs directly state the exact value proposition: 'Share a booking link, connect your calendars, and let people pick a time without the back-and-forth,' backed by API/product features like available-slots lookup, event types, and scheduling configuration that make this work, and community feedback confirms real-world usage replacing manual scheduling (e.g. switching from Calendly due to UX). Missing for 10: independent hands-on verification of the live-availability booking flow itself (most corroboration is docs-based) and no dispute exists to weigh against.", "evidenceIds": [ "cal-com-docs-16", "cal-com-docs-28", "cal-com-docs-2", "cal-com-docs-6", "cal-com-comm-1" ] }, { "productId": "cal-com", "storyId": "booking-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com's API v2 docs explicitly document a webhook resource with triggers including BOOKING_CREATED, BOOKING_RESCHEDULED, BOOKING_CANCELLED, BOOKING_PAID, etc., configurable subscriberUrl and payload template, directly matching the story of real-time booking event notifications. Evidence is first-party docs only, without independent/hands-on confirmation of webhook delivery reliability. missing for 10: independent/hands-on verification of webhook delivery in production, details on retry/failure handling.", "evidenceIds": [ "cal-com-docs-5", "cal-com-docs-26", "cal-com-docs-42", "cal-com-docs-52", "cal-com-docs-60" ] }, { "productId": "cal-com", "storyId": "buffers-notice-limits", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers scheduling infrastructure (schedules, event types, webhooks, routing) but contains no documentation or mention of buffer times before/after meetings, minimum booking notice, daily booking caps, or date-range availability windows — the specific booking-protection controls this story asks about.", "evidenceIds": [] }, { "productId": "cal-com", "storyId": "collective-availability", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Cal.com explicitly lists 'collective' as one of its native scheduling types alongside round-robin, group and one-on-one, and its slots API supports checking availability across multiple hosts (e.g. dynamic/username-based slot queries for '2 or more people'), which is the mechanism needed to only surface times when every host is free. However, the evidence pack shows detailed configuration docs (priority/weight/host groups/CRM fallback) only for round-robin, with no equivalent documented detail on collective-event host requirements or slot-intersection logic. Missing for 10: explicit collective-event configuration API docs, independent/hands-on confirmation that slots correctly reflect all-hosts-free logic.", "evidenceIds": [ "cal-com-docs-28", "cal-com-docs-38", "cal-com-docs-15", "cal-com-docs-35" ] }, { "productId": "cal-com", "storyId": "crm-automation-integrations", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Cal.com exposes webhooks (BOOKING_CREATED, BOOKING_PAID, BOOKING_RESCHEDULED, etc.) and a general-purpose API/OAuth layer that could feed a CRM or Zapier via automation, and routing-form docs reference 'CRM lookups' and 'CRM fallback' in host-selection logic, plus an 'app store of integrations' is claimed. However, there is no direct evidence of a native Salesforce, HubSpot, or Zapier app/connector, nor of an out-of-the-box no-code integration flow — only the building blocks (webhooks + API) that a sales lead would need someone to wire up. Missing for 10: explicit documentation or listing of a Salesforce/HubSpot/Zapier native app, an official Zapier integration page, and any hands-on/independent confirmation that bookings actually sync into these CRMs.", "evidenceIds": [ "cal-com-docs-5", "cal-com-docs-26", "cal-com-docs-42", "cal-com-docs-8", "cal-com-docs-28", "cal-com-docs-20" ] }, { "productId": "cal-com", "storyId": "cross-calendar-blocking-sync", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Cal.com's docs mention connecting your calendars so people can book around your availability (cal-com-docs-16, cal-com-docs-28), implying calendar sync is core to the platform, but the evidence pack never details two-way busy-block sync across multiple work/personal calendars, conflict-checking logic, or write-back behavior. missing for 10: explicit documentation of multi-calendar busy-block overlay/sync, two-way write-back, and any hands-on confirmation that it keeps personal and work calendars in step.", "evidenceIds": [ "cal-com-docs-16", "cal-com-docs-28" ] }, { "productId": "cal-com", "storyId": "event-type-controls", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Docs confirm event types support multiple durations (docs-4), custom locations including video/conferencing apps (docs-7, docs-21), custom booking-form questions/fields (docs-40, docs-59), and confirmation/scheduling logic including round-robin and requested/accepted booking states (docs-25, docs-58). This covers durations, locations, custom questions, and confirmation rules comprehensively via first-party API docs. Missing for 10: independent/hands-on verification of the full event-type creation UI flow beyond docs.", "evidenceIds": [ "cal-com-docs-4", "cal-com-docs-7", "cal-com-docs-21", "cal-com-docs-40", "cal-com-docs-59", "cal-com-docs-25", "cal-com-docs-58", "cal-com-docs-34" ] }, { "productId": "cal-com", "storyId": "focus-time-defense", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Cal.com's evidence covers booking, rescheduling, scheduling APIs, webhooks, and AI-agent integration, but nothing describes an autonomous system that 'defends' recurring focus time/habit blocks by detecting conflicts and proactively rescheduling them rather than dropping them. Reschedule endpoints exist but are manually/API-triggered, not an autonomous focus-time-protection feature.", "evidenceIds": [ "cal-com-docs-3", "cal-com-docs-24", "cal-com-docs-27", "cal-com-docs-37" ] }, { "productId": "cal-com", "storyId": "free-tier-individual", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "A Cal.com cofounder explicitly states in community discussion that everything that is Calendly's paid 'Pro' tier is free on Cal.com, and general docs describe core one-on-one scheduling/booking-link functionality that would presumably be available without payment; however, other community comments note certain paid add-ons (e.g., $29/mo premium usernames) exist, and there is no first-party pricing-page or plan-limits documentation in the pack confirming exactly what's free. Missing for 10: an official pricing/plan page from Cal.com detailing which core scheduling features are free, and independent hands-on confirmation of using a booking link fully free.", "evidenceIds": [ "cal-com-comm-10", "cal-com-docs-16", "cal-com-docs-28", "cal-com-docs-43", "cal-com-comm-6" ] }, { "productId": "cal-com", "storyId": "multi-calendar-conflict-check", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The evidence pack only contains a single generic line ('connect your calendars... pick a time without the back-and-forth') suggesting calendar sync exists, but nothing details Google/Outlook/Apple-specific connections or explicit cross-calendar conflict-checking logic. Missing for 10: explicit documentation of Google/Outlook/Apple calendar integrations, description of two-way sync/conflict-avoidance mechanics, and independent corroboration that double-booking is prevented across multiple connected calendars.", "evidenceIds": [ "cal-com-docs-16" ] }, { "productId": "cal-com", "storyId": "openness-api-parity", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Cal.com's API v2 covers most UI capabilities (bookings, event types, schedules, webhooks, routing, conferencing apps, managed users) and docs explicitly frame the API as AI-agent-ready, plus an MCP server exposes these operations to AI clients. However, evidence doesn't confirm full UI parity (e.g., no mention of API access to billing/compliance settings, app marketplace management, or admin/org settings via API), and an official OpenAPI spec could not be found (404s), making completeness hard to verify. missing for 10: confirmed full parity for admin/org-level settings and marketplace app configuration via API, a published OpenAPI schema, independent hands-on confirmation that all UI actions are API-reachable.", "evidenceIds": [ "cal-com-docs-12", "cal-com-docs-17", "cal-com-docs-30", "cal-com-docs-45", "cal-com-docs-9", "cal-com-docs-6", "cal-com-docs-7", "cal-com-docs-8", "cal-com-probe-3", "cal-com-probe-4" ] }, { "productId": "cal-com", "storyId": "openness-full-export", "verdict": "disputed", "quality": 3, "confidence": "medium", "rationale": "Cal.com documents an open API (auth via key/OAuth) and an MIT-licensed self-host fork (Cal.diy) that could in principle let a user pull out their data and run independently, but there is no explicit 'export all my data' feature documented, and hands-on community reports directly contradict the openness/exit narrative: users say self-hosting the API isn't really possible ('there's no way to self-host the API... AGPL is a very restrictive license'), and more recent reports describe a bait-and-switch where Cal.diy/self-hosted docker images were pulled back and restricted to 'personal, non-production use,' with users abandoning self-hosting as a result. missing for 10: a documented data-export/portability feature, and confirmation that self-hosting reliably preserves full data ownership without restriction.", "evidenceIds": [ "cal-com-gh-1", "cal-com-gh-2", "cal-com-docs-13", "cal-com-docs-20", "cal-com-comm-3", "cal-com-comm-14", "cal-com-comm-15", "cal-com-comm-18", "cal-com-comm-19" ] }, { "productId": "cal-com", "storyId": "openness-open-license", "verdict": "disputed", "quality": 5, "confidence": "medium", "rationale": "Cal.com does publish source under an open license — Cal.diy is documented as '100% MIT-licensed' with no proprietary Enterprise Edition and 'no license key required' (cal-com-gh-1/4/5), and llms.txt calls the 'self-hostable MIT edition' a core differentiator (cal-com-docs-43/48). However, hands-on community reports concretely contradict how open/usable that source is in practice: Cal.com stopped shipping public Docker images and now tells self-hosters 'It is strictly recommended for personal, non-production use' — a stated reversal from prior claims that self-hosting gave 'full ownership of infrastructure' (cal-com-comm-14, cal-com-comm-15, cal-com-comm-18, cal-com-comm-19), and the flagship cal.com repo itself is under a restrictive AGPL license per commenters (cal-com-comm-3). missing for 10: independent verification that the MIT Cal.diy source is fully buildable/production-usable, and reconciliation of the AGPL vs MIT licensing claims across the main repo and the fork.", "evidenceIds": [ "cal-com-gh-1", "cal-com-gh-4", "cal-com-gh-5", "cal-com-docs-43", "cal-com-docs-48", "cal-com-comm-3", "cal-com-comm-14", "cal-com-comm-15", "cal-com-comm-18", "cal-com-comm-19" ] }, { "productId": "cal-com", "storyId": "openness-self-host", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "Vendor and GitHub evidence claim Cal.diy is a 100% MIT-licensed, no-license-key-required fork designed for full self-hosting control, but multiple hands-on community reports concretely contradict this: users report the vendor stopped shipping public Docker images (requiring manual builds), official docs now say the OSS edition is 'strictly recommended for personal, non-production use,' and one commenter states you can't actually self-host the API without paying, calling it effectively 'self-hosting the UI' only, prompting accusations of a bait-and-switch from long-time self-hosters. A few users do report successfully self-hosting both API and DB, so the capability partially exists but is actively disputed. Missing for 10: a stable, vendor-provided production-grade self-hosting path (Docker images, full API) without contested community reports of regressions or non-production caveats.", "evidenceIds": [ "cal-com-gh-1", "cal-com-gh-2", "cal-com-gh-4", "cal-com-gh-5", "cal-com-comm-3", "cal-com-comm-4", "cal-com-comm-11", "cal-com-comm-12", "cal-com-comm-14", "cal-com-comm-15", "cal-com-comm-16", "cal-com-comm-18", "cal-com-comm-19" ] }, { "productId": "cal-com", "storyId": "payments-on-booking", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Cal.com's docs list \"payments\" among core platform capabilities (cal-com-docs-28/48) and webhook events explicitly include BOOKING_PAYMENT_INITIATED and BOOKING_PAID, confirming a payment-at-booking flow exists (cal-com-docs-5/26/42). However, the evidence pack lacks any Stripe-specific setup docs, API fields for configuring a paid event type, or a hands-on confirmation that a booking actually triggers a Stripe charge. Missing for 10: dedicated Stripe/payment-app integration docs, API examples showing price/currency fields on event-type creation, and independent/hands-on verification of a successful paid booking flow.", "evidenceIds": [ "cal-com-docs-28", "cal-com-docs-48", "cal-com-docs-5", "cal-com-docs-26", "cal-com-docs-42" ] }, { "productId": "cal-com", "storyId": "privacy-data-residency", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Cal.com does not document a data-residency/region-selection feature for its hosted SaaS product, but it does offer self-hosting (Cal.diy, MIT-licensed, 'full control over their scheduling infrastructure') as the mechanism by which a user could choose where data lives, and llms.txt cites GDPR/CCPA/HIPAA compliance as differentiators. However community evidence shows self-hosting is troubled (no self-hostable API per cal-com-comm-3, docker image friction cal-com-comm-4/11, and a documented 'bait and switch' restricting Cal.diy to non-production use cal-com-comm-14/15), undercutting reliability of this as a residency-control path. Missing for 10: an explicit region/data-residency selection setting in the hosted product, first-party docs describing where data centers are located, and confirmation that self-hosting reliably satisfies residency requirements without the documented friction.", "evidenceIds": [ "cal-com-gh-1", "cal-com-gh-2", "cal-com-docs-44", "cal-com-docs-43", "cal-com-comm-3", "cal-com-comm-14", "cal-com-comm-15" ] }, { "productId": "cal-com", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Cal.com is a scheduling platform, not an AI model provider or AI product with training data policies; the evidence pack shows only scheduling/API/compliance features (GDPR, SOC2, HIPAA) with no mention of AI model training opt-outs. This axis is a category error for a scheduling infrastructure product.", "evidenceIds": [] }, { "productId": "cal-com", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains only a generic compliance claim (GDPR/CCPA/SOC2/HIPAA) with no concrete documentation of data retention policies, deletion APIs, or AI-agent-accessible controls to purge or manage stored booking/user data. No endpoint or workflow is shown for an AI-native user to actually control retention windows or trigger deletion.", "evidenceIds": [ "cal-com-docs-44" ] }, { "productId": "cal-com", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Cal.com is a scheduling SaaS/platform, and the evidence pack has no mention of telemetry opt-out or usage-tracking controls; this axis is really an AI-agent/tool privacy-posture question about a client SDK or agent framework, not a fair question for this kind of scheduling product's evidence pack. Given no product feature ever surfaces around telemetry toggles, treat as category mismatch rather than a documented absence.", "evidenceIds": [] }, { "productId": "cal-com", "storyId": "reminders-noshow-workflows", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence only indirectly supports this: llms.txt lists 'workflows' as a product capability and mentions 'no-show calculations' in round-robin config, and webhooks (BOOKING_CREATED/RESCHEDULED/CANCELLED) plus a Zapier app that 'automates workflows when a booking is created, rescheduled, cancelled' could be used to build reminder/follow-up sequences. However, no evidence explicitly documents built-in automated email/SMS reminder sequences targeting no-show reduction. Missing for 10: dedicated docs on the Workflows feature's reminder/SMS templates, timing/triggers configuration, and any data or claims about no-show reduction impact.", "evidenceIds": [ "cal-com-docs-28", "cal-com-docs-41", "cal-com-docs-26", "cal-com-intdir-7" ] }, { "productId": "cal-com", "storyId": "reschedule-cancel-flows", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com documents reschedule/cancel flows directly on bookings (accepted/pending statuses), webhooks firing on BOOKING_RESCHEDULED/BOOKING_CANCELLED for downstream sync, calendar connections (Google, Apple, etc.) and conferencing apps that update everywhere, plus scheduling policies (schedules, round-robin configs, custom booking fields) enforced at booking time. This covers the core invitee self-service reschedule/cancel plus calendar sync and policy enforcement described in the docs. Missing for 10: no independent/hands-on confirmation that invitee-facing reschedule/cancel links actually work end-to-end in production, and no explicit documentation of the invitee-facing confirmation-page UI behavior itself (only API-level reschedule endpoint is evidenced).", "evidenceIds": [ "cal-com-docs-3", "cal-com-docs-24", "cal-com-docs-39", "cal-com-docs-58", "cal-com-docs-5", "cal-com-docs-26", "cal-com-docs-42", "cal-com-docs-7", "cal-com-docs-21", "cal-com-docs-55", "cal-com-docs-6", "cal-com-docs-27", "cal-com-docs-41", "cal-com-docs-25" ] }, { "productId": "cal-com", "storyId": "round-robin-distribution", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Cal.com's API documents full round-robin scheduling configuration with per-host priority, weight, group assignment, weights toggle, lead threshold, no-show calculations, and CRM fallback (cal-com-docs-15/25/41), plus llms.txt confirms round-robin scheduling as a core product feature (cal-com-docs-28). This directly matches the sales-lead need for fair, weighted lead distribution. Missing for 10: independent/hands-on verification of round-robin fairness in practice and no UI-level walkthrough evidence beyond API docs.", "evidenceIds": [ "cal-com-docs-15", "cal-com-docs-25", "cal-com-docs-41", "cal-com-docs-28", "cal-com-docs-35", "cal-com-docs-51" ] }, { "productId": "cal-com", "storyId": "routing-forms-qualify", "verdict": "full", "quality": 6, "confidence": "medium", "rationale": "Cal.com's docs explicitly list routing forms as a core feature (docs-28) and expose a dedicated API for tracing 'how the booking was routed through routing forms, CRM lookups, and host selection logic' (cal-com-docs-8), confirming invitee answers drive routing decisions. Team scheduling configs also support round-robin host selection with priority/weight/lead-threshold/CRM fallback (cal-com-docs-15/25/41), reinforcing routing-to-right-person capability. Missing for 10: no detailed documentation of the routing form builder UI itself (question types, conditional branching rules) or independent/hands-on confirmation of routing form setup and accuracy.", "evidenceIds": [ "cal-com-docs-8", "cal-com-docs-28", "cal-com-docs-15", "cal-com-docs-25", "cal-com-docs-41" ] }, { "productId": "cal-com", "storyId": "scheduling-rest-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Cal.com provides extensive documented REST API v2 endpoints for creating/rescheduling bookings, creating event types, availability schedules, webhooks, and scheduling configuration, plus authentication via OAuth/API keys, directly enabling developers to build scheduling into their own product. missing for 10: no independently discoverable OpenAPI/swagger spec (probe found 404s) and no hands-on third-party developer corroboration of API reliability beyond vendor docs.", "evidenceIds": [ "cal-com-docs-1", "cal-com-docs-4", "cal-com-docs-6", "cal-com-docs-23", "cal-com-docs-24", "cal-com-docs-13", "cal-com-docs-20", "cal-com-docs-42", "cal-com-probe-3" ] }, { "productId": "cal-com", "storyId": "self-host-scheduling-engine", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "Cal.com ships an MIT-licensed, no-license-key-required fork (Cal.diy) explicitly marketed for self-hosters (cal-com-gh-1/2/3/4/5), but hands-on community reports concretely contradict full self-hosting viability: the vendor reportedly stopped providing public Docker images (requiring users to build from source themselves) and now recommends the OSS edition 'strictly for personal, non-production use' after previously advertising full infrastructure ownership (cal-com-comm-14, cal-com-comm-15, cal-com-comm-19), and earlier reports describe broken/undocumented docker-compose setups and API access requiring a hosted paid service (cal-com-comm-3, cal-com-comm-4, cal-com-comm-11), though at least one user reports successfully self-hosting both API and DB (cal-com-comm-12). missing for 10: a consistent, current first-party guarantee of a working container image and full production-grade self-host path that isn't contradicted by these recent community reports.", "evidenceIds": [ "cal-com-gh-1", "cal-com-gh-2", "cal-com-gh-3", "cal-com-gh-4", "cal-com-gh-5", "cal-com-comm-3", "cal-com-comm-4", "cal-com-comm-11", "cal-com-comm-12", "cal-com-comm-14", "cal-com-comm-15", "cal-com-comm-19" ] }, { "productId": "cal-com", "storyId": "timezone-safe-booking", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no documentation or mention of timezone auto-detection, timezone display to invitees, or DST handling — only generic booking-link and API/event-type documentation. This is a fair and applicable axis for a scheduling product, but nothing in the pack substantiates it. Missing for 10: any docs on invitee timezone detection, timezone conversion display, or DST-safe scheduling logic.", "evidenceIds": [] }, { "productId": "cal-com", "storyId": "transparent-seat-pricing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no published pricing page, tier comparison, or per-seat cost breakdown for Cal.com; only scattered community mentions of a $29/month premium username add-on and a cofounder claim that 'everything PRO on Calendly is free,' neither of which constitutes documented per-seat tier pricing.", "evidenceIds": [ "cal-com-comm-6", "cal-com-comm-10", "cal-com-comm-2" ] }, { "productId": "cal-com", "storyId": "video-conferencing-links", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Docs explicitly state every booking gets a location, defaulting to Cal Video, and can be pointed at Zoom, Microsoft Teams, or Google Meet once the app is connected — matching the story exactly. This is first-party documented core functionality with clear API support for conferencing app connections. Missing for 10: independent hands-on confirmation of the automatic link-generation flow in production use.", "evidenceIds": [ "cal-com-docs-7", "cal-com-docs-21", "cal-com-docs-28" ] }, { "productId": "cal-com", "storyId": "website-embed", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack lacks any explicit documentation of an embed.js-style snippet supporting inline, popup, and floating widget modes. It only mentions React 'atoms' for building custom scheduling UI in an app (cal-com-docs-10, cal-com-docs-36, cal-com-docs-54), which is a different integration method (framework components, not a drop-in snippet) and requires managed users rather than a simple embed code. Missing for 10: documented embed.js snippet, inline/popup/floating-button embed modes, and any non-React (plain HTML/JS) usage example.", "evidenceIds": [ "cal-com-docs-10", "cal-com-docs-36", "cal-com-docs-54" ] }, { "productId": "cal-com", "storyId": "working-hours-overrides", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Cal.com docs explicitly describe creating schedules with working hours ('Create a schedule for the authenticated user... available at specific times'), and the scheduling configuration endpoint references advanced availability settings; the platform is widely known for date overrides and OOO via its UI, and the API-level schedule creation endpoint supports these core scheduling primitives. Missing for 10: explicit documentation snippet showing date-override and out-of-office API/UI fields, and independent hands-on confirmation of these specific sub-features beyond schedule creation.", "evidenceIds": [ "cal-com-docs-6", "cal-com-docs-27", "cal-com-docs-25", "cal-com-docs-41", "cal-com-docs-28" ] }, { "productId": "calendly", "storyId": "agent-books-meeting", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-5", "calendly-docs-6", "calendly-docs-24", "calendly-docs-25", "calendly-docs-34", "calendly-docs-35", "calendly-docs-7", "calendly-probe-3" ] }, { "productId": "calendly", "storyId": "agent-scheduling-tool", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-2", "calendly-docs-5", "calendly-docs-6", "calendly-docs-34", "calendly-docs-35", "calendly-docs-45", "calendly-probe-3", "calendly-docs-24" ] }, { "productId": "calendly", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-probe-1", "calendly-probe-2", "calendly-docs-2" ] }, { "productId": "calendly", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-58", "calendly-docs-18", "calendly-docs-27", "calendly-docs-28" ] }, { "productId": "calendly", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-12", "calendly-docs-13", "calendly-docs-14", "calendly-docs-7", "calendly-docs-11", "calendly-docs-35", "calendly-docs-45", "calendly-docs-25" ] }, { "productId": "calendly", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-19", "calendly-docs-27", "calendly-docs-58" ] }, { "productId": "calendly", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-3", "calendly-docs-52", "calendly-docs-6", "calendly-docs-25", "calendly-docs-7", "calendly-docs-23", "calendly-docs-30" ] }, { "productId": "calendly", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-2", "calendly-docs-5", "calendly-docs-34", "calendly-docs-35", "calendly-docs-45", "calendly-probe-3" ] }, { "productId": "calendly", "storyId": "agentic-nl-commands", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-5", "calendly-docs-21", "calendly-docs-2", "calendly-docs-27", "calendly-docs-34", "calendly-docs-35", "calendly-probe-3" ] }, { "productId": "calendly", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-52", "calendly-docs-53", "calendly-docs-54", "calendly-probe-3" ] }, { "productId": "calendly", "storyId": "agentic-public-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-1", "calendly-docs-3", "calendly-docs-4", "calendly-docs-5", "calendly-docs-6", "calendly-docs-7", "calendly-docs-52", "calendly-docs-53", "calendly-docs-54", "calendly-docs-34", "calendly-docs-35", "calendly-probe-1", "calendly-probe-3" ] }, { "productId": "calendly", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-3", "calendly-docs-4", "calendly-docs-30", "calendly-docs-31", "calendly-docs-34" ] }, { "productId": "calendly", "storyId": "agentic-sdks", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-52", "calendly-docs-53", "calendly-docs-54", "calendly-docs-3", "calendly-docs-4", "calendly-docs-34", "calendly-probe-3" ] }, { "productId": "calendly", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-7", "calendly-docs-23", "calendly-docs-54", "calendly-docs-55" ] }, { "productId": "calendly", "storyId": "ai-meeting-time-optimization", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-49", "calendly-docs-27", "calendly-docs-19", "calendly-docs-32", "calendly-comm-13", "calendly-comm-6" ] }, { "productId": "calendly", "storyId": "ai-task-autoschedule", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-19", "calendly-docs-27", "calendly-docs-58", "calendly-docs-12", "calendly-docs-14" ] }, { "productId": "calendly", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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).", "evidenceIds": [] }, { "productId": "calendly", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-52", "calendly-docs-53", "calendly-docs-54", "calendly-probe-1", "calendly-probe-2" ] }, { "productId": "calendly", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-52" ] }, { "productId": "calendly", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-6", "calendly-docs-35", "calendly-docs-45", "calendly-docs-52", "calendly-docs-7" ] }, { "productId": "calendly", "storyId": "automation-rules-engine", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-12", "calendly-docs-13", "calendly-docs-14", "calendly-docs-11", "calendly-docs-7", "calendly-docs-23", "calendly-docs-55" ] }, { "productId": "calendly", "storyId": "automation-scheduled-jobs", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "calendly-docs-12", "calendly-docs-13", "calendly-docs-14", "calendly-docs-7", "calendly-docs-23" ] }, { "productId": "calendly", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "booking-link-self-serve", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-16", "calendly-docs-15", "calendly-docs-41", "calendly-docs-49", "calendly-docs-36", "calendly-comm-2", "calendly-comm-3", "calendly-comm-6", "calendly-comm-13" ] }, { "productId": "calendly", "storyId": "booking-webhooks", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-7", "calendly-docs-23", "calendly-docs-54", "calendly-docs-55" ] }, { "productId": "calendly", "storyId": "buffers-notice-limits", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-15", "calendly-docs-42", "calendly-comm-15" ] }, { "productId": "calendly", "storyId": "collective-availability", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "calendly-docs-56", "calendly-docs-38", "calendly-docs-17", "calendly-comm-6" ] }, { "productId": "calendly", "storyId": "crm-automation-integrations", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "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).", "evidenceIds": [ "calendly-docs-10", "calendly-docs-43", "calendly-docs-44", "calendly-docs-7", "calendly-docs-23", "calendly-docs-52", "calendly-docs-54" ] }, { "productId": "calendly", "storyId": "cross-calendar-blocking-sync", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-15", "calendly-docs-42", "calendly-docs-49", "calendly-comm-6", "calendly-comm-10" ] }, { "productId": "calendly", "storyId": "event-type-controls", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-16", "calendly-docs-56", "calendly-docs-45", "calendly-docs-38", "calendly-docs-42", "calendly-comm-9" ] }, { "productId": "calendly", "storyId": "focus-time-defense", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "free-tier-individual", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-40", "calendly-docs-60", "calendly-comm-2", "calendly-comm-3", "calendly-comm-17" ] }, { "productId": "calendly", "storyId": "multi-calendar-conflict-check", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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).", "evidenceIds": [ "calendly-docs-15", "calendly-docs-42", "calendly-docs-49", "calendly-comm-6", "calendly-comm-13", "calendly-comm-10" ] }, { "productId": "calendly", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-1", "calendly-docs-5", "calendly-docs-6", "calendly-docs-35", "calendly-docs-45", "calendly-docs-52", "calendly-docs-53", "calendly-docs-54", "calendly-docs-11", "calendly-docs-12", "calendly-docs-29" ] }, { "productId": "calendly", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-1", "calendly-docs-52" ] }, { "productId": "calendly", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "calendly", "storyId": "openness-self-host", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "calendly", "storyId": "payments-on-booking", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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).", "evidenceIds": [ "calendly-docs-29", "calendly-docs-37" ] }, { "productId": "calendly", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "reminders-noshow-workflows", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-12", "calendly-docs-13", "calendly-docs-14", "calendly-docs-57" ] }, { "productId": "calendly", "storyId": "reschedule-cancel-flows", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-54", "calendly-docs-7", "calendly-docs-23", "calendly-docs-15", "calendly-docs-42", "calendly-docs-49", "calendly-docs-14" ] }, { "productId": "calendly", "storyId": "round-robin-distribution", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-38", "calendly-docs-17", "calendly-docs-26", "calendly-docs-10", "calendly-comm-7" ] }, { "productId": "calendly", "storyId": "routing-forms-qualify", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-10", "calendly-docs-11", "calendly-docs-17", "calendly-docs-26", "calendly-docs-43", "calendly-docs-44" ] }, { "productId": "calendly", "storyId": "scheduling-rest-api", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-3", "calendly-docs-4", "calendly-docs-7", "calendly-docs-9", "calendly-docs-24", "calendly-docs-52", "calendly-docs-54", "calendly-docs-55" ] }, { "productId": "calendly", "storyId": "self-host-scheduling-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "calendly", "storyId": "timezone-safe-booking", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "calendly", "storyId": "transparent-seat-pricing", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-18", "calendly-docs-19", "calendly-docs-29", "calendly-docs-32", "calendly-docs-37", "calendly-docs-38", "calendly-docs-39", "calendly-docs-51", "calendly-docs-58", "calendly-docs-59", "calendly-comm-7", "calendly-comm-8" ] }, { "productId": "calendly", "storyId": "video-conferencing-links", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-18", "calendly-docs-51", "calendly-docs-39", "calendly-docs-58" ] }, { "productId": "calendly", "storyId": "website-embed", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "calendly-docs-8", "calendly-docs-22", "calendly-docs-33", "calendly-docs-36", "calendly-docs-46", "calendly-docs-53" ] }, { "productId": "calendly", "storyId": "working-hours-overrides", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "calendly-docs-15", "calendly-docs-42", "calendly-docs-49" ] }, { "productId": "motion", "storyId": "agent-books-meeting", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-29", "motion-docs-6", "motion-docs-7" ] }, { "productId": "motion", "storyId": "agent-scheduling-tool", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-29", "motion-docs-2", "motion-docs-28" ] }, { "productId": "motion", "storyId": "agentic-agent-docs", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-34", "motion-docs-2", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "agentic-ai-insights", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-4", "motion-docs-11", "motion-docs-15", "motion-docs-39", "motion-docs-40", "motion-docs-22", "motion-docs-23" ] }, { "productId": "motion", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-3", "motion-docs-10", "motion-docs-12", "motion-docs-14", "motion-docs-16", "motion-docs-23" ] }, { "productId": "motion", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-10", "motion-docs-14", "motion-docs-15", "motion-docs-22", "motion-docs-23", "motion-docs-39" ] }, { "productId": "motion", "storyId": "agentic-headless", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-18", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-28", "motion-docs-29", "motion-docs-18" ] }, { "productId": "motion", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-17", "motion-docs-16", "motion-docs-20", "motion-docs-23" ] }, { "productId": "motion", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-2", "motion-docs-29" ] }, { "productId": "motion", "storyId": "agentic-public-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-29", "motion-docs-37" ] }, { "productId": "motion", "storyId": "agentic-sdks", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-2", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-18", "motion-docs-29" ] }, { "productId": "motion", "storyId": "ai-meeting-time-optimization", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-3", "motion-docs-8", "motion-docs-27", "motion-docs-9" ] }, { "productId": "motion", "storyId": "ai-task-autoschedule", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-3", "motion-docs-10", "motion-docs-11", "motion-docs-12", "motion-docs-17", "motion-docs-39" ] }, { "productId": "motion", "storyId": "api-interactive-docs", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-2", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "api-machine-spec", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-29", "motion-docs-2", "motion-docs-28" ] }, { "productId": "motion", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-29", "motion-docs-2" ] }, { "productId": "motion", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-14", "motion-docs-15", "motion-docs-38", "motion-docs-18", "motion-docs-23" ] }, { "productId": "motion", "storyId": "automation-scheduled-jobs", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-12", "motion-docs-1", "motion-docs-23", "motion-docs-29" ] }, { "productId": "motion", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "booking-link-self-serve", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-5", "motion-docs-27", "motion-docs-7", "motion-docs-8", "motion-docs-6" ] }, { "productId": "motion", "storyId": "booking-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-29", "motion-docs-5" ] }, { "productId": "motion", "storyId": "buffers-notice-limits", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-6", "motion-docs-38", "motion-docs-5", "motion-docs-27" ] }, { "productId": "motion", "storyId": "collective-availability", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "crm-automation-integrations", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-18", "motion-docs-1", "motion-docs-29", "motion-docs-33" ] }, { "productId": "motion", "storyId": "cross-calendar-blocking-sync", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-8", "motion-docs-3" ] }, { "productId": "motion", "storyId": "event-type-controls", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-7", "motion-docs-5", "motion-docs-27", "motion-docs-6", "motion-docs-38" ] }, { "productId": "motion", "storyId": "focus-time-defense", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-3", "motion-docs-10", "motion-docs-11", "motion-docs-12", "motion-docs-39" ] }, { "productId": "motion", "storyId": "free-tier-individual", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-24", "motion-docs-30", "motion-docs-32" ] }, { "productId": "motion", "storyId": "multi-calendar-conflict-check", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-8", "motion-docs-3", "motion-docs-6", "motion-docs-38" ] }, { "productId": "motion", "storyId": "openness-api-parity", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-28", "motion-docs-29" ] }, { "productId": "motion", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-29" ] }, { "productId": "motion", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "motion", "storyId": "openness-self-host", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "motion", "storyId": "payments-on-booking", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-5", "motion-docs-27" ] }, { "productId": "motion", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "reminders-noshow-workflows", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-7", "motion-docs-9", "motion-docs-21" ] }, { "productId": "motion", "storyId": "reschedule-cancel-flows", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-5", "motion-docs-6", "motion-docs-27", "motion-docs-38" ] }, { "productId": "motion", "storyId": "round-robin-distribution", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "routing-forms-qualify", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "motion", "storyId": "scheduling-rest-api", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-1", "motion-docs-29", "motion-docs-2", "motion-docs-28", "motion-docs-5" ] }, { "productId": "motion", "storyId": "self-host-scheduling-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "motion", "storyId": "timezone-safe-booking", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "motion", "storyId": "transparent-seat-pricing", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-24", "motion-docs-30", "motion-docs-32", "motion-docs-25", "motion-docs-35", "motion-docs-36", "motion-docs-37", "motion-docs-41" ] }, { "productId": "motion", "storyId": "video-conferencing-links", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "motion-docs-9", "motion-docs-20", "motion-docs-8" ] }, { "productId": "motion", "storyId": "website-embed", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "motion-docs-5", "motion-docs-27" ] }, { "productId": "motion", "storyId": "working-hours-overrides", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "agent-books-meeting", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a public API or MCP server for programmatic booking/rescheduling/cancellation; the product only documents dashboard, browser extension, and in-app AI assistant features. Probes for an OpenAPI spec returned 404s, and no API/MCP docs appear anywhere in the evidence pack.", "evidenceIds": [ "reclaim-probe-3", "reclaim-docs-11", "reclaim-docs-51" ] }, { "productId": "reclaim", "storyId": "agent-scheduling-tool", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an MCP server, tool-calling API, or agent-facing surface exposing availability/bookings/event types; probes for OpenAPI/spec endpoints returned 404s, and the AI Assistant feature is a chat UI for the human user, not an agent tool interface.", "evidenceIds": [ "reclaim-docs-11", "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 7, "confidence": "high", "rationale": "A direct probe confirms Reclaim's help center serves a live llms.txt at https://help.reclaim.ai/llms.txt returning HTTP 200 with structured markdown links to docs, directly satisfying the story's core ask. Missing for 10: no per-page .md docs variant (404 on docs-md probe) and no independent community confirmation of agents actually consuming the llms.txt file.", "evidenceIds": [ "reclaim-probe-1", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "agentic-ai-insights", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Reclaim documents an AI Assistant chat for planning/prioritizing/optimizing schedules, a Schedule Assistant that 'highlights what needs attention and suggests what to do next', and automatic time analytics across meetings/tasks/work-life balance — all AI-generated insights derived from the user's calendar data inside the product. Missing for 10: independent/hands-on corroboration of the insight quality, and more detail on the analytics/insights UI beyond marketing copy.", "evidenceIds": [ "reclaim-docs-11", "reclaim-docs-51", "reclaim-docs-6", "reclaim-docs-36", "reclaim-docs-33" ] }, { "productId": "reclaim", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Reclaim.ai runs continuous background automations—auto-scheduling/rescheduling Tasks, Habits, Focus Time, buffers, and travel time without manual reshuffling—which is a real form of autonomous, persistent automation, and community testimonials corroborate this behavior (e.g., proactive scheduling, hands-off operation). However, this is calendar-domain automation rather than general-purpose 'agentic' automation across arbitrary tasks/tools, and at least one user reported a sync automation not working as expected. missing for 10: evidence of broader/cross-domain autonomous automations beyond calendar scheduling, a clear framework for user-defined custom automations/triggers, and stronger independent verification of reliability at scale.", "evidenceIds": [ "reclaim-docs-34", "reclaim-docs-30", "reclaim-docs-12", "reclaim-docs-14", "reclaim-docs-33", "reclaim-comm-3", "reclaim-comm-5" ] }, { "productId": "reclaim", "storyId": "agentic-builtin-assistant", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Reclaim ships a built-in AI Assistant chat feature that lets users delegate planning, prioritizing, and schedule optimization tasks, plus a 'Schedule Assistant' control center that surfaces suggested actions and lets users preview/deploy changes. This matches the story of delegating tasks to an in-product AI assistant. Missing for 10: independent/hands-on user reports specifically about the chat AI Assistant (community evidence predates this feature and focuses on general auto-scheduling), and detail on the full scope of tasks it can autonomously execute versus merely suggest.", "evidenceIds": [ "reclaim-docs-11", "reclaim-docs-51", "reclaim-docs-52" ] }, { "productId": "reclaim", "storyId": "agentic-headless", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Reclaim.ai is a calendar-scheduling SaaS with a web/app UI and integrations, but there is no evidence of a CLI, headless mode, or CI/automation runner; probes for API/OpenAPI specs all returned 404s.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence that Reclaim.ai supports plugging in MCP servers or any tool-use protocol; the product integrates with calendars, task apps, and Slack, but there's nothing about MCP client capability. Missing for 10: any mention of MCP support, tool-plugin architecture, or third-party tool invocation.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Reclaim.ai is a scheduling/calendar automation product, not an AI agent/assistant itself, so an official MCP server is a plausible ecosystem integration; however, no evidence in the pack shows any MCP server, API for agent connectivity, or related integration—only calendar/scheduling features and a failed OpenAPI probe.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Reclaim advertises an 'AI Assistant' chat interface for planning, prioritizing, and optimizing your schedule, and a 2.0 'Schedule Assistant' that suggests actions — both implying natural-language interaction. However, there's no detailed documentation of command scope, examples of actual NL commands, or independent/hands-on evidence confirming this works reliably as a command interface. Missing for 10: independent corroboration of the AI Assistant's natural-language capabilities, detailed command examples/scope, and hands-on user reports validating it in practice.", "evidenceIds": [ "reclaim-docs-11", "reclaim-docs-51" ] }, { "productId": "reclaim", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an official CLI for Reclaim.ai; the product surfaces are calendar integrations, web app, Slack/Google add-ons, and chat AI assistant, with no mention of a command-line interface. missing for 10: any documentation or reference to a CLI tool, CLI installation instructions, or CLI-based automation.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a documented public API for Reclaim.ai — the evidence pack only shows product feature docs and community discussion of the scheduling app, and explicit probes for OpenAPI/swagger endpoints all returned 404s.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of scoped or least-privilege API credential issuance for agents; the OpenAPI probe returned 404s and no docs mention API keys, tokens, or permission scoping. This is a fair question for an AI-native scheduling product with integrations, so it applies but is unmet.", "evidenceIds": [ "reclaim-probe-3" ] }, { "productId": "reclaim", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an official SDK for developers to build against; probes for OpenAPI/API specs all returned 404, and all docs reference end-user scheduling features, not developer SDKs.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a webhooks/event subscription API; probes for OpenAPI/schema endpoints all returned 404, and no docs mention webhooks at all.", "evidenceIds": [ "reclaim-probe-3" ] }, { "productId": "reclaim", "storyId": "ai-meeting-time-optimization", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Reclaim explicitly markets Smart Meetings as finding the best time across all attendees' schedules, and documents automatic rescheduling of lower-priority events to make room for higher-priority meetings, with priority-based continuous optimization applied across the calendar. Community feedback corroborates the automatic scheduling behavior (throttling, control over free/busy) though one user notes syncing hiccups. Missing for 10: independent hands-on verification specifically of multi-attendee optimization accuracy/quality and no detailed technical explanation of the algorithm across multiple external calendars.", "evidenceIds": [ "reclaim-docs-5", "reclaim-docs-29", "reclaim-docs-33", "reclaim-docs-34", "reclaim-docs-17", "reclaim-comm-1" ] }, { "productId": "reclaim", "storyId": "ai-task-autoschedule", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Reclaim's core product explicitly auto-schedules Tasks/Habits into calendar blocks around meetings and deadlines using priority levels, and automatically reschedules events when conflicts arise without manual reshuffling (reclaim-docs-7, -32, -33, -34, -29, -12). Community users corroborate this in practice, describing it as reserving time and reducing manual calendar management (reclaim-comm-3, reclaim-comm-4, reclaim-comm-10, reclaim-comm-9), with one user reporting a specific self-invite scenario that didn't trigger rescheduling (reclaim-comm-5). Missing for 10: independent quantitative benchmarks of re-planning reliability and broader third-party testing beyond a few anecdotal community posts.", "evidenceIds": [ "reclaim-docs-7", "reclaim-docs-9", "reclaim-docs-32", "reclaim-docs-33", "reclaim-docs-34", "reclaim-docs-12", "reclaim-docs-29", "reclaim-docs-37", "reclaim-comm-3", "reclaim-comm-4", "reclaim-comm-9", "reclaim-comm-10", "reclaim-comm-5" ] }, { "productId": "reclaim", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an interactive API reference or runnable examples; probes for OpenAPI/swagger specs all returned 404, and no docs mention a developer API console.", "evidenceIds": [ "reclaim-probe-3" ] }, { "productId": "reclaim", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The probe explicitly checked common OpenAPI/swagger spec paths and all returned 404, and no documentation mentions a downloadable machine-readable API spec; only an llms.txt for docs is present.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-1" ] }, { "productId": "reclaim", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Reclaim.ai is a calendar/scheduling automation tool, not a developer platform or agent framework with sandboxed test environments; there is no concept of production vs sandbox data in this product category.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any versioned API or documented deprecation policy; OpenAPI probes returned 404s and no API documentation appears anywhere in the evidence pack.", "evidenceIds": [ "reclaim-probe-3" ] }, { "productId": "reclaim", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Reclaim's docs describe automating scheduling, priorities, and syncing for individual tasks/habits/meetings, but there is no evidence of a bulk-operations capability (e.g., editing, rescheduling, or updating many items at once via a single command or API call).", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Reclaim ships several built-in automated behaviors that resemble simple rule-trigger-action patterns — e.g. hashtags like #reclaim_free, #reclaim_busy, #needs_travel that change scheduling behavior on tagged events, priority levels (P1-P4) that drive auto-scheduling decisions, and automatic buffer/travel-time insertion and rescheduling on conflicts. However, these are fixed, product-defined automations rather than a general-purpose rule engine where an AI-native user can define arbitrary custom triggers and actions across event types. Missing for 10: a documented user-configurable rule/trigger-action builder (e.g. 'if event has property X, do Y'), support for custom event-based automations beyond the handful of built-in hashtags/priorities, and any API/webhook-based automation hooks.", "evidenceIds": [ "reclaim-docs-33", "reclaim-docs-34", "reclaim-docs-43", "reclaim-docs-44", "reclaim-docs-45", "reclaim-docs-14", "reclaim-docs-37" ] }, { "productId": "reclaim", "storyId": "automation-scheduled-jobs", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Reclaim's Habits and recurring Tasks features let users define recurring routines that the AI auto-schedules and re-flexes around the calendar week over week, and priorities/auto-rescheduling keep them running without manual intervention (reclaim-docs-4, reclaim-docs-31, reclaim-docs-33, reclaim-docs-34), with community confirmation that Habits offer real control for recurring commitments (reclaim-comm-1, reclaim-comm-10). However this is calendar-event recurrence, not general 'workflow' automation (e.g., multi-step or cross-tool automated jobs) — missing for 10: evidence of broader workflow/automation beyond calendar-based recurring tasks, and any API/triggered job scheduling for developers.", "evidenceIds": [ "reclaim-docs-4", "reclaim-docs-31", "reclaim-docs-33", "reclaim-docs-34", "reclaim-comm-1", "reclaim-comm-10" ] }, { "productId": "reclaim", "storyId": "automation-versioned-workflows", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "Reclaim's 2.0 Schedule Assistant lets users 'preview changes in your calendar before deploying them' (docs-52), which offers a thin form of review before automation changes are applied, and locking events (docs-37, docs-41) provides a manual override, but there is no evidence of true automation versioning, change history, or a rollback mechanism for scheduling rules/priorities themselves. Missing for 10: version history of automation rules, ability to roll back to a prior automation configuration, audit trail of automated schedule changes.", "evidenceIds": [ "reclaim-docs-52", "reclaim-docs-37", "reclaim-docs-41" ] }, { "productId": "reclaim", "storyId": "booking-link-self-serve", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Reclaim's Scheduling Links feature is directly documented as sharing availability so invitees can book from live calendar data across one or many calendars, with automatic conflict-avoidance and rescheduling of lower-priority events to keep availability accurate (reclaim-docs-2, reclaim-docs-49, reclaim-docs-17, reclaim-docs-29, reclaim-docs-23, reclaim-docs-35). This matches the founder story of a self-serve booking link replacing email back-and-forth. Missing for 10: independent/hands-on user confirmation specifically of the booking-link flow (community evidence covers other Reclaim features, not scheduling links directly) and no evidence on booking page customization/embedding.", "evidenceIds": [ "reclaim-docs-2", "reclaim-docs-49", "reclaim-docs-17", "reclaim-docs-29", "reclaim-docs-23", "reclaim-docs-35" ] }, { "productId": "reclaim", "storyId": "booking-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any webhook capability for booking/reschedule/cancel events; probes for OpenAPI/API docs returned 404s and no webhook documentation appears anywhere in the evidence pack.", "evidenceIds": [ "reclaim-probe-3" ] }, { "productId": "reclaim", "storyId": "buffers-notice-limits", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Reclaim documents robust buffer-time features (travel time before/after meetings, decompression time, spacing between tasks/habits) and scheduling-link availability sharing, but the evidence pack has no mention of configurable minimum notice, daily booking caps, or date-range windows for scheduling links. missing for 10: minimum notice period settings, daily booking caps, date-range windows for booking links, independent confirmation of these specific link controls.", "evidenceIds": [ "reclaim-docs-3", "reclaim-docs-14", "reclaim-docs-19", "reclaim-docs-20", "reclaim-docs-21", "reclaim-docs-24", "reclaim-docs-2", "reclaim-docs-49" ] }, { "productId": "reclaim", "storyId": "collective-availability", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Reclaim's Scheduling Links let a sales lead share \"you and your team's availability\" so bookers can pick slots \"across one, or many\" calendars (reclaim-docs-49), and Smart Meetings claim to find times that work for all attendees (reclaim-docs-5), which is directionally aligned with collective event scheduling. However, there is no explicit documentation of a distinct 'collective' event type or of logic that strictly shows only slots where every required host is simultaneously free (vs. round-robin or single-host links). missing for 10: explicit product terminology/config for collective events, confirmation that all-hosts-free logic is enforced, independent/hands-on verification of this specific behavior.", "evidenceIds": [ "reclaim-docs-49", "reclaim-docs-5", "reclaim-docs-50" ] }, { "productId": "reclaim", "storyId": "crm-automation-integrations", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack details Reclaim's calendar sync (Google/Outlook), Slack status sync, and task-tool integrations (Todoist, Asana, ClickUp, Linear, Jira, Google Tasks), but contains no mention of Salesforce, HubSpot, Zapier, or any CRM/automation-platform integration for sales bookings. Since Reclaim is a scheduling tool, this CRM/automation-flow axis is a fair question, but no evidence supports it being delivered.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "cross-calendar-blocking-sync", "verdict": "disputed", "quality": 6, "confidence": "medium", "rationale": "Reclaim's Calendar Sync feature is documented extensively as creating 'synced copies' of events across source/destination calendars so busy blocks stay in sync automatically (reclaim-docs-8, reclaim-docs-13, reclaim-docs-18, reclaim-docs-23, reclaim-docs-50), which directly matches the story. However, a hands-on community report describes the sync failing to reflect changes when tested across accounts ('I've signed up... but if I invite myself from another account, nothing happens' — reclaim-comm-5), a concrete contradiction of the claimed automatic behavior. Missing for 10: independent verification that sync reliably works across real work/personal accounts, resolution of the reported failure case, and clearer documentation on cross-provider (e.g., Exchange/Outlook) sync reliability.", "evidenceIds": [ "reclaim-docs-8", "reclaim-docs-13", "reclaim-docs-18", "reclaim-docs-23", "reclaim-docs-50", "reclaim-comm-5" ] }, { "productId": "reclaim", "storyId": "event-type-controls", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Reclaim's Scheduling Links docs describe sharing availability and smart rescheduling around priorities, but nothing in the evidence pack describes creating multiple distinct event types each with their own duration, location, custom questions, or confirmation rules — the core of this story.", "evidenceIds": [ "reclaim-docs-2", "reclaim-docs-12", "reclaim-docs-17", "reclaim-docs-49" ] }, { "productId": "reclaim", "storyId": "focus-time-defense", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Reclaim's core Focus Time and Habits features are explicitly documented as AI-defended blocks that flex/reschedule around conflicts rather than being dropped (reclaim-docs-1, reclaim-docs-30, reclaim-docs-31, reclaim-docs-34), reinforced by priority-based auto-scheduling (reclaim-docs-33) and locking behavior. Community testimonials corroborate real-world use of habit/commitment defense (reclaim-comm-1, reclaim-comm-3, reclaim-comm-10). Missing for 10: independent long-term reliability data or edge-case testing showing how conflicts are resolved in practice beyond vendor docs and a few anecdotes.", "evidenceIds": [ "reclaim-docs-1", "reclaim-docs-30", "reclaim-docs-31", "reclaim-docs-33", "reclaim-docs-34", "reclaim-comm-1", "reclaim-comm-3", "reclaim-comm-10" ] }, { "productId": "reclaim", "storyId": "free-tier-individual", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Docs confirm a free 'Lite' tier exists for a single user with 'essential smart time blocking features' (reclaim-docs-16/28), and Scheduling Links are documented as a core feature (reclaim-docs-2, reclaim-docs-49), but no evidence explicitly states that Scheduling Links/booking links are included in the free Lite tier versus gated behind a paid plan. Missing for 10: explicit confirmation that booking/scheduling links work on the free tier, and independent hands-on confirmation of a usable free booking link.", "evidenceIds": [ "reclaim-docs-16", "reclaim-docs-28", "reclaim-docs-2", "reclaim-docs-49" ] }, { "productId": "reclaim", "storyId": "multi-calendar-conflict-check", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Reclaim's Calendar Sync explicitly creates 'synced copies' across calendars so double-booking is avoided and true availability is reflected, and docs confirm native Google and Outlook support (reclaim-docs-8,13,18,23,50,46,47). Apple/iCloud support exists but only via a workaround using shared calendar sync to Google Calendar, not a first-class integration (reclaim-docs-48), and one hands-on community report describes cross-account invites not being caught (reclaim-comm-5), while older community comments raised doubts about Exchange/O365 coverage (reclaim-comm-6,7). missing for 10: native first-class Apple Calendar integration, current independent confirmation that conflict detection works reliably across all three calendar types simultaneously.", "evidenceIds": [ "reclaim-docs-8", "reclaim-docs-13", "reclaim-docs-18", "reclaim-docs-23", "reclaim-docs-50", "reclaim-docs-46", "reclaim-docs-47", "reclaim-docs-48", "reclaim-comm-5", "reclaim-comm-6", "reclaim-comm-7" ] }, { "productId": "reclaim", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation of a public API at all — probes for OpenAPI/swagger specs at help.reclaim.ai all returned 404, and no docs items reference API endpoints or programmatic parity with the UI. Without any evidence of an API existing, there's no basis to claim API/UI feature parity.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any data export/portability feature or open-format export capability; evidence only covers scheduling/calendar automation features, and API/openapi probes returned 404s, suggesting no documented export mechanism.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Reclaim.ai is a closed-source SaaS scheduling product; no evidence of any open-source license or public source repository is present in the evidence pack. This is a fair axis to ask (any product could open-source components), but nothing indicates it does, so verdict is none.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "openness-self-host", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.)", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "payments-on-booking", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack of Stripe integration or payment collection at booking; scheduling links features cover availability and auto-rescheduling only, not payments.", "evidenceIds": [ "reclaim-docs-2", "reclaim-docs-12", "reclaim-docs-17" ] }, { "productId": "reclaim", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack that Reclaim.ai offers data residency/region selection options; all documentation covers scheduling features with no mention of data storage location controls. Missing for 10: any mention of data residency, regional hosting, or storage location choice.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any AI-training opt-out, data-usage policy, or privacy controls for AI model training; evidence only covers scheduling features and general product feedback.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items address data retention, deletion, export, or privacy controls for user data; all citations focus on scheduling/calendar features and community sentiment unrelated to data governance. missing for 10: data retention policy documentation, account/data deletion mechanism, data export tools, privacy/GDPR compliance controls.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses telemetry/usage-tracking opt-out settings or privacy controls for Reclaim.ai; documentation focuses entirely on scheduling features, and one community comment even expresses discomfort about handing calendar data to the company with no rebuttal about opt-out mechanisms.", "evidenceIds": [ "reclaim-comm-2" ] }, { "productId": "reclaim", "storyId": "reminders-noshow-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Reclaim.ai is a calendar/scheduling automation tool focused on smart time-blocking, buffers, and scheduling links; no evidence anywhere in the pack mentions automated reminder or follow-up sequences via email/SMS to reduce no-shows.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "reschedule-cancel-flows", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence describes Reclaim's own AI-driven rescheduling of lower-priority events and Calendar Sync propagating changes, but there is no documentation of an invitee-facing reschedule/cancel action from a booking confirmation, nor of policies (e.g., notice windows, buffers) being enforced when an invitee makes that change. This is a reasonable ask for a scheduling-link product, but no evidence supports it.", "evidenceIds": [ "reclaim-docs-12", "reclaim-docs-29", "reclaim-docs-49" ] }, { "productId": "reclaim", "storyId": "round-robin-distribution", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Reclaim's evidence covers individual scheduling, priorities, buffers, scheduling links, and calendar sync, but there is no mention of round-robin distribution, lead routing, or weighted/priority-based load balancing across a sales team's inbound meetings — that is a distinct sales-scheduling capability not evidenced here.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "routing-forms-qualify", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence covers scheduling links, calendar sync, and availability sharing, but there is no mention of a routing form feature that qualifies invitees via questions and routes them to different people/teams — this is a distinct capability from simple scheduling links.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "scheduling-rest-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a documented REST API for managing event types, availability, or bookings; probes for OpenAPI/Swagger specs all returned 404, and no docs mention a public API or SDK for developers.", "evidenceIds": [ "reclaim-probe-3", "reclaim-probe-2" ] }, { "productId": "reclaim", "storyId": "self-host-scheduling-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Reclaim.ai is a closed-source SaaS scheduling product with no evidence of any open-source license, source availability, or container image for self-hosting; all evidence points to a hosted proprietary service.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "timezone-safe-booking", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence describes time zone detection, display in invitee's local time, or DST handling for Scheduling Links; docs mention 'true availability across calendars' and lock times 'in your local timezone' but never address invitee-side timezone conversion or DST correctness.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "transparent-seat-pricing", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence confirms Reclaim has a dedicated pricing/plans doc and that the Lite tier is free for a single user, but no evidence pack content shows actual per-seat dollar prices or feature breakdowns for paid tiers. Missing for 10: explicit price points for Starter/Business/Enterprise tiers, per-seat cost breakdown, and feature comparison table across tiers.", "evidenceIds": [ "reclaim-docs-16", "reclaim-docs-28" ] }, { "productId": "reclaim", "storyId": "video-conferencing-links", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers Reclaim's scheduling, buffers, calendar sync, tasks, and priorities extensively, but there is no mention anywhere of automatic video conference link generation (Zoom, Google Meet, Teams, or native video) for bookings or scheduling links. Missing for 10: any documentation of video conferencing integration or auto-added meeting links to bookings/scheduling links.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "website-embed", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an embeddable booking widget (inline/popup/floating) or documented snippet for websites; Scheduling Links only refer to sharable links, not embeds. Missing for 10: any mention of embed code, widget SDK, iframe, or JS snippet for embedding booking on external sites.", "evidenceIds": [] }, { "productId": "reclaim", "storyId": "working-hours-overrides", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Reclaim provides dedicated OOO/vacation handling (reclaim-docs-38) and schedule overrides via hashtags like #reclaim_free/#reclaim_busy for exception periods (reclaim-docs-43, reclaim-docs-44), plus availability-based scheduling links (reclaim-docs-2, reclaim-docs-49, reclaim-docs-23). However, there's no explicit documentation of a dedicated 'working hours' settings screen or true date-specific override calendar (beyond hashtag hacks), missing for 10: explicit working-hours configuration UI, granular date-override scheduling beyond hashtags, and independent verification of these settings working reliably.", "evidenceIds": [ "reclaim-docs-38", "reclaim-docs-43", "reclaim-docs-44", "reclaim-docs-2", "reclaim-docs-49", "reclaim-docs-23" ] }, { "productId": "savvycal", "storyId": "agent-books-meeting", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "SavvyCal has a documented REST API with OAuth/PAT auth and a named 'Meetings API' (savvycal-docs-5,45,50,53,54,61), suggesting programmatic meeting management exists, but there is no evidence of specific endpoints for checking availability, booking, rescheduling, or canceling meetings, and no MCP server is mentioned anywhere. Probes confirm no discoverable OpenAPI spec or llms.txt, undermining agent-readiness. missing for 10: explicit API endpoints/docs for availability check, book, reschedule, cancel; any MCP server or agent-specific integration; independent confirmation of end-to-end API scheduling flow.", "evidenceIds": [ "savvycal-docs-5", "savvycal-docs-45", "savvycal-docs-50", "savvycal-docs-52", "savvycal-docs-61", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "agent-scheduling-tool", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal offers a REST API, webhooks, and OAuth/PAT auth, but there is no evidence of an MCP server, tool-calling schema, or agent-facing surface; probes for llms.txt and OpenAPI spec both 404, indicating no discoverable machine/agent tool interface.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-52", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "A direct probe for llms.txt returned a 404, and no evidence indicates any agent-oriented documentation or AI-consumable docs format exists.", "evidenceIds": [ "savvycal-probe-1" ] }, { "productId": "savvycal", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of AI-generated insights, analytics, or suggestions surfaced within SavvyCal; the product is a scheduling tool with API/webhook/workflow automation features but nothing about AI-derived insights from user data.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "agentic-autonomous-automation", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "SavvyCal's Workflows feature lets users attach multi-action automations to scheduling links that trigger automatically on meeting lifecycle events (booked, canceled, reminders) without manual intervention, and further extend via Zapier for CRM/task automations — this matches autonomous background automation. Missing for 10: independent/hands-on verification of workflow reliability, evidence of conditional/branching logic or scheduled (non-event-triggered) automations, and any AI-specific automation capability.", "evidenceIds": [ "savvycal-docs-15", "savvycal-docs-16", "savvycal-docs-17", "savvycal-docs-25", "savvycal-docs-26", "savvycal-docs-48" ] }, { "productId": "savvycal", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The only remotely related item, 'Delegate to an assistant' (savvycal-docs-59), refers to giving a human executive assistant account access on a pricing page, not a built-in AI assistant. No evidence anywhere in the pack of an AI assistant feature users can delegate tasks to within SavvyCal.", "evidenceIds": [ "savvycal-docs-59" ] }, { "productId": "savvycal", "storyId": "agentic-headless", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "SavvyCal exposes a REST API with OAuth/personal-access-token auth and webhooks (savvycal-docs-1, savvycal-docs-5, savvycal-docs-45) which allows scripted, non-UI automation of scheduling tasks, giving a partial headless-usage path. However there is no CLI, no documented CI/automation runner, and no explicit guidance for unattended CI execution. Missing for 10: a CLI or headless mode, CI-specific documentation/examples, and evidence of unattended/automated execution outside interactive OAuth flows.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-5", "savvycal-docs-45", "savvycal-docs-52" ] }, { "productId": "savvycal", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "SavvyCal is a scheduling SaaS product, not an AI agent or agent-facing platform; there is no evidence of MCP client functionality or any mechanism to plug in MCP servers, and this axis is a category error for a scheduling tool.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal is a scheduling SaaS, so publishing an official MCP server is a fair, applicable question for its ecosystem, but there is no mention of MCP anywhere in the evidence—only REST API, webhooks, and JS embed integrations are documented. missing for 10: any mention of an MCP server, agent integration, or MCP protocol support.", "evidenceIds": [ "savvycal-docs-52", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any natural-language command interface, AI assistant, or chat-based control for SavvyCal; the evidence only covers scheduling features, REST API, webhooks, and OAuth. Probes for llms.txt and OpenAPI spec both returned 404, further indicating no AI-native interface layer.", "evidenceIds": [ "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal offers a REST API, webhooks, and JS embed library, but there is no mention anywhere of an official CLI tool for AI-native workflows.", "evidenceIds": [ "savvycal-docs-52" ] }, { "productId": "savvycal", "storyId": "agentic-public-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "SavvyCal documents a public REST API using JSON, OAuth2 and personal access tokens, plus webhooks with HMAC signing and a JS embed library, giving programmatic/agentic control over scheduling. Missing for 10: a discoverable machine-readable OpenAPI spec or llms.txt (probes returned 404) and independent/hands-on corroboration of API completeness.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-5", "savvycal-docs-38", "savvycal-docs-52", "savvycal-docs-61", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "SavvyCal's docs show OAuth2 and personal access token authentication for its API, but there is no evidence of scope definitions, granular permissions, or least-privilege credential issuance tailored for an agent use case.", "evidenceIds": [ "savvycal-docs-5", "savvycal-docs-50", "savvycal-docs-61" ] }, { "productId": "savvycal", "storyId": "agentic-sdks", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "SavvyCal offers a documented REST API with OAuth/PAT auth, webhooks, and a JavaScript embed library, giving developers programmatic access, but there is no evidence of official language-specific SDKs (e.g., Python, Node, Ruby) beyond the JS embed script, and probes show no OpenAPI spec or llms.txt available for AI tooling. Missing for 10: dedicated official SDK libraries in multiple languages, published OpenAPI/swagger spec, and AI-discoverable docs (llms.txt) that would support agentic building.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-2", "savvycal-docs-52", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "SavvyCal has documented webhook support with HTTP POST notifications on account changes, HMAC-SHA256 signature verification, and setup instructions via Settings > Integrations, enabling event-driven subscription for automation/agent use cases. Missing for 10: no independent/hands-on corroboration or public OpenAPI/webhook schema (openapi probe returned 404s), and no explicit list of subscribable event types.", "evidenceIds": [ "savvycal-docs-3", "savvycal-docs-4", "savvycal-docs-39", "savvycal-docs-46", "savvycal-docs-52", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "ai-meeting-time-optimization", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "SavvyCal offers collective/round-robin availability views and 'ranked availability windows' but these are rule-based scheduling features, not an AI system that finds and continuously re-optimizes the best time as calendars change; no evidence of any AI/ML-driven optimization engine is present in the evidence pack.", "evidenceIds": [ "savvycal-docs-6", "savvycal-docs-31", "savvycal-docs-19" ] }, { "productId": "savvycal", "storyId": "ai-task-autoschedule", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal is a scheduling-link tool with API/webhooks/workflows, but there is no evidence of AI-driven autonomous task scheduling into calendar blocks or automatic re-planning around deadlines/meetings; its 'workflows' are manual/trigger-based automations, not AI task planning.", "evidenceIds": [ "savvycal-docs-12", "savvycal-docs-15", "savvycal-docs-25" ] }, { "productId": "savvycal", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence confirms SavvyCal has a REST API with OAuth/bearer/personal-access-token docs, but nothing describes an interactive reference with runnable/try-it examples, and probes for openapi.json/swagger.json/llms.txt all return 404, suggesting no such interactive spec is discoverable.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-52", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "SavvyCal documents a REST API with OAuth/PAT auth (savvycal-docs-1, -38, -52), and the API reference format (Bearer Auth listings) suggests it may be generated from an OpenAPI schema, but no evidence shows a downloadable OpenAPI/Swagger spec is actually published. Direct probes for openapi.json, swagger.json, and llms.txt all returned 404, contradicting any claim of a machine-readable spec being available.", "evidenceIds": [ "savvycal-docs-52", "savvycal-docs-61", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a sandbox, test mode, or staging environment for the SavvyCal API; docs only cover REST API, OAuth, webhooks and personal access tokens with no mention of test data isolation.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-52" ] }, { "productId": "savvycal", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence shows SavvyCal has a REST API with OAuth/PAT authentication, but there is no mention anywhere of API versioning or a documented deprecation policy, and probes for openapi/llms.txt specs failed (404s). Missing for 10: any documentation of API version numbers, changelog, or deprecation/sunset policy.", "evidenceIds": [ "savvycal-docs-1", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "SavvyCal exposes a REST API and webhooks, which could in principle support bulk operations, but no evidence describes any batch/bulk endpoints, batch scheduling actions, or bulk update/import/export capability across links, meetings, or contacts.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-52", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "SavvyCal's Workflows feature lets users attach multi-action automations to scheduling links that trigger on meeting lifecycle events (booked, reminder, follow-up), and webhooks plus Zapier extend this to external CRM/task actions, which is genuine event-driven automation. However the evidence shows this is scoped to meeting-lifecycle triggers rather than general conditional rule logic (if/then branching) across arbitrary events. Missing for 10: documented conditional/branching rule syntax, evidence of custom trigger conditions beyond meeting stages, and independent/hands-on confirmation of workflow reliability.", "evidenceIds": [ "savvycal-docs-15", "savvycal-docs-16", "savvycal-docs-25", "savvycal-docs-26", "savvycal-docs-17", "savvycal-docs-3", "savvycal-docs-46" ] }, { "productId": "savvycal", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "SavvyCal's 'workflows' feature (docs-15/16/25/26) triggers actions based on meeting lifecycle events (booking, reminders, CRM updates), not on a recurring/cron-like schedule independent of a meeting trigger; there is no evidence of scheduling arbitrary recurring jobs or workflows for AI-native automation.", "evidenceIds": [ "savvycal-docs-15", "savvycal-docs-16", "savvycal-docs-25", "savvycal-docs-26", "savvycal-docs-17" ] }, { "productId": "savvycal", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal offers workflows/automations (docs-15, docs-16, docs-25) but there is no evidence of any version history, change review, diffing, or rollback capability for these automations or workflows.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "booking-link-self-serve", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "SavvyCal's core product is booking links that show live availability, embeddable via widget/hyperlink/JS, with calendar overlay so invitees pick a mutual time without email back-and-forth. This is well documented across multiple first-party pages. Missing for 10: independent/third-party hands-on corroboration beyond vendor docs.", "evidenceIds": [ "savvycal-docs-33", "savvycal-docs-34", "savvycal-docs-35", "savvycal-docs-42", "savvycal-docs-49", "savvycal-docs-28" ] }, { "productId": "savvycal", "storyId": "booking-webhooks", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "SavvyCal docs explicitly describe webhooks for listening to account changes via HTTP POST, with HMAC-SHA256 signature verification and setup instructions via Settings > Integrations. Missing for 10: explicit enumeration of specific event types (booking created/rescheduled/canceled) and independent/hands-on confirmation of real-time delivery reliability.", "evidenceIds": [ "savvycal-docs-3", "savvycal-docs-4", "savvycal-docs-39", "savvycal-docs-46", "savvycal-docs-52" ] }, { "productId": "savvycal", "storyId": "buffers-notice-limits", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "SavvyCal explicitly documents daily/weekly/monthly booking caps (docs-11, docs-36) and 'budget your time' calendar-based preferences that could relate to buffers/notice (docs-12), but there is no explicit mention of configurable pre/post-meeting buffers, minimum notice period, or date-range availability windows in the evidence pack. missing for 10: explicit buffer-before/after-meeting settings, minimum notice period configuration, and date-range window limits.", "evidenceIds": [ "savvycal-docs-11", "savvycal-docs-36", "savvycal-docs-12" ] }, { "productId": "savvycal", "storyId": "collective-availability", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "SavvyCal explicitly documents collective scheduling links that show combined availability across multiple teammates, only surfacing slots where the whole group is free ('Show combined availability for you and any number of teammates that allow recipients to book a time with your selected group'; 'Combine your availability with multiple colleagues on scheduling links'), distinct from its round-robin (any-available-host) mode. Missing for 10: independent/hands-on corroboration beyond vendor marketing pages and explicit confirmation of 'required host' logic vs optional overlay.", "evidenceIds": [ "savvycal-docs-29", "savvycal-docs-43", "savvycal-docs-6", "savvycal-docs-19" ] }, { "productId": "savvycal", "storyId": "crm-automation-integrations", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "SavvyCal explicitly supports Zapier for CRM syncing and workflow automations (create/update CRM records), plus webhooks and a REST API for custom integrations, which together enable bookings to flow into CRM/automation stacks without manual copying. However, there is no evidence of native, first-party Salesforce or HubSpot integrations — only generic Zapier and webhook/API-based paths, which require setup/configuration rather than a turnkey connection. Missing for 10: dedicated Salesforce/HubSpot native integrations, documented pre-built Zaps or CRM field-mapping templates, and independent case studies confirming reliable no-manual-copy CRM sync in practice.", "evidenceIds": [ "savvycal-docs-17", "savvycal-docs-26", "savvycal-docs-57", "savvycal-docs-3", "savvycal-docs-52" ] }, { "productId": "savvycal", "storyId": "cross-calendar-blocking-sync", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "SavvyCal's docs reference including external/multiple calendars in availability checks and budgeting time via calendar events, implying busy blocks from connected calendars feed into scheduling, but no evidence explicitly describes connecting a personal AND work calendar and syncing busy blocks automatically between them for an individual user's own scheduling link. missing for 10: explicit documentation of multi-calendar (work+personal) connection and automatic busy-block sync for a single user, plus independent/hands-on confirmation.", "evidenceIds": [ "savvycal-docs-8", "savvycal-docs-12", "savvycal-docs-27", "savvycal-docs-42" ] }, { "productId": "savvycal", "storyId": "event-type-controls", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Evidence confirms SavvyCal supports multiple customizable scheduling links (branding, payment integration, booking limits, workflows attached to links), implying separate 'event types' per link, but nothing in the pack explicitly documents per-link duration settings, location options, custom intake questions, or confirmation/approval rules. missing for 10: explicit docs on setting duration per link, location fields, custom questions builder, and confirmation-required vs auto-confirm booking rules.", "evidenceIds": [ "savvycal-docs-9", "savvycal-docs-11", "savvycal-docs-16", "savvycal-docs-33", "savvycal-docs-34", "savvycal-docs-36" ] }, { "productId": "savvycal", "storyId": "focus-time-defense", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal's evidence covers scheduling links, availability, round robin, workflows, and payments, but there is no mention of auto-defending recurring focus time/habits or dynamically rescheduling blocked time when conflicts arise. The 'budget your time using calendar events' feature (docs-12) is the closest but only describes honoring preferences during booking, not proactive conflict-driven rescheduling of habits.", "evidenceIds": [ "savvycal-docs-12" ] }, { "productId": "savvycal", "storyId": "free-tier-individual", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of a free tier, free plan details, or what a basic booking link includes without payment; only feature and API docs are present, with no pricing-plan breakdown. Missing for 10: any documentation of a free plan's scope/limits, evidence that a usable booking link exists without payment, and confirmation of no-cost individual scheduling.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "multi-calendar-conflict-check", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers API/webhooks, round-robin scheduling, payments, and workflows, but contains no mention of connecting multiple external calendars (Google/Outlook/Apple) or cross-calendar conflict checking for double-booking prevention — the closest items reference 'external calendars' only in the context of team availability aggregation, not personal multi-calendar conflict-checking.", "evidenceIds": [ "savvycal-docs-8" ] }, { "productId": "savvycal", "storyId": "openness-api-parity", "verdict": "partial", "quality": 3, "confidence": "medium", "rationale": "SavvyCal ships a documented REST API, OAuth/personal-access-token auth, webhooks, and a JS embed library, showing genuine API-based access to core scheduling functions, but there is no evidence the API covers the full breadth of UI features (round-robin, meeting polls, workflows, Stripe payment links, custom branding) and probes for an OpenAPI spec/llms.txt both 404, suggesting incomplete or undocumented API surface parity. missing for 10: evidence that advanced UI features (round robin, polls, workflows, payments, branding) are fully exposed via API, a public OpenAPI/schema reference, and independent confirmation of parity.", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-52", "savvycal-docs-5", "savvycal-probe-1", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "There is no evidence of a bulk data export feature or open-format data portability (e.g., CSV/JSON export of bookings, contacts, workflows) that would let a user take all their data and leave; the API exists for integration, not for full data export, and no explicit export/GDPR-style data-download feature is documented.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "SavvyCal is a closed proprietary SaaS scheduling product; the only related evidence is a page mentioning unspecified 'contributions to the community,' not the product's own source code under an open license.", "evidenceIds": [ "savvycal-docs-47" ] }, { "productId": "savvycal", "storyId": "openness-self-host", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal is a hosted SaaS scheduling product with no evidence of a self-hostable core; only an 'open-source contributions' page is mentioned, not a self-hostable server offering.", "evidenceIds": [ "savvycal-docs-47" ] }, { "productId": "savvycal", "storyId": "payments-on-booking", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "SavvyCal's docs explicitly describe connecting a Stripe product to a scheduling link and requiring payment before reserving the meeting time, plus Stripe Tax support for sales tax/VAT/GST and native management of offerings/pricing within SavvyCal. This directly matches the founder story of collecting payment at booking. Missing for 10: independent/hands-on verification of the payment flow (all evidence is vendor docs) and no detail on payment failure/refund handling.", "evidenceIds": [ "savvycal-docs-9", "savvycal-docs-10", "savvycal-docs-30", "savvycal-docs-51" ] }, { "productId": "savvycal", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack of data residency options, regional storage selection, or data localization controls for SavvyCal; the evidence covers scheduling features and API auth only.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses AI training data usage, opt-out controls, or any privacy policy statement regarding AI model training; SavvyCal is a scheduling product and this specific privacy commitment is unevidenced.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence found addressing data retention policies, deletion controls, or privacy/data lifecycle management for SavvyCal; the evidence pack covers scheduling features, API auth, and webhooks only.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention telemetry, usage tracking, analytics opt-out, or privacy controls of this kind; SavvyCal's docs focus on API/webhooks/scheduling features only.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "reminders-noshow-workflows", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "SavvyCal's Workflows feature explicitly supports sending customized 'meeting lifecycle messages' with adjustable timing and content designed 'to minimize no-shows,' plus Zapier integration for further automation (e.g., SMS via third-party apps). However, native SMS reminders are not documented—only email-based workflow messages and templates are described, with SMS presumably requiring Zapier/CRM integration rather than being built-in. missing for 10: native SMS reminder capability, evidence of automatic sequencing/multi-touch cadence beyond single reminders, independent confirmation of no-show reduction impact.", "evidenceIds": [ "savvycal-docs-15", "savvycal-docs-16", "savvycal-docs-25", "savvycal-docs-40", "savvycal-docs-48", "savvycal-docs-17", "savvycal-docs-57" ] }, { "productId": "savvycal", "storyId": "reschedule-cancel-flows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains no mention of invitee-initiated rescheduling or cancellation from a confirmation, nor any statement about policy enforcement or calendar sync on such changes. While this is a plausible feature for a scheduling product like SavvyCal, no documentation, webhook event, or feature page in the pack addresses it. Missing for 10: any mention of reschedule/cancel links in confirmations, policy enforcement on changes, or calendar update propagation across all attendees.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "round-robin-distribution", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "SavvyCal has dedicated round-robin/pooling features that distribute meetings across team members either by cycling (equal distribution) or random selection for max availability, explicitly marketed for sales use cases. However, there is no evidence of configurable weighting or priority levels among team members (e.g., unequal load ratios) beyond binary equal/random distribution. Missing for 10: explicit weighted/priority-based distribution controls, admin-configurable ratios per rep, and independent confirmation of fairness enforcement over time.", "evidenceIds": [ "savvycal-docs-19", "savvycal-docs-20", "savvycal-docs-7", "savvycal-docs-55", "savvycal-docs-62", "savvycal-docs-21" ] }, { "productId": "savvycal", "storyId": "routing-forms-qualify", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "SavvyCal documents round-robin and collective team scheduling that automatically distributes meetings across team members, but there is no evidence of a routing/qualification form that asks invitees questions and branches them to different people or teams based on their answers. Missing for 10: any mention of conditional routing forms, question-based qualification logic, or answer-driven assignment to specific reps/teams.", "evidenceIds": [ "savvycal-docs-19", "savvycal-docs-20", "savvycal-docs-7", "savvycal-docs-62" ] }, { "productId": "savvycal", "storyId": "scheduling-rest-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "SavvyCal documents a REST API with OAuth2/personal-access-token auth and a 'SavvyCal Meetings API' plus webhooks and a JS embed library, indicating programmatic access to scheduling functionality. However, the evidence never specifies concrete endpoints for event types, availability, or bookings, and probes show no discoverable OpenAPI/swagger spec or llms.txt, leaving the exact API surface unconfirmed. Missing for 10: explicit endpoint/resource documentation for event types, availability, and bookings, and a machine-readable API spec (404s on openapi.json/swagger.json).", "evidenceIds": [ "savvycal-docs-1", "savvycal-docs-5", "savvycal-docs-52", "savvycal-docs-61", "savvycal-probe-2" ] }, { "productId": "savvycal", "storyId": "self-host-scheduling-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "SavvyCal is a hosted SaaS scheduling product; evidence shows only a REST API, webhooks, and JS embed for integration, with a page listing 'open-source contributions' but no self-hostable engine, source release, or container image. No evidence of any self-hosting capability under an open-source license.", "evidenceIds": [ "savvycal-docs-47", "savvycal-docs-52" ] }, { "productId": "savvycal", "storyId": "timezone-safe-booking", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item mentions time zone detection, display, or DST handling for invitees; the docs focus on API, webhooks, embedding, team scheduling, and payments but never address time zone automation.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "transparent-seat-pricing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack items reference pricing tiers, per-seat cost, or plan feature comparisons; only savvycal.com/pricing is mentioned once in passing (docs-59) without any pricing details. This is an applicable axis for a SaaS scheduling product, but no evidence shows published per-seat pricing.", "evidenceIds": [] }, { "productId": "savvycal", "storyId": "video-conferencing-links", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Evidence shows automatic video link creation for specific providers (Zoom rooms, Google Meet links, Whereby rooms) tied to round-robin scheduling, implying similar support elsewhere, but there's no explicit mention of Teams integration or a general 'native video' option, and no confirmation this applies uniformly to all booking types beyond round-robin links. missing for 10: Microsoft Teams video link support, native/built-in video conferencing option, and confirmation this auto-generation applies to all booking link types (not just round-robin).", "evidenceIds": [ "savvycal-docs-22", "savvycal-docs-23", "savvycal-docs-24" ] }, { "productId": "savvycal", "storyId": "website-embed", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "SavvyCal documents a JavaScript embed library supporting inline, popover, and floating widget embeds, plus hyperlink/JS-call triggers, matching the story closely (savvycal-docs-2, savvycal-docs-18, savvycal-docs-49, savvycal-docs-52). Missing for 10: a directly-quoted code snippet in the evidence pack and independent/hands-on confirmation of the embed working on a third-party site.", "evidenceIds": [ "savvycal-docs-2", "savvycal-docs-18", "savvycal-docs-49", "savvycal-docs-52" ] }, { "productId": "savvycal", "storyId": "working-hours-overrides", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence only tangentially references availability settings — 'preset work hours' for round-robin links and 'budget your time using calendar events' to honor scheduling preferences — but there is no explicit documentation of a full availability-schedule builder with working hours, date overrides, or dedicated out-of-office periods. missing for 10: explicit docs on defining weekly working-hour schedules, date-specific overrides, and out-of-office blocking.", "evidenceIds": [ "savvycal-docs-12", "savvycal-docs-21", "savvycal-docs-11", "savvycal-docs-36" ] } ]