[ { "productId": "deel", "storyId": "accounting-software-sync", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers Deel's global payroll processing, API/webhooks, sandbox, and MCP server, but there is no mention of a QuickBooks/Xero accounting sync or automated GL journal-entry export capability anywhere in the pack.", "evidenceIds": [] }, { "productId": "deel", "storyId": "agent-onboards-new-hire", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Deel's API/MCP docs show contract creation, listing contracts, time-off requests, and payroll/EOR cost comparisons, and the API supports creating contracts via POST /rest/contracts, suggesting an agent could programmatically onboard a contractor. However, there is no explicit documented endpoint or MCP tool for full employee onboarding covering compensation setup and tax setup as a single end-to-end workflow — the evidence only shows contract creation and cost comparison tools, not a unified 'create employee + compensation + tax' flow. missing for 10: explicit API/MCP endpoints for employee creation with compensation configuration, dedicated tax-setup endpoint/tool, and a documented end-to-end onboarding workflow example or independent confirmation it works as described.", "evidenceIds": [ "deel-docs-1", "deel-docs-14", "deel-docs-21", "deel-docs-10", "deel-docs-23", "deel-docs-30", "deel-docs-8" ] }, { "productId": "deel", "storyId": "agent-payroll-preview-anomalies", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Deel's API/MCP exposes contracts, time-off, and EOR cost-comparison tools, and general marketing about running global payroll, but there is no documented payroll-run preview endpoint, no anomaly-detection capability, and no approval workflow surfaced via API/MCP.", "evidenceIds": [ "deel-docs-10", "deel-docs-23", "deel-docs-20", "deel-docs-19" ] }, { "productId": "deel", "storyId": "agent-reconciles-payroll-journal", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Deel's API and MCP server expose payroll data (and contracts, people, time data) that an agent could pull via API calls or MCP tools like listOfContracts, and sandbox/webhook infrastructure supports building such integrations. However, there is no explicit evidence of a 'payroll journal' entry format, GL-code export, or reconciliation-into-ledger capability (e.g., no mention of accounting export formats or ledger-sync tools). missing for 10: dedicated payroll journal/GL export endpoint, explicit reconciliation or ledger-sync tooling, evidence of accounting-system integration.", "evidenceIds": [ "deel-docs-2", "deel-docs-11", "deel-docs-18", "deel-docs-23", "deel-docs-30", "deel-docs-6" ] }, { "productId": "deel", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Probe confirms llms.txt exists at developer.deel.com/llms.txt (HTTP 200) and per-page markdown (.md) versions are available, plus dedicated MCP/agent-oriented docs exist. Missing for 10: independent third-party confirmation that agents actually consume llms.txt effectively in practice.", "evidenceIds": [ "deel-probe-1", "deel-probe-2", "deel-probe-3", "deel-docs-8" ] }, { "productId": "deel", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Deel doesn't advertise a native in-app AI insights/analytics dashboard, but its MCP server explicitly exposes structured tools (e.g., calculateEorVersusEntityHiringCosts, listOfContracts) that let connected AI agents like Claude or ChatGPT pull and reason over contracts, payroll, and time data to generate insights/suggestions such as EOR-vs-entity cost comparisons. This satisfies the spirit of 'AI-generated insights from my data' but only via external agent connection, not a built-in AI feature surfaced directly in Deel's UI. missing for 10: a native in-product AI insights/recommendation feature (e.g., dashboard-level AI suggestions), independent evidence of the MCP-driven insight tools being used in practice.", "evidenceIds": [ "deel-docs-8", "deel-docs-10", "deel-docs-15", "deel-docs-30", "deel-probe-3" ] }, { "productId": "deel", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Deel provides the building blocks for autonomous automation—real-time webhooks that avoid polling, a public API, and an MCP server exposing tools (listOfContracts, createTimeOffRequest, etc.) that AI agents can invoke—so agents could be wired to act on Deel data without human intervention. However, there's no evidence of a native scheduling/orchestration engine or documented example of an agent running unattended background workflows end-to-end. Missing for 10: evidence of built-in automation/workflow engine, documented autonomous/scheduled agent runs, and independent confirmation of agents operating without human-in-the-loop.", "evidenceIds": [ "deel-docs-6", "deel-docs-7", "deel-docs-8", "deel-docs-9", "deel-docs-30", "deel-docs-29", "deel-docs-17" ] }, { "productId": "deel", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Deel exposes an MCP server so external AI agents (Claude, ChatGPT, custom agents) can query contracts/payroll/time-off data, but this is the opposite direction: it lets outside assistants pull from Deel, not a built-in assistant delegated tasks inside Deel's own product UI. No evidence of a native in-app AI assistant feature.", "evidenceIds": [ "deel-docs-2", "deel-docs-8", "deel-docs-18", "deel-docs-30" ] }, { "productId": "deel", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Deel exposes a REST API with API-token authentication (a non-interactive credential suitable for headless/CI use), plus a sandbox environment for safe automated testing and webhooks for event-driven automation without polling, all of which support running Deel operations headlessly. However, there is no explicit CI/CD example, official SDK, or CLI tool documented for automation pipelines, and MCP usage is framed around interactive AI clients (Claude, ChatGPT) rather than CI contexts. missing for 10: official CI/CD integration guide or example, dedicated SDK/CLI for scripted automation, evidence of MCP server running unattended in a pipeline.", "evidenceIds": [ "deel-docs-3", "deel-docs-4", "deel-docs-6", "deel-docs-27", "deel-docs-31" ] }, { "productId": "deel", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Deel is a workforce/payroll SaaS platform, not an AI agent or assistant host; all evidence describes Deel exposing its own MCP server so external agents (Claude, ChatGPT, etc.) can call Deel's tools, which is the opposite direction from this story of plugging external MCP servers into Deel itself. There is no evidence of any Deel-side agent or assistant that could act as an MCP client consuming other servers' tools, making this axis a category mismatch for this product.", "evidenceIds": [ "deel-docs-2", "deel-docs-8", "deel-docs-29" ] }, { "productId": "deel", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Deel documents an official MCP server exposing tools (listOfContracts, createTimeOffRequest, etc.) that map to Deel API operations, with OAuth2 auto-handled by clients like Claude Desktop, Cursor, VS Code, and ChatGPT, and compatibility with any MCP-over-HTTP client. This is well-documented first-party evidence with no independent hands-on corroboration found. missing for 10: independent/hands-on confirmation of the MCP server working in practice, broader community validation.", "evidenceIds": [ "deel-docs-2", "deel-docs-8", "deel-docs-9", "deel-docs-17", "deel-docs-18", "deel-docs-29", "deel-docs-30", "deel-probe-3" ] }, { "productId": "deel", "storyId": "agentic-nl-commands", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Deel ships an official MCP server exposing contracts, payroll, and time-off tools that can be invoked by AI agents/assistants (Claude, ChatGPT, Cursor) using natural language, with structured tool definitions like createTimeOffRequest and listOfContracts documented in detail. This directly enables AI-native users to operate Deel via natural-language commands routed through MCP clients rather than a native chat UI. Missing for 10: independent/hands-on validation that these NL-driven MCP interactions work reliably in practice, and no evidence of a native in-product NL command interface outside the MCP integration.", "evidenceIds": [ "deel-docs-2", "deel-docs-8", "deel-docs-9", "deel-docs-17", "deel-docs-18", "deel-docs-20", "deel-docs-23", "deel-docs-30", "deel-probe-3" ] }, { "productId": "deel", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Deel offers a REST API, an MCP server, and sandbox/webhooks, but nowhere is a dedicated CLI tool mentioned or documented; all developer interactions are via HTTP API or MCP, not a command-line interface.", "evidenceIds": [] }, { "productId": "deel", "storyId": "agentic-public-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Deel provides a well-documented public REST API with authentication (API tokens, OAuth2), versioning, sandbox environment, webhooks, and even an official MCP server exposing tools mapped to API operations—giving AI-native users multiple documented ways to drive the product programmatically. Missing for 10: independent third-party developer corroboration of real-world API usage beyond vendor docs.", "evidenceIds": [ "deel-docs-1", "deel-docs-3", "deel-docs-8", "deel-docs-18", "deel-docs-27", "deel-docs-28", "deel-docs-31", "deel-probe-1", "deel-probe-2", "deel-probe-3" ] }, { "productId": "deel", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Deel documents two auth methods—static API tokens and OAuth2 (deel-docs-27, deel-docs-28)—and OAuth2 is described as granting access to 'specific data... with explicit user consent,' implying some scoping, and MCP clients handle this OAuth2 flow automatically (deel-docs-17, deel-docs-29). However, there is no explicit documentation of configurable least-privilege scopes/permission sets for API tokens or a scope list for OAuth grants tailored to agent use. Missing for 10: explicit scope/permission catalog for API tokens, documented ability to restrict an agent's OAuth grant to specific resources/actions, and any hands-on confirmation that agents can be issued narrowly scoped credentials.", "evidenceIds": [ "deel-docs-27", "deel-docs-28", "deel-docs-17", "deel-docs-29", "deel-docs-8" ] }, { "productId": "deel", "storyId": "agentic-sdks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Deel provides a rich developer platform — a documented REST API, sandbox environment, webhooks, OAuth2/API-token auth, versioning, and an official MCP server exposing typed tools (createTimeOffRequest, listOfContracts, etc.) that AI agents can call directly — which supports agentic, AI-native integration. However, the evidence never explicitly documents official client SDKs (e.g., language-specific libraries like Python/Node/Go SDKs); all examples are raw REST calls or MCP tool calls, not SDK wrappers. missing for 10: explicit official SDK libraries/language bindings, SDK-specific docs or code samples, independent confirmation of SDK usage.", "evidenceIds": [ "deel-docs-1", "deel-docs-8", "deel-docs-18", "deel-docs-27", "deel-docs-3", "deel-docs-6", "deel-probe-3" ] }, { "productId": "deel", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Deel provides documented webhooks delivering real-time event notifications with HMAC-SHA256 signature security, explicitly framed as an alternative to polling for building integrations—directly matching the AI-native subscribe-to-events story. Missing for 10: no explicit list of supported event types/topics, and no independent/hands-on corroboration of webhook reliability.", "evidenceIds": [ "deel-docs-6", "deel-docs-7" ] }, { "productId": "deel", "storyId": "api-interactive-docs", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Deel provides a sandbox environment with pre-populated data for safely testing API calls (deel-docs-3, deel-docs-4, deel-docs-22, deel-docs-26) and detailed API/MCP tool references, which supports experimentation, but there is no explicit evidence of an interactive in-browser API reference UI with 'try it now' runnable code examples (e.g., Swagger/OpenAPI explorer). Missing for 10: an explicit interactive API reference page with embedded runnable requests, and independent/hands-on confirmation that such a console exists.", "evidenceIds": [ "deel-docs-3", "deel-docs-4", "deel-docs-22", "deel-docs-26", "deel-docs-31" ] }, { "productId": "deel", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack documents Deel's REST API endpoints, versioning headers, sandbox, and MCP server, but nowhere mentions an OpenAPI/Swagger spec file or download link for the API. Missing for 10: any reference to an OpenAPI/Swagger JSON/YAML spec, a spec download endpoint, or explicit machine-readable API schema.", "evidenceIds": [ "deel-docs-1", "deel-docs-31", "deel-probe-1", "deel-probe-2" ] }, { "productId": "deel", "storyId": "api-sandbox", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Deel documents a dedicated API Sandbox described as a 'completely isolated testing environment' that mirrors production without affecting real data, triggering payments, or creating legal contracts, and comes pre-populated with sample contracts/workers/orgs plus a reset function to restore clean data. This directly satisfies the ai-native story of testing without touching production. Missing for 10: independent/hands-on confirmation that the sandbox behaves as documented (only first-party docs available).", "evidenceIds": [ "deel-docs-3", "deel-docs-4", "deel-docs-5", "deel-docs-22", "deel-docs-26" ] }, { "productId": "deel", "storyId": "api-versioning-policy", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Deel documents header-based date versioning (X-Version) for managing API changes, giving clear evidence of a versioned API scheme, but no evidence pack item describes a documented deprecation policy (e.g., sunset timelines, notice periods, or a changelog of deprecated versions). Missing for 10: explicit deprecation/sunset policy documentation, changelog of version retirements, migration guidance for deprecated versions.", "evidenceIds": [ "deel-docs-31", "deel-docs-27" ] }, { "productId": "deel", "storyId": "automatic-tax-filing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only offers generic claims of 'automated compliance' and global payroll processing across 150+ countries, with no specific mention of federal/state/local tax calculation, filing, or remittance automation for US payroll. Missing for 10: any documentation of US tax jurisdiction handling, filing cadence, remittance to tax authorities, or compliance guarantees specific to federal/state/local payroll taxes.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24" ] }, { "productId": "deel", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence shows individual REST/MCP operations (single contract creation, single time-off request, single contract listing) but no documented bulk/batch endpoints or batch MCP tools for operating on many items at once. Payroll 'consolidation' and webhook mentions do not describe bulk create/update operations across large item sets.", "evidenceIds": [ "deel-docs-14", "deel-docs-20", "deel-docs-23", "deel-docs-18" ] }, { "productId": "deel", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Deel offers webhooks for event notifications (deel-docs-6, deel-docs-7) which could feed automated actions, and its MCP server/API expose tools like createTimeOffRequest that agents could invoke, but there's no evidence of a built-in rules engine or automation/workflow builder where a user defines 'if event X then action Y' logic natively within Deel. missing for 10: a native rules/automation engine or workflow builder, documented trigger-condition-action configuration UI or API, and evidence of end-to-end automated event-to-action chaining without external glue code.", "evidenceIds": [ "deel-docs-6", "deel-docs-7", "deel-docs-8", "deel-docs-9", "deel-docs-30" ] }, { "productId": "deel", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Deel's API/MCP server exposes discrete tools (create contract, time-off request, list contracts) and webhooks for event-driven notifications, but there is no mention of scheduling, cron-like recurring job triggers, or workflow automation orchestration that an AI-native user could invoke. Webhooks only react to events rather than being scheduled or recurring on a timer.", "evidenceIds": [ "deel-docs-6", "deel-docs-8", "deel-docs-18", "deel-docs-30" ] }, { "productId": "deel", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Deel's docs cover API/MCP tools, sandbox testing, and webhooks, but there is no evidence of any versioning, review, or rollback mechanism for automations built on Deel (e.g., no changelog, revision history, or rollback feature for workflows/API integrations).", "evidenceIds": [ "deel-docs-3", "deel-docs-6", "deel-docs-8", "deel-docs-18" ] }, { "productId": "deel", "storyId": "cancel-or-correct-payroll", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows Deel's payroll processing, API/MCP tooling, and general platform capabilities, but nothing documents an ability to cancel or correct a submitted payroll run before employees are paid; no API endpoint, MCP tool, or docs reference this workflow. Community comments discuss unrelated complaints (data privacy, wallet terms) and don't address payroll correction/cancellation.", "evidenceIds": [ "deel-docs-11", "deel-docs-12", "deel-docs-19" ] }, { "productId": "deel", "storyId": "compliance-alerts", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence covers Deel's API, MCP server, sandbox, and general payroll/compliance marketing claims, but nothing describes proactive alerts or notifications tied to compliance obligations triggered by new hires, location changes, or law changes; webhooks exist for platform events generally, not compliance-specific alerting. Community evidence is unrelated to this axis. No evidence of a compliance-alerting feature.", "evidenceIds": [] }, { "productId": "deel", "storyId": "embedded-payroll-for-platforms", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Deel exposes a documented REST API and MCP tools for contracts, payroll, and time-off data (e.g., deel-docs-1, deel-docs-11, deel-docs-19, deel-docs-27) that a developer could integrate into their own product, with OAuth2/API tokens and a sandbox for testing (deel-docs-3, deel-docs-26, deel-docs-28). However, none of the evidence mentions a formal 'white-label' or partner-branding program, reseller terms, or embedded-finance partnership model — the API is presented as direct integration, not white-label embedding. Missing for 10: explicit white-label/partner API program docs, branding customization options, and partner agreement terms.", "evidenceIds": [ "deel-docs-1", "deel-docs-11", "deel-docs-19", "deel-docs-27", "deel-docs-28", "deel-docs-3", "deel-docs-26" ] }, { "productId": "deel", "storyId": "fast-direct-deposit", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains general claims about running global payroll (150+ countries, unified data) but no specific mention of direct deposit speed (next-day or 2-day) or check-replacement wire/ACH capability for employees. Community evidence even suggests Deel pushed a proprietary 'Deel Wallet' card rather than standard bank deposit, but this isn't framed against a documented claim. Missing for 10: any documentation of direct deposit timing, ACH/bank transfer speed, or comparison to check payments.", "evidenceIds": [] }, { "productId": "deel", "storyId": "flexible-pay-schedules", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence pack covers Deel's global payroll marketing claims, API/MCP docs, and community complaints, but nothing specifically documents configuring multiple pay schedules (weekly, biweekly, semimonthly, monthly) across different teams. Missing for 10: any docs, UI screenshots, or API reference showing pay schedule/frequency configuration per team.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24" ] }, { "productId": "deel", "storyId": "global-payroll-eor", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Deel's core offering directly matches this story: docs describe EOR and owned-entity payroll across 150+ countries with compliance and cost visibility (deel-docs-11, deel-docs-19, deel-docs-24), plus API/MCP tooling to create contracts and compare EOR vs entity hiring costs (deel-docs-10, deel-docs-14). Community complaints (deel-comm-1/2/3) concern customer service and data-privacy practices, not whether EOR/payroll actually functions, so they don't contradict the core capability. Missing for 10: independent third-party verification of payroll accuracy/compliance across countries beyond vendor marketing copy.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24", "deel-docs-10", "deel-docs-14", "deel-docs-13" ] }, { "productId": "deel", "storyId": "health-benefits-administration", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack covers payroll, contracts, EOR, API/MCP integration, and sandbox testing, but contains no mention of health insurance offerings, enrollment workflows, or benefits deductions syncing to payroll. While benefits administration is a plausible axis for an HR/payroll platform like Deel, there is no documentation or feature evidence supporting this specific capability.", "evidenceIds": [] }, { "productId": "deel", "storyId": "international-contractor-payments", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Deel's docs describe creating contractor contracts via API and running compliant payroll for contractors across 150+ countries with automated compliance and unified data, directly matching the story's core ask. Missing for 10: explicit documentation of local-currency disbursement mechanics and independent verification of contract compliance quality (community feedback focuses on data-sharing/Wallet friction rather than confirming or denying local-currency payment execution).", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24", "deel-docs-14", "deel-docs-21" ] }, { "productId": "deel", "storyId": "multi-state-payroll", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Deel's marketing pages claim 'automated compliance' and payroll processing across 150+ countries, implying broad tax/compliance handling, but no evidence specifically addresses U.S. multi-state payroll registrations or per-state withholding mechanics. Missing for 10: documentation on state-specific tax registration setup, per-state withholding calculation details, and any hands-on/independent verification of multi-state payroll accuracy.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24", "deel-docs-12" ] }, { "productId": "deel", "storyId": "off-cycle-payroll-run", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows general global payroll processing capability (docs-11, docs-19, docs-24) but contains no mention of off-cycle payroll runs, bonus payments, correction runs, or termination-related payroll outside the regular schedule. A community report even notes that 'any exceptions to the rigid workflow breaks the entire process' (deel-comm-3), suggesting non-standard payroll actions may not be well supported, but this is not concrete enough to call it disputed—there's simply no direct evidence the feature exists.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24", "deel-comm-3" ] }, { "productId": "deel", "storyId": "offer-letters-and-documents", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers contracts API, payroll, MCP tools, and sandbox testing, but contains no mention of offer-letter e-signature workflows or per-employee document storage. Missing for 10: e-signature capability documentation, offer letter templates, per-employee document repository evidence.", "evidenceIds": [] }, { "productId": "deel", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Deel exposes a broad REST API and MCP server covering contracts, payroll, time-off, people data, and more, with sandbox/testing and webhook support, indicating substantial parity between API and UI capabilities. However, no evidence explicitly confirms full 1:1 parity between every UI feature and API/MCP tool coverage; documentation shows selected core objects (contracts, time-off, EOR cost calc) rather than an exhaustive UI-equivalence map. Missing for 10: explicit statement or audit confirming all UI actions have API equivalents, and coverage of less common UI workflows (e.g., compliance docs, benefits admin) via API.", "evidenceIds": [ "deel-docs-1", "deel-docs-8", "deel-docs-9", "deel-docs-18", "deel-docs-23", "deel-docs-30", "deel-docs-6", "deel-docs-3" ] }, { "productId": "deel", "storyId": "openness-full-export", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Deel's REST API lets you programmatically retrieve contracts, workers, and payroll data in JSON (an open format) via endpoints like listOfContracts, which could support partial self-service extraction, but there is no documented bulk 'export all my data' feature, account-closure/offboarding data-export workflow, or explicit data-portability guarantee. missing for 10: dedicated full-account data export tool, documented account termination/data takeout process, independent confirmation that all data types (payroll, docs, history) are exportable.", "evidenceIds": [ "deel-docs-1", "deel-docs-23", "deel-docs-14", "deel-docs-27" ] }, { "productId": "deel", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Deel is a closed-source, proprietary SaaS HR/payroll platform, not an open-source project; publishing source code under an open license is not a plausible axis for this kind of commercial service product.", "evidenceIds": [] }, { "productId": "deel", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Deel is a SaaS HR/payroll platform, not open-source infrastructure meant to be self-hosted; self-hosting the core product is a category error for this kind of service.", "evidenceIds": [] }, { "productId": "deel", "storyId": "pay-employees-and-contractors", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Deel's own marketing and API docs explicitly state it can 'pay every worker type... employees, contractors, and EOR workers' from one platform, and the API supports creating contractor contracts and payroll consolidation (deel-docs-11,19,24,14). This directly matches the ops story of paying both W-2 employees and 1099 contractors together. Missing for 10: explicit mention of US W-2 tax-form handling/classification, and independent/hands-on confirmation beyond vendor marketing copy.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24", "deel-docs-14", "deel-docs-25" ] }, { "productId": "deel", "storyId": "payroll-event-webhooks", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Deel's docs confirm a webhooks system delivering real-time notifications for 'key platform events' with HMAC-SHA256 signed payloads, avoiding polling — directly supporting event-driven downstream automation. However, the evidence never enumerates specific payroll lifecycle events like 'payroll processed', 'employee onboarded', or 'payment failed', so it's unclear the exact event catalog matches the story's examples. Missing for 10: an explicit list of supported webhook event types/payloads, and any hands-on/community confirmation of reliability in production use.", "evidenceIds": [ "deel-docs-6", "deel-docs-7" ] }, { "productId": "deel", "storyId": "payroll-reports-exports", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence confirms Deel runs global payroll and exposes payroll data via API/MCP, but there is no mention of payroll register reports, gross-to-net breakdowns, or export/analysis features for ops users. Missing for 10: payroll register report generation, gross-to-net report format, export functionality (CSV/Excel) for analysis.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24" ] }, { "productId": "deel", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention data residency, region selection, or where data is stored; the API/MCP/sandbox docs cover functionality but not storage location or residency controls. Community items are unrelated to data residency and are ignored. missing for 10: any documentation of region/residency options, data center locations, or configurable data storage location.", "evidenceIds": [] }, { "productId": "deel", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation, settings, or policy statements about opting out of AI model training on user data—only API/MCP integration docs and unrelated community complaints about data sharing for marketing. Since Deel exposes workforce data via MCP to AI agents, this is a fair privacy question, but nothing in the pack addresses training-data controls.", "evidenceIds": [] }, { "productId": "deel", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack item describes any Deel feature letting an AI-native user configure data retention periods or delete data used by AI agents/MCP integrations; sandbox reset only pertains to test data, not production or AI-agent data. Community reports (deel-comm-1) even suggest Deel retains and reuses data (e.g., marketing outreach) beyond user control, but this doesn't confirm a specific retention/deletion control feature exists to be disputed.", "evidenceIds": [] }, { "productId": "deel", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item addresses telemetry/usage-tracking opt-out controls for Deel's platform, API, or MCP server; community evidence even raises concerns about Deel using customer/worker data for its own marketing purposes, but nothing documents an opt-out mechanism one way or the other.", "evidenceIds": [] }, { "productId": "deel", "storyId": "pto-policies-and-accruals", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows a generic 'createTimeOffRequest' MCP/API tool for submitting a time-off request; there is no documentation of defining PTO accrual policies, approval workflows, or automatic application of those policies to payroll runs. missing for 10: PTO policy configuration, accrual rule definitions, approval workflow documentation, and evidence linking time-off data to payroll processing.", "evidenceIds": [ "deel-docs-9", "deel-docs-20", "deel-docs-30" ] }, { "productId": "deel", "storyId": "retirement-plan-sync", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions 401(k), retirement plans, or benefits administration syncing with payroll; the pack only covers global payroll, contracts, MCP/API tooling, and unrelated community complaints.", "evidenceIds": [] }, { "productId": "deel", "storyId": "run-payroll-end-to-end", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Deel's marketing pages claim it can 'run accurate, compliant payroll' and 'process payroll globally' across 150+ countries, implying payroll execution capability, but there is no documentation of the actual end-to-end flow (reviewing hours/earnings, previewing totals, submitting) as a single unified action — the API/MCP evidence only covers contracts, time-off requests, and cost comparisons, not a payroll run review-preview-submit sequence. Missing for 10: explicit description or screenshot/API of the review-hours step, a totals-preview step, and a single submit action tying them together.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-24", "deel-docs-12", "deel-docs-25" ] }, { "productId": "deel", "storyId": "self-serve-employee-onboarding", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers Deel's API/MCP developer tools, payroll/contract endpoints, and community complaints, but contains no mention of a self-serve onboarding flow, W-4/I-9 collection, or bank detail setup for new hires. Onboarding is plausibly a core Deel HR feature, but no evidence documents this specific capability, so it cannot be credited as delivered.", "evidenceIds": [] }, { "productId": "deel", "storyId": "time-tracking-into-payroll", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Deel's payroll platform and MCP tools cover contracts, people, payroll, and time-off requests, but nothing documents hourly time entry tracking or overtime calculations flowing into a payroll run. Missing for 10: hourly time entry logging, overtime calculation rules, and explicit integration of time-tracking data into payroll processing.", "evidenceIds": [ "deel-docs-11", "deel-docs-19", "deel-docs-20", "deel-docs-30" ] }, { "productId": "deel", "storyId": "year-end-forms", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence pack covers Deel's API, MCP server, sandbox, and general global payroll/EOR marketing claims, but contains no mention of W-2/1099 tax form generation or year-end distribution to workers.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "accounting-software-sync", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "Gusto states it 'works with many types of apps, including accounting... software' but no evidence specifies automatic payroll journal entry sync, journal entry mapping, or named integrations like QuickBooks/Xero. Missing for 10: explicit QuickBooks/Xero integration docs, journal entry field mapping, and automatic sync confirmation or independent user reports of this working.", "evidenceIds": [ "gusto-docs-41" ] }, { "productId": "gusto", "storyId": "agent-onboards-new-hire", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Gusto's Embedded Payroll API docs cover company onboarding, employee tax setup (federal/state), and a paginated /employees endpoint, and the Dev Assistant MCP server lets AI coding tools query the API and docs directly — supporting agent-driven integration work. However, there is no explicit documentation of a compensation-creation endpoint or an end-to-end 'create employee + compensation + tax' flow demonstrated together, and the MCP server is aimed at developers building integrations rather than an agent performing hiring actions itself. Missing for 10: explicit compensation-setup API reference, a documented end-to-end new-hire onboarding sequence, and evidence of an agent actually executing this workflow (not just API capability existing).", "evidenceIds": [ "gusto-docs-60", "gusto-docs-63", "gusto-docs-37", "gusto-docs-43", "gusto-docs-70", "gusto-docs-6", "gusto-docs-34", "gusto-probe-3" ] }, { "productId": "gusto", "storyId": "agent-payroll-preview-anomalies", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Gusto's Embedded Payroll API supports agent-driven interaction: the official MCP server lets AI tools call the API directly, and endpoints exist to retrieve unprocessed/upcoming payrolls (GET /v1/companies/{id}/payrolls) and a contractor payment preview endpoint that surfaces submission_blockers for review before funding. However, there is no documented 'preview' or anomaly-detection endpoint specifically for regular employee payroll runs (only for contractor payment groups), and no explicit anomaly-flagging mechanism (e.g., variance/error detection) is described for the standard payroll approval flow. Missing for 10: a dedicated regular-payroll preview/calculate endpoint, explicit anomaly-detection logic for employee payroll (vs only contractor submission_blockers), and independent evidence of an agent actually performing this workflow end-to-end.", "evidenceIds": [ "gusto-docs-6", "gusto-docs-34", "gusto-docs-66", "gusto-docs-40", "gusto-docs-46", "gusto-docs-27", "gusto-docs-10" ] }, { "productId": "gusto", "storyId": "agent-reconciles-payroll-journal", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Gusto's docs show a general Payroll API (e.g., GET /v1/companies/{id}/payrolls), webhooks for payroll.paid events, and mentions of 'Generate payroll reports' plus integrations with accounting apps, which could support an agent pulling payroll data programmatically. However, there is no explicit documentation of a payroll journal-entry export, GL-mapping, or reconciliation feature, and the MCP server referenced is a dev-assistant tool for building integrations (coding help), not an agent-facing data-pull/reconciliation workflow. Missing for 10: explicit journal entry/GL export endpoint, documented reconciliation workflow, and evidence of an agent (not just a developer) performing the reconciliation end-to-end.", "evidenceIds": [ "gusto-docs-40", "gusto-docs-44", "gusto-docs-41", "gusto-docs-5", "gusto-docs-16", "gusto-docs-6" ] }, { "productId": "gusto", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Gusto hosts a verified llms.txt (HTTP 200) and .md-formatted docs (docs-md probe), plus an official MCP server for AI code editors/assistants to interact with docs and API, directly matching the story. Missing for 10: independent third-party confirmation of agents successfully using llms.txt in practice.", "evidenceIds": [ "gusto-probe-1", "gusto-probe-2", "gusto-probe-3", "gusto-docs-6", "gusto-docs-34" ] }, { "productId": "gusto", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence only covers Gusto's Embedded Payroll developer platform (APIs, webhooks, SDKs) and a developer-facing MCP server for AI coding assistants to interact with the API/docs — none of this is an in-product feature that surfaces AI-generated insights or suggestions to end users based on their own payroll/HR data. No dashboard analytics, anomaly detection, or AI recommendations for users are documented.", "evidenceIds": [ "gusto-docs-6", "gusto-docs-34", "gusto-docs-66" ] }, { "productId": "gusto", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Gusto's evidence shows webhooks for event notification and pre-generated scheduled payrolls, plus an MCP server aimed at AI coding assistants for development-time API/doc lookup — none of these constitute a user-configurable system for autonomous background agent automations. Missing for 10: any workflow/automation builder, agentic scheduling of tasks beyond fixed payroll cadence, or evidence of AI agents autonomously executing multi-step Gusto actions unsupervised.", "evidenceIds": [ "gusto-docs-5", "gusto-docs-16", "gusto-docs-62", "gusto-docs-6" ] }, { "productId": "gusto", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence only shows a developer-facing MCP server that lets external AI coding tools (Cursor, Windsurf, Claude Desktop) interact with the Embedded Payroll API for building integrations — this is a dev-tooling integration, not a built-in AI assistant inside the Gusto product for end users to delegate payroll/HR tasks. No evidence of an in-app AI assistant, chat interface, or agentic feature for end users.", "evidenceIds": [ "gusto-docs-6", "gusto-docs-34", "gusto-docs-66", "gusto-probe-3" ] }, { "productId": "gusto", "storyId": "agentic-headless", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Gusto Embedded Payroll is an API-first product with REST endpoints, idempotency keys, and webhooks that inherently support headless/automated integration (e.g., docs-8, docs-17, docs-24, docs-16), and demo companies exist for automated testing (docs-13). However, there is no explicit CI/CD documentation, SDK, or CLI tooling described for running Gusto in automated pipelines, and the MCP server is aimed at AI coding assistants, not CI automation. Missing for 10: explicit CI/pipeline integration guides, official SDKs/CLI for scripted automation, and independent evidence of headless usage in production automation.", "evidenceIds": [ "gusto-docs-8", "gusto-docs-17", "gusto-docs-24", "gusto-docs-16", "gusto-docs-13", "gusto-docs-6" ] }, { "productId": "gusto", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "medium", "rationale": "Gusto is a payroll/HR SaaS platform, not an AI agent or assistant that itself consumes external tools; the evidence only shows Gusto exposing its own MCP server for other AI coding tools to call into (the reverse direction), which doesn't establish Gusto as consuming/plugging in external MCP servers.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Gusto documents an official Embedded Dev Assistant MCP server that lets AI code editors (Cursor, Windsurf) and general tools (Claude Desktop) interact directly with the Embedded Payroll API and docs, confirmed by both docs and a probe hit. Missing for 10: independent/hands-on community corroboration of the MCP server working in practice, and details on setup/auth specifics beyond the docs page.", "evidenceIds": [ "gusto-docs-6", "gusto-docs-34", "gusto-docs-66", "gusto-probe-3" ] }, { "productId": "gusto", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Gusto ships an official Embedded Dev Assistant MCP server letting AI coding tools (Cursor, Windsurf, Claude Desktop) interact with its API and docs, which enables some natural-language-driven operation during integration/development [gusto-docs-6][gusto-docs-34][gusto-docs-66][gusto-probe-3]. However this is a developer-integration tool, not evidence that end-users can operate core Gusto payroll/HR workflows (running payroll, approving time off, etc.) via natural-language commands in the product itself. Missing for 10: an end-user-facing conversational/NL interface for actual payroll operations, and independent hands-on validation of the MCP server's capabilities.", "evidenceIds": [ "gusto-docs-6", "gusto-docs-34", "gusto-docs-66", "gusto-probe-3" ] }, { "productId": "gusto", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Gusto provides an MCP server, React SDK, and API client libraries, but there is no evidence of an official CLI tool for AI-native workflows anywhere in the docs pack; missing for 10: any mention of a Gusto CLI, its installation, or command set.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "agentic-public-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Gusto Embedded Payroll provides a comprehensive, well-documented public REST API covering payroll, contractors, time off, webhooks, versioning, authentication, idempotency, pagination, error handling, official client libraries/SDKs, and even an official MCP server enabling AI agents to interact directly with the API and docs. This is extensive first-party documentation with a probe confirming the docs endpoints resolve live; missing for 10: independent third-party developer accounts of building against the API to corroborate the docs.", "evidenceIds": [ "gusto-docs-6", "gusto-docs-34", "gusto-docs-66", "gusto-docs-54", "gusto-docs-53", "gusto-docs-67", "gusto-docs-70", "gusto-docs-8", "gusto-docs-25", "gusto-docs-43", "gusto-probe-3", "gusto-probe-2" ] }, { "productId": "gusto", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Gusto's API has authentication constructs like 'System access tokens' for application-level actions and an MCP server for AI tools to call the API, but nothing describes issuing scoped or least-privilege credentials specifically for an AI agent (e.g., granular permission scopes, agent-specific token types, or restricted access grants). Missing for 10: any documentation of scoped/limited-permission API keys or tokens tailored to AI-agent use, OAuth scope definitions, or least-privilege credential issuance workflow.", "evidenceIds": [ "gusto-docs-70", "gusto-docs-66", "gusto-docs-34" ] }, { "productId": "gusto", "storyId": "agentic-sdks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Gusto documents official client libraries/SDKs for multiple languages plus a dedicated React SDK, providing developers with official building blocks. Missing for 10: independent hands-on developer corroboration of SDK quality/coverage across all languages and no explicit list of supported languages beyond React.", "evidenceIds": [ "gusto-docs-53", "gusto-docs-54", "gusto-docs-65" ] }, { "productId": "gusto", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Gusto's docs describe a full webhook subscription system: creating subscriptions with subscription_types (gusto-docs-56), verifying via a token before events are sent (gusto-docs-71), HMAC signature verification (gusto-docs-23), specific events like payroll.paid (gusto-docs-16/22/49/59), and a health-check endpoint (gusto-docs-57). This is well-documented first-party API capability suitable for AI-native/event-driven integration. Missing for 10: independent/hands-on developer confirmation of webhook reliability and a broader catalog of subscription event types beyond payroll.paid.", "evidenceIds": [ "gusto-docs-5", "gusto-docs-16", "gusto-docs-22", "gusto-docs-23", "gusto-docs-49", "gusto-docs-56", "gusto-docs-57", "gusto-docs-71" ] }, { "productId": "gusto", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows extensive reference documentation, endpoint docs, Postman collections, and client SDKs, but nothing describes an interactive in-browser API reference with runnable/try-it examples (e.g., a live console or embedded code execution). Demo companies (gusto-docs-13) and Postman collections (gusto-docs-68) support testing workflows but are not the same as an interactive runnable reference UI.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "api-machine-spec", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Gusto publishes versioned Postman collections for its API (gusto-docs-68) and has structured, versioned reference docs (gusto-docs-67, gusto-docs-69), which are machine-readable-adjacent artifacts, but there is no explicit mention of a downloadable OpenAPI/Swagger spec file or equivalent standard schema. missing for 10: explicit OpenAPI/Swagger spec, a documented download link or endpoint for the raw spec, and confirmation of spec format/versioning compatibility with standard tooling.", "evidenceIds": [ "gusto-docs-68", "gusto-docs-67", "gusto-docs-69" ] }, { "productId": "gusto", "storyId": "api-sandbox", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Gusto's docs mention that 'Demo companies are automatically generated with company info, employees, and previous payrolls so you can begin testing right away' (gusto-docs-13), which supports sandbox-style testing without touching production data. However, this is a single, brief mention with no further detail on sandbox API endpoints, environment separation, or independent confirmation of its reliability. missing for 10: explicit sandbox API/environment documentation beyond demo companies, details on how sandbox vs production keys/environments are isolated, and independent/hands-on verification of the sandbox experience.", "evidenceIds": [ "gusto-docs-13" ] }, { "productId": "gusto", "storyId": "api-versioning-policy", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Gusto documents explicit API versioning (X-Gusto-API-Version header, per-version Postman collections, version-gated error formats since 2023-02-01), showing a real versioning scheme. However, the evidence pack contains no explicit deprecation policy (e.g., sunset timelines, notice periods, migration guides between versions). Missing for 10: documented deprecation/sunset policy, migration guidance between API versions, and independent confirmation of how version transitions are handled in practice.", "evidenceIds": [ "gusto-docs-67", "gusto-docs-68", "gusto-docs-69" ] }, { "productId": "gusto", "storyId": "automatic-tax-filing", "verdict": "disputed", "quality": 6, "confidence": "medium", "rationale": "Gusto's docs explicitly claim automatic federal/state/local tax calculation, filing, and remittance as a core Embedded Payroll feature (gusto-docs-44, gusto-docs-52, gusto-docs-58, gusto-docs-45, gusto-docs-63), which is a strong first-party claim covering the full story. However, independent community reports describe a concrete tax-filing failure — W-2c corrections causing 2021 Q1 payroll to be double-reported to the IRS with support unable to resolve it — directly contradicting the 'automatically calculated and filed correctly' claim. missing for 10: independent third-party audit or hands-on verification showing reliable accuracy at scale, and no rebuttal/fix documentation for the cited filing error.", "evidenceIds": [ "gusto-docs-44", "gusto-docs-52", "gusto-docs-58", "gusto-docs-63", "gusto-docs-45", "gusto-comm-11", "gusto-comm-12" ] }, { "productId": "gusto", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Gusto's API supports pagination and individual payroll/contractor payment operations, but there is no evidence of true bulk/batch endpoints (e.g., bulk employee creation, bulk payroll processing, batch contractor payments in a single call) that an AI-native user could invoke to operate across many items at once. missing for 10: bulk/batch API endpoints, batch job or async bulk-processing documentation, evidence of multi-item operations beyond single-resource calls and pagination.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Gusto Embedded exposes webhooks for events like payroll.paid, contractor payment states, and time-off requests, letting a developer's application 'perform subsequent business logic' after an event fires — this is event notification infrastructure rather than a native rules engine where an end user defines conditional automation logic inside Gusto itself. Missing for 10: no in-product rule/condition builder, no support for chaining multiple actions or conditional branching declaratively, and no evidence of AI-native or no-code rule definition beyond raw webhook subscriptions that require the partner to write their own business logic.", "evidenceIds": [ "gusto-docs-5", "gusto-docs-16", "gusto-docs-22", "gusto-docs-49", "gusto-docs-56", "gusto-docs-71", "gusto-docs-23" ] }, { "productId": "gusto", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Gusto's docs describe automatic recurring payroll generation based on a company's pay schedule (docs-62) and webhooks for event-driven integration, but there is no evidence of an AI-native user or agent being able to define, schedule, or manage recurring automated jobs/workflows themselves via API, MCP server, or any workflow engine — the recurring behavior is a fixed internal payroll process, not a configurable automation primitive.", "evidenceIds": [ "gusto-docs-62", "gusto-docs-40", "gusto-docs-46", "gusto-docs-6" ] }, { "productId": "gusto", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Gusto is a payroll/HR API platform with no mention of automation versioning, change review, or rollback for workflows/automations; only unrelated concepts like idempotency keys and record version fields for concurrency control appear, which are not automation version control.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "cancel-or-correct-payroll", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Docs describe off-cycle payrolls for handling 'corrections' (gusto-docs-4, gusto-docs-21, gusto-docs-32) and show that upcoming payrolls can be queried with processing_statuses=unprocessed (gusto-docs-46), implying visibility into payrolls not yet finalized, but there is no documented API/UI action to explicitly cancel or edit a submitted payroll before it pays employees. Missing for 10: an explicit 'cancel/void submitted payroll' endpoint or workflow, confirmation of edit windows before check date, and independent/hands-on evidence that corrections actually stop a pending pay run rather than creating a separate off-cycle run after the fact.", "evidenceIds": [ "gusto-docs-4", "gusto-docs-21", "gusto-docs-32", "gusto-docs-46", "gusto-docs-40" ] }, { "productId": "gusto", "storyId": "compliance-alerts", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack covers Gusto Embedded Payroll's API/webhook infrastructure for developers building on Gusto, plus community sentiment on support quality — none of it describes a founder-facing proactive compliance alert system for new hires, new locations, or law changes. Webhooks (e.g., payroll.paid) are developer integration events, not compliance-obligation notifications to founders.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "embedded-payroll-for-platforms", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Gusto Embedded Payroll is an extensive, well-documented partner API/platform explicitly designed for developers to white-label payroll (onboarding, payroll runs, contractors, time off, webhooks, tax, benefits add-ons, SDKs, versioning, idempotency) into their own product. Evidence includes first-party docs, SDKs (React, API clients), and a dedicated MCP dev-assistant server. missing for 10: independent hands-on developer reviews of the embedded API itself (community evidence is about core Gusto payroll/support, not the embedded/partner API), and no case studies of live partner integrations.", "evidenceIds": [ "gusto-docs-1", "gusto-docs-14", "gusto-docs-38", "gusto-docs-44", "gusto-docs-52", "gusto-docs-53", "gusto-docs-54", "gusto-docs-70", "gusto-probe-3" ] }, { "productId": "gusto", "storyId": "fast-direct-deposit", "verdict": "disputed", "quality": 5, "confidence": "medium", "rationale": "Gusto's docs clearly describe next-day, 2-day, and standard 4-day direct deposit payroll options as a core capability (gusto-docs-3, gusto-docs-15, gusto-docs-58), fully replacing check-writing with automated bank transfers. However, a hands-on customer account (gusto-comm-5) reports that 2-day payroll was capped at ~$60k regardless of bank balance, requiring manual exception requests every pay cycle, ultimately driving them to switch providers — a concrete contradiction of the frictionless fast-deposit claim. missing for 10: independent confirmation that the cap issue is resolved or was an isolated case, and no evidence of uncapped fast-deposit reliability at scale.", "evidenceIds": [ "gusto-docs-3", "gusto-docs-15", "gusto-docs-58", "gusto-comm-5" ] }, { "productId": "gusto", "storyId": "flexible-pay-schedules", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Gusto's docs confirm multi-location companies can have different pay schedules ('might want everyone paid at the same time, or prefer different pay schedules based on location or job type') and that payrolls are auto-generated per company's pay schedule and pay periods, supporting the general capability. However, the pack never explicitly enumerates the specific frequency types (weekly, biweekly, semimonthly, monthly) or shows an API/UI flow for configuring multiple schedules per team. missing for 10: explicit list of supported pay frequencies, documented API/UI steps for creating/assigning schedules to specific teams.", "evidenceIds": [ "gusto-docs-31", "gusto-docs-48", "gusto-docs-62", "gusto-docs-60" ] }, { "productId": "gusto", "storyId": "global-payroll-eor", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "All Gusto documentation describes US-based payroll (EIN, federal/state/local tax filings) with no mention of employer-of-record services or international entity payroll, and community evidence explicitly states Gusto lacks support for employees outside the US and cannot handle staff spread across multiple countries.", "evidenceIds": [ "gusto-comm-5", "gusto-comm-7", "gusto-docs-37", "gusto-docs-63" ] }, { "productId": "gusto", "storyId": "health-benefits-administration", "verdict": "disputed", "quality": 4, "confidence": "low", "rationale": "Docs confirm Gusto offers health insurance administration via its SimplyInsured partner integration as part of the platform ecosystem [gusto-docs-39], implying enrollment/deduction handling analogous to its 401(k) Guideline flow, but there is no first-party documentation detailing how health-insurance deductions specifically sync to payroll. Independent, hands-on reports directly contradict smooth benefits administration: one describes Gusto failing to correctly terminate an employee's health plan causing prolonged billing problems [gusto-comm-14], and another describes being unable to customize plans for a multi-state/country workforce, leading them to switch providers [gusto-comm-7]; platform lock-in around benefits features is also noted [gusto-comm-4]. Missing for 10: explicit docs on health-insurance enrollment-to-payroll-deduction sync mechanics, resolution/rebuttal of the termination-failure report, and independent corroboration of successful multi-state benefits administration.", "evidenceIds": [ "gusto-docs-39", "gusto-comm-14", "gusto-comm-7", "gusto-comm-4" ] }, { "productId": "gusto", "storyId": "international-contractor-payments", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Gusto's embedded payroll docs describe US-based contractor payments (direct deposit, check) but no international/local-currency payment support or compliant international contractor agreements are documented; community feedback explicitly states 'Gusto doesn't support outside of US folks,' reinforcing the absence of this capability.", "evidenceIds": [ "gusto-docs-9", "gusto-docs-18", "gusto-docs-26", "gusto-docs-61", "gusto-comm-5" ] }, { "productId": "gusto", "storyId": "multi-state-payroll", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Gusto's platform docs explicitly state it handles multi-state tax requirements, multi-location payroll with different schedules, and 'federal, state, and local filings and payments,' plus employee onboarding requires both federal and state tax configuration (docs-44, docs-48, docs-52, docs-63). This directly matches the story of running payroll across states with correct withholdings/registrations. missing for 10: explicit documentation on the mechanics of new-state tax registration/EIN setup, and independent hands-on confirmation that multi-state tax filings are error-free (community evidence only covers support/benefits complaints, not multi-state tax accuracy).", "evidenceIds": [ "gusto-docs-44", "gusto-docs-48", "gusto-docs-52", "gusto-docs-63", "gusto-docs-31" ] }, { "productId": "gusto", "storyId": "off-cycle-payroll-run", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Gusto's docs explicitly cover off-cycle payroll creation for bonuses/corrections (gusto-docs-4, gusto-docs-21, gusto-docs-32) with a dedicated 'create-an-off-cycle-payroll' guide, specific handling of bonus withholding rules (gusto-docs-47), and platform-level messaging that termination processing and off-cycle payments are supported (gusto-docs-52, gusto-docs-44). Missing for 10: no independent/hands-on community verification specifically of the off-cycle run flow (community evidence is about general payroll/support, not off-cycle runs), and no detail on termination-specific off-cycle nuances beyond bonus example.", "evidenceIds": [ "gusto-docs-4", "gusto-docs-21", "gusto-docs-32", "gusto-docs-47", "gusto-docs-52", "gusto-docs-44" ] }, { "productId": "gusto", "storyId": "offer-letters-and-documents", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence pack covers payroll, contractor payments, time off, benefits, and API/webhook infrastructure extensively, but nowhere mentions offer letters, e-signature, or per-employee HR document storage — this is a distinct HR document management feature not evidenced here.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Gusto's Embedded Payroll API surface is extensive—covering onboarding, payroll runs (regular/off-cycle/contractor), tax configuration, time-off requests/approvals, benefits links, and webhooks—and docs explicitly say partners can 'build custom experiences using APIs' or use pre-built UI Flows interchangeably (gusto-docs-38, gusto-docs-44, gusto-docs-52). This implies broad but not confirmed 1:1 parity between UI actions and API actions. missing for 10: an explicit statement or audit confirming every UI action (e.g., admin dashboard settings, reporting/export UI, benefits marketplace configuration) has a corresponding API endpoint, and independent/hands-on verification that no UI-only features exist.", "evidenceIds": [ "gusto-docs-38", "gusto-docs-44", "gusto-docs-52", "gusto-docs-19", "gusto-docs-40", "gusto-docs-53", "gusto-docs-54" ] }, { "productId": "gusto", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers Gusto's Embedded Payroll API, webhooks, SDKs, and docs, but contains no mention of a bulk data-export feature, open-format export (CSV/JSON dumps), or an account-closure/data-portability workflow. Community threads mention users switching away to competitors but never describe exporting their data in an open format when leaving.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Gusto is a closed commercial SaaS payroll/HR platform, not open-source software; source code availability under an open license is not a relevant axis for this kind of product.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Gusto is a payroll/HR SaaS platform, not infrastructure software; self-hosting the core product is a category error for this kind of service since payroll processing inherently requires the vendor's regulated, hosted infrastructure (tax filings, bank transfers, compliance).", "evidenceIds": [] }, { "productId": "gusto", "storyId": "pay-employees-and-contractors", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Gusto's Embedded Payroll docs detail full W-2 employee payroll processing (regular/off-cycle, tax filing, multi-location, benefits) alongside dedicated contractor payment APIs (direct deposit, check, historical payment, submission blockers) all within the same platform/API, confirming ops users can manage both worker types from one system. Missing for 10: independent hands-on report explicitly confirming a single payroll run mixing W-2 and 1099 payments, and broader community corroboration beyond docs.", "evidenceIds": [ "gusto-docs-44", "gusto-docs-52", "gusto-docs-9", "gusto-docs-27", "gusto-docs-28", "gusto-docs-60", "gusto-docs-2" ] }, { "productId": "gusto", "storyId": "payroll-event-webhooks", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Gusto's docs clearly describe a webhooks infrastructure with subscription creation, verification (HMAC), a payroll.paid event, and a health-check endpoint, directly supporting the 'payroll processed' automation use case. However, the evidence pack does not name or document specific 'employee onboarded' or 'payment failed' webhook event types, only the payroll.paid event is explicitly cited. Missing for 10: documented onboarding-event and payment-failure-event webhook types, and independent/hands-on confirmation of webhook reliability in production.", "evidenceIds": [ "gusto-docs-5", "gusto-docs-16", "gusto-docs-22", "gusto-docs-23", "gusto-docs-49", "gusto-docs-56", "gusto-docs-57", "gusto-docs-71" ] }, { "productId": "gusto", "storyId": "payroll-reports-exports", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The only direct evidence is a single bullet listing \"Generate payroll reports\" among platform capabilities, with no detail on payroll register format, gross-to-net breakdowns, or export/download options for offline analysis. Missing for 10: documentation of report content/format, gross-to-net specificity, export file types (CSV/PDF), and any independent confirmation that ops users can actually pull and export these reports.", "evidenceIds": [ "gusto-docs-44" ] }, { "productId": "gusto", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions data residency, regional storage options, or geographic data controls for Gusto; Gusto's US-focused payroll model is even called out in community evidence as not supporting non-US operations, but that doesn't address configurable data residency choices for the buyer. This is an applicable axis for a data-handling B2B/embedded platform, so absence of evidence yields 'none' rather than 'na'.", "evidenceIds": [ "gusto-comm-5" ] }, { "productId": "gusto", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses AI training data usage or opt-out controls; Gusto is a payroll/HR platform and the evidence covers payroll APIs, webhooks, MCP dev tools, etc., with nothing about AI model training data policies.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no documentation of data retention policies, deletion controls, or privacy/GDPR-style data management APIs for AI-native users; all evidence covers payroll processing, webhooks, contractor payments, and MCP dev tooling, none of which address retention/deletion controls.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry/usage-tracking opt-out settings for AI-native users; Gusto's docs cover payroll APIs, webhooks, MCP server, and SDKs but nothing about privacy controls or telemetry opt-out. Missing for 10: any documentation of telemetry collection, usage tracking, or an opt-out mechanism.", "evidenceIds": [] }, { "productId": "gusto", "storyId": "pto-policies-and-accruals", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Gusto Embedded's docs show a full time-off request lifecycle API — balance checking, submission, employer approval/decline, and payroll integration (gusto-docs-11, gusto-docs-19, gusto-docs-29, gusto-docs-51, gusto-docs-55) — which supports approvals flowing into payroll automatically. However, there's no evidence of ops-configurable PTO *policy* definition (accrual rates, carryover rules, policy types) being exposed via API/UI, only that balances can be checked and requests approved. Missing for 10: documentation of accrual policy creation/configuration, accrual rate rules, and independent/hands-on confirmation that approvals auto-apply to payroll runs.", "evidenceIds": [ "gusto-docs-11", "gusto-docs-19", "gusto-docs-29", "gusto-docs-51", "gusto-docs-55", "gusto-docs-12" ] }, { "productId": "gusto", "storyId": "retirement-plan-sync", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Gusto's embedded platform lists 401(k) via Guideline as a supported benefit and documents a flow for generating admin access links to Guideline through Gusto Embedded's pre-built flows, implying integration between payroll and the retirement plan provider. However, the docs never explicitly describe automatic contribution syncing with each payroll run — only account-access link generation is documented. missing for 10: explicit documentation of per-payroll automatic contribution deduction/sync mechanics, and independent/hands-on confirmation that 401(k) contributions actually flow through automatically each pay cycle.", "evidenceIds": [ "gusto-docs-36", "gusto-docs-39", "gusto-docs-42", "gusto-docs-50", "gusto-docs-64" ] }, { "productId": "gusto", "storyId": "run-payroll-end-to-end", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Gusto's Embedded Payroll docs describe the components of a payroll run — retrieving upcoming/unprocessed payrolls (gusto-docs-40, gusto-docs-46), a guide titled 'complete-a-regular-payroll' implying a full review-to-submit flow, off-cycle payroll creation (gusto-docs-32), and platform-overview claims that Gusto 'handles everything from tax calculations to bank transfers' (gusto-docs-58, gusto-docs-44). However, unlike the contractor-payment flow which explicitly documents a preview endpoint (gusto-docs-27), no evidence explicitly shows a 'preview totals' step for regular employee payroll before submission, and all evidence is API/developer-facing rather than showing the actual end-to-end ops-user UI experience. Missing for 10: an explicit preview-totals endpoint/step for regular payroll runs, and direct evidence (docs or hands-on) of the single consolidated UI flow an ops user would use rather than API building blocks.", "evidenceIds": [ "gusto-docs-40", "gusto-docs-46", "gusto-docs-44", "gusto-docs-58", "gusto-docs-32", "gusto-docs-27" ] }, { "productId": "gusto", "storyId": "self-serve-employee-onboarding", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Docs show pieces of new-hire onboarding data collection — employees configuring federal/state tax info (W-4 equivalent) and companies/employees needing bank account information — but there is no mention of I-9 collection or an explicit self-serve 'before day one' onboarding flow sent to a new hire; most evidence is API/company-onboarding oriented (Embedded Payroll platform) rather than a described ops-facing new-hire onboarding UX. Missing for 10: I-9 collection, explicit self-serve pre-day-one flow/UI for new hires, confirmation this exists in core Gusto product (not just the Embedded API).", "evidenceIds": [ "gusto-docs-60", "gusto-docs-63", "gusto-docs-37", "gusto-docs-2" ] }, { "productId": "gusto", "storyId": "time-tracking-into-payroll", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Gusto's docs cover time-off (PTO) request/approval APIs and payroll processing/off-cycle runs, and mention generic integrations with 'time tracking software' apps, but there is no documentation of native hourly time-entry capture or overtime calculation logic that flows directly into a payroll run. The evidence only implies this happens via unspecified third-party time-tracking integrations rather than a built-in Gusto feature. missing for 10: dedicated hourly timesheet/time-entry API, overtime rule/calculation documentation, explicit description of how hourly+overtime data is ingested into a payroll run.", "evidenceIds": [ "gusto-docs-41", "gusto-docs-11", "gusto-docs-44", "gusto-docs-62" ] }, { "productId": "gusto", "storyId": "year-end-forms", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "Gusto's docs claim broad automatic tax compliance ('Calculate and file taxes automatically', 'Tax configuration and compliance', 'federal tax information to file and pay taxes correctly') implying year-end tax form handling, but no doc explicitly describes automatic W-2/1099 generation and distribution to workers. A concrete community report describes Gusto incorrectly reissuing 2021 W-2 forms as W-2c forms that combined two tax IDs, causing double reporting to the IRS and unresponsive support on the issue — a documented failure in exactly this workflow. missing for 10: explicit vendor documentation of automatic W-2/1099 generation/e-filing/distribution timeline, and independent evidence the process works reliably at scale.", "evidenceIds": [ "gusto-docs-44", "gusto-docs-45", "gusto-docs-37", "gusto-comm-11", "gusto-comm-12" ] }, { "productId": "justworks", "storyId": "accounting-software-sync", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Docs describe a documented Xero integration where pay types map to Chart of Accounts, with department/office/employee-level overrides, and invoices can auto-sync the day after payroll processing (justworks-docs-12, -5, -19, -6, -13, -20, -25). This directly matches the story of syncing payroll journal entries to accounting software automatically. Missing for 10: explicit QuickBooks integration details (only Xero is documented) and independent/hands-on corroboration beyond vendor help docs.", "evidenceIds": [ "justworks-docs-12", "justworks-docs-5", "justworks-docs-19", "justworks-docs-6", "justworks-docs-13", "justworks-docs-20", "justworks-docs-25", "justworks-docs-26" ] }, { "productId": "justworks", "storyId": "agent-onboards-new-hire", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any public API for creating employees, compensation, or tax setup — probes for llms.txt and OpenAPI specs both returned 404, and all documentation describes manual UI workflows (Time Off tab, Pay menu, Xero integration setup) rather than programmatic onboarding endpoints.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2", "justworks-docs-4", "justworks-docs-8", "justworks-docs-17" ] }, { "productId": "justworks", "storyId": "agent-payroll-preview-anomalies", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any API for payroll preview, run automation, or anomaly detection; probes for llms.txt and OpenAPI specs both return 404, and docs describe only manual UI workflows for payroll review.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2", "justworks-docs-1", "justworks-docs-9" ] }, { "productId": "justworks", "storyId": "agent-reconciles-payroll-journal", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Justworks provides a Custom Payroll Report in Analytics and native Xero GL-mapping/sync (with department/office/employee-level overrides and manual or automatic invoice sync) that could serve as an export/reconciliation path, but there is no evidence of a public API, and probes explicitly show no OpenAPI spec or llms.txt endpoint, so an agent could not pull data programmatically as described. missing for 10: documented payroll/journal API for agent access, evidence of agent-friendly export automation, confirmation that Custom Payroll Report can be pulled without manual UI steps.", "evidenceIds": [ "justworks-docs-1", "justworks-docs-5", "justworks-docs-6", "justworks-docs-12", "justworks-docs-13", "justworks-docs-25", "justworks-docs-26", "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The probe explicitly shows llms.txt returns 404 and no agent-oriented docs (openapi/well-known) exist; no evidence of any AI-agent-facing documentation format.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions AI-generated insights, suggestions, analytics recommendations, or any AI/ML feature surfaced to users; the docs cover only manual payroll, benefits, time-off, and Xero integration workflows. Missing for 10: any mention of AI-driven insights, automated suggestions, or predictive analytics within Justworks.", "evidenceIds": [ "justworks-docs-1", "justworks-docs-9", "justworks-docs-21" ] }, { "productId": "justworks", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Justworks is an HR/payroll PEO platform; the evidence pack shows no mention of automations, workflows, agents, or AI-driven background processes—only manual payroll, benefits, time-off, and integration setup steps. No documented capability for autonomous or agentic automation exists, so this applicable axis is unmet.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any built-in AI assistant or agentic delegation feature within Justworks; all evidence pertains to HR/payroll workflows (payroll, benefits, time off, integrations) with no mention of AI capabilities.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Justworks is an HR/payroll/benefits SaaS platform for humans to manage payroll, time off, and integrations via a web UI; there is no concept of headless/CI automation for this kind of product's core workflows. This axis is a category error for an HR/PEO platform, not a missing capability.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Justworks is an HR/payroll SaaS platform, not an AI agent, and this MCP-plugin story applies to agent products acting as MCP clients; no evidence suggests Justworks functions as an AI agent that consumes MCP tools.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Justworks is a PEO/HR SaaS platform, so an official MCP server is a plausible axis, but there is no evidence of any MCP server offering; probes for llms.txt and OpenAPI specs both returned 404, and all docs relate to payroll/benefits/integrations with Xero, not agent connectivity.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any natural-language command interface, chatbot, or AI assistant within Justworks; all documentation describes manual UI navigation (clicking menus, tabs, buttons). Probes for llms.txt and OpenAPI also failed, indicating no AI-native interface infrastructure.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an official CLI for Justworks; the evidence pack only covers HR/payroll web UI features and shows failed probes for llms.txt and OpenAPI specs, with no mention of any command-line tool.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a documented public API for Justworks; probes for llms.txt and OpenAPI/swagger specs all returned 404, and the help docs only cover UI-based workflows (payroll, benefits, time off, integrations), not API access.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any API, API credentials, or scoped/least-privilege access token system; probes for llms.txt and OpenAPI specs both returned 404. This is an applicable axis for an HR platform (many SaaS HR tools expose scoped API tokens), but Justworks shows no such capability in the evidence pack.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any official SDKs, API client libraries, or developer-facing API documentation; probes for llms.txt and OpenAPI specs both returned 404s, and all docs relate to HR/payroll product usage, not developer integration.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions webhooks or event subscription APIs; documentation only covers payroll, benefits, time-off, and Xero integration workflows. Probes for API/OpenAPI specs also returned 404s, indicating no discoverable webhook or event API.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any API reference, interactive docs, or runnable examples; probes for llms.txt and OpenAPI specs both returned 404, and all other evidence is unrelated help-center content about payroll/benefits/time-off features.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Probes explicitly show no OpenAPI/swagger spec or llms.txt is available at any expected location, and no documentation references a machine-readable API spec.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any sandbox or test environment for Justworks; the evidence pack only covers payroll, benefits, time-off, and Xero integration docs, plus failed probes for API/OpenAPI specs. Missing for 10: any mention of a sandbox/test mode, staging environment, or non-production API access.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any public API, versioning scheme, or deprecation policy; probes for llms.txt and OpenAPI specs both returned 404, and all documentation is about HR/payroll product usage, not developer APIs.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "automatic-tax-filing", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Evidence shows Justworks collects employee withholding/filing status info and provides payroll accuracy checks, implying tax handling is embedded in payroll runs, but no documentation explicitly confirms automatic calculation, filing, and remittance of federal/state/local payroll taxes. Missing for 10: explicit docs on tax filing cadence, remittance to agencies, and multi-jurisdiction tax compliance guarantees.", "evidenceIds": [ "justworks-docs-7", "justworks-docs-22", "justworks-docs-9" ] }, { "productId": "justworks", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack shows only individual, single-item workflows (setting up one PTO policy, mapping one pay type, recording one fringe benefit) with no mention of bulk/batch operations, CSV import, multi-select actions, or APIs for programmatic bulk processing. There is no evidence of any bulk-operation capability for AI-native or automated workflows.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows only fixed, built-in automations (holiday date rollover, automatic invoice sync) rather than any user-definable rule/trigger-action system; there is no documented workflow builder, conditional rule engine, or custom event-trigger capability in Justworks' help docs or API surface (llms.txt/openapi probes both 404).", "evidenceIds": [ "justworks-docs-24", "justworks-docs-25", "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any automation/workflow scheduling capability (e.g., API, webhooks, recurring job triggers) for AI-native or programmatic use; evidence only covers HR/payroll UI features and confirms absence of API/llms.txt endpoints. Missing for 10: any API or automation framework, scheduling/trigger mechanism, or documentation of recurring workflow support.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack discusses versioning, reviewing, or rolling back automations; Justworks is an HR/payroll PEO platform with no documented automation-versioning or audit/rollback tooling. missing for 10: any version history feature, review/approval workflow for automations, rollback mechanism, or audit trail of automation changes.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "cancel-or-correct-payroll", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers payroll data verification, fringe benefits recording, PTO policies, integrations, and onboarding, but contains no mention of canceling, voiding, or correcting a payroll run once submitted before pay date. Missing for 10: any documentation on payroll cancellation/correction workflow, deadlines for edits after submission, or off-cycle correction process.", "evidenceIds": [ "justworks-docs-1", "justworks-docs-9", "justworks-docs-14", "justworks-docs-21" ] }, { "productId": "justworks", "storyId": "compliance-alerts", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention proactive compliance alerts for new hires, new locations, or law changes; the docs cover payroll accuracy checks, benefits recording, PTO setup, and Xero integration but nothing about automated compliance notifications. Missing for 10: any mention of proactive alerting, multi-state/location compliance triggers, or law-change notifications.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "embedded-payroll-for-platforms", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any partner/embeddable API, white-label payroll offering, or developer platform; probes for OpenAPI/llms.txt returned 404s and all docs are end-user help articles about running payroll within Justworks' own UI, not embedding it into third-party products.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "fast-direct-deposit", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions direct deposit speed, next-day/2-day pay, or check-writing alternatives; the payroll docs cover custom reports, W-4 collection, and fringe benefits but not deposit timing or methods. Missing for 10: any mention of direct deposit, payment speed options, or replacing paper checks.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "flexible-pay-schedules", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "None of the evidence discusses configuring multiple pay schedules (weekly, biweekly, semimonthly, monthly) or assigning different schedules to different teams; the pack covers payroll accuracy checks, fringe benefits recording, PTO policies, Xero integration mapping, and onboarding — none address pay frequency setup. Missing for 10: any documentation of pay schedule configuration, frequency options, or per-team/department schedule assignment.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "global-payroll-eor", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Justworks is a US-focused PEO; the evidence pack covers only domestic payroll, PTO, onboarding, and Xero integration — nothing about employer-of-record services or owned-entity payroll for international employees.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "health-benefits-administration", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers payroll reports, fringe benefits payments, PTO policies, and Xero integration, but contains no documentation about offering or administering health insurance plans, employee enrollment in benefits, or syncing insurance deductions to payroll. Justworks PEO quoting is mentioned only regarding onboarding pricing, not benefits administration or deduction sync mechanics.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "international-contractor-payments", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "None of the evidence mentions international contractor payments, multi-currency payouts, or compliant international contractor agreements — Justworks documentation here covers only US domestic payroll, PEO onboarding, PTO, and Xero integration. Missing for 10: any mention of international contractor support, local currency payout, or compliant global contractor contracts.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "multi-state-payroll", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers general payroll setup, W-4-equivalent withholding collection, benefits recording, and PTO/Xero integration, but nothing addresses multi-state employer tax registrations or per-state withholding/compliance handling that the story specifically asks about.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "off-cycle-payroll-run", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention off-cycle payroll runs, bonus payments, correction runs, or termination pay processing—only recurring payroll, fringe benefits recording, time-off policies, and integrations are documented. Missing for 10: any documentation of off-cycle/supplemental payroll run capability, bonus/termination payment workflows, or scheduling outside the regular cycle.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "offer-letters-and-documents", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "None of the evidence mentions offer letters, e-signature, or document storage per employee; all cited docs relate to payroll, benefits, time off, and accounting integrations. This is an applicable axis for an HR/PEO platform, but there is no evidence Justworks delivers it.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a public API at all — probes for llms.txt and OpenAPI specs both returned 404, and all docs describe UI-only workflows (payroll, time off, benefits, integrations) with no mention of programmatic access matching UI capabilities.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any data export or data portability feature in open formats, nor any documented account-closure/export workflow; evidence only covers payroll, benefits, time off, and Xero integration setup. Probes for llms.txt and OpenAPI both returned 404, suggesting no discoverable API/export tooling.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Justworks is a closed-source commercial HR/PEO SaaS platform, not an open-source project; source code availability is not a fair axis for this kind of product.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Justworks is a SaaS PEO/HR platform delivered as a hosted service; self-hosting the core product is not a coherent concept for this category, similar to expecting source-available deployment of a payroll/benefits SaaS.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "pay-employees-and-contractors", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers Justworks payroll, benefits, time off, and Xero integration features but contains no mention of 1099 contractors or contractor payments anywhere, so there's no evidence the platform supports paying both W-2 employees and 1099 contractors together.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "payroll-event-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any webhook or event subscription capability; probes for API/OpenAPI specs returned 404s and no documentation mentions payroll lifecycle event notifications. Missing for 10: webhook subscription mechanism, documented event types (payroll processed, onboarding, payment failed), any developer API reference.", "evidenceIds": [ "justworks-probe-1", "justworks-probe-2" ] }, { "productId": "justworks", "storyId": "payroll-reports-exports", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Evidence confirms an Analytics > Custom Payroll Report exists for checking payroll data, implying report generation, but there's no explicit mention of gross-to-net reports or export/download functionality for analysis. Missing for 10: explicit gross-to-net report detail, export/download format confirmation (CSV/Excel), and independent corroboration of reporting depth.", "evidenceIds": [ "justworks-docs-1", "justworks-docs-14", "justworks-docs-21", "justworks-docs-9" ] }, { "productId": "justworks", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses data residency, regional storage options, or any data locality controls for Justworks; all cited docs concern payroll, benefits, time off, and Xero integration. Missing for 10: any mention of data center regions, residency options, or storage location controls.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Justworks is a PEO/HR payroll platform; the evidence pack contains only payroll, benefits, time-off, and Xero integration docs with no mention of AI model training, data usage policies, or opt-out controls for AI training. No evidence exists that this capability is addressed at all.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses data retention policies, deletion controls, or any AI-specific privacy/data governance features for Justworks; all evidence concerns payroll, benefits, time off, and Xero integration workflows.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Justworks is a PEO/HR payroll platform, not an AI tool or agent product with telemetry/usage-tracking settings relevant to AI-native workflows; the evidence pack covers payroll, benefits, time off, and Xero integration with no AI or telemetry features at all, so this axis is a category error for this product.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "pto-policies-and-accruals", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm PTO policy setup (name, dates, policy type, timecard sync) and integration with payroll/timecards via docs-3, docs-11, docs-16, plus automated holiday handling (docs-24). However, evidence does not detail accrual rules/rates or an explicit approval workflow for time-off requests feeding into payroll. missing for 10: explicit accrual rate configuration details, documented approval workflow for PTO requests, and independent confirmation that approved PTO flows automatically into payroll processing.", "evidenceIds": [ "justworks-docs-3", "justworks-docs-11", "justworks-docs-16", "justworks-docs-24" ] }, { "productId": "justworks", "storyId": "retirement-plan-sync", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "None of the evidence mentions 401(k)/retirement plan offerings or automatic contribution syncing with payroll; the pack only covers PTO, Xero integration, fringe benefits recording, and onboarding topics.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "run-payroll-end-to-end", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Docs confirm ops can review payroll accuracy (via Custom Payroll Report and employee profiles) before running payroll and can record fringe benefits during the pay flow, implying a review-then-run sequence, but there is no explicit description of a 'preview totals' screen or a single continuous submit action tying review, preview, and submission together. missing for 10: explicit preview-totals step, description of final submit/confirmation action, evidence of a single unified flow rather than separate menu actions.", "evidenceIds": [ "justworks-docs-1", "justworks-docs-9", "justworks-docs-23" ] }, { "productId": "justworks", "storyId": "self-serve-employee-onboarding", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Docs confirm employees self-enroll and Justworks collects W-4 filing/withholding info directly so they don't need to file a W-4 themselves, and general onboarding timelines (2-3 weeks) are documented. However, no evidence explicitly confirms I-9 collection or bank/direct-deposit detail collection as part of a unified self-serve pre-day-one flow. Missing for 10: explicit I-9 collection/verification workflow, explicit bank account/direct deposit setup step, and confirmation these are bundled into one onboarding flow before day one.", "evidenceIds": [ "justworks-docs-7", "justworks-docs-22", "justworks-docs-17", "justworks-docs-4" ] }, { "productId": "justworks", "storyId": "time-tracking-into-payroll", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence covers PTO policy setup, payroll accuracy checks, integrations, and fringe benefits, but there is no mention of hourly time entry tracking or overtime calculation flowing into payroll runs.", "evidenceIds": [] }, { "productId": "justworks", "storyId": "year-end-forms", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "None of the evidence items mention W-2/1099 generation or year-end tax form distribution; the pack only covers payroll reporting, benefits recording, PTO setup, onboarding, and Xero integration. Absence of evidence for this applicable payroll-compliance capability yields 'none'. missing for 10: any documentation of W-2/1099 generation, e-filing, or worker distribution at year-end.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "accounting-software-sync", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Rippling explicitly claims integration with QuickBooks, Xero, and NetSuite for accounting sync (rippling-docs-14), plus general automatic data-flow claims (rippling-docs-13, rippling-docs-10). However, there is no detail on how payroll journal entries specifically map/sync, no documentation of configuration, sync frequency, or error-handling, and no independent/hands-on corroboration confirming this works reliably in practice. Missing for 10: technical details on journal entry mapping, sync frequency/reliability, and independent verification of the accounting sync working correctly.", "evidenceIds": [ "rippling-docs-14", "rippling-docs-13", "rippling-docs-10" ] }, { "productId": "rippling", "storyId": "agent-onboards-new-hire", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "While Rippling advertises unified onboarding, payroll, and developer APIs/sandbox in general (rippling-docs-33, rippling-docs-43, rippling-docs-8), there is no evidence of a documented API or endpoint that lets an agent programmatically create an employee record, set compensation, and configure tax setup end-to-end. Missing for 10: API reference for employee creation/compensation/tax objects, example agent-driven onboarding workflow, and any confirmation this is exposed outside the UI.", "evidenceIds": [ "rippling-docs-33", "rippling-docs-43", "rippling-docs-8" ] }, { "productId": "rippling", "storyId": "agent-payroll-preview-anomalies", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Rippling documents a pay-run comparison feature to catch discrepancies before approval (rippling-docs-1) and offers general developer APIs/sandbox for building custom integrations (rippling-docs-8, rippling-docs-43), which could theoretically support an agent-driven payroll preview workflow. However, there is no evidence of a specific payroll preview API endpoint, anomaly-surfacing mechanism accessible programmatically, or any agent/AI integration example for this exact workflow. Missing for 10: a documented payroll preview API endpoint, anomaly-detection API output format, and any evidence of an agent actually using the API to run a preview and flag anomalies before approval.", "evidenceIds": [ "rippling-docs-1", "rippling-docs-8", "rippling-docs-43" ] }, { "productId": "rippling", "storyId": "agent-reconciles-payroll-journal", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Rippling documents integrations with accounting systems (Xero, QuickBooks, NetSuite) and offers developer APIs/sandbox and a CLI for building custom integrations, which could support pulling payroll data programmatically, but there is no explicit mention of a payroll journal export/API or agent-driven reconciliation workflow into a ledger. missing for 10: explicit payroll journal API/export documentation, agent-specific reconciliation tooling, and any hands-on evidence of this exact workflow.", "evidenceIds": [ "rippling-docs-14", "rippling-docs-43", "rippling-docs-8", "rippling-gh-1" ] }, { "productId": "rippling", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an llms.txt file, agent-oriented documentation format, or any mention of enabling AI agents to consume Rippling docs directly; evidence only covers developer docs/sandbox and a CLI, not agent-readable doc formats. Missing for 10: llms.txt file, agent-oriented doc structure, any mention of AI agent doc consumption.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Rippling documents AI-driven insights inside the product—e.g. 'Use AI to build reports and dashboards on labor cost trends, overtime by location' and a headcount dashboard with a natural-language prompt 'Show me headcount vs plan,' plus AI-powered instant answers for benefits questions. These are first-party marketing claims without independent hands-on verification or detail on breadth/accuracy across the whole platform. Missing for 10: independent/hands-on corroboration of the AI insights actually working, broader coverage of AI-generated suggestions beyond time-attendance/benefits (e.g. payroll, HR core), and technical depth on how insights are generated.", "evidenceIds": [ "rippling-docs-5", "rippling-docs-42", "rippling-docs-20", "rippling-docs-21" ] }, { "productId": "rippling", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Rippling documents workflow automation that runs in the background without manual triggering—e.g., automating administrative tasks like bonus reminders, triggering a Slack alert from a Zendesk ticket, and auto-provisioning/deprovisioning accounts based on lifecycle events—which shows autonomous, condition-based background automations. However, these are rule-based workflow triggers rather than AI-driven agentic automations that reason or act independently. Missing for 10: evidence of AI/agent-driven autonomous decision-making automations (not just rule-based triggers), scheduling/monitoring dashboards for these automations, and independent confirmation of reliability at scale.", "evidenceIds": [ "rippling-docs-3", "rippling-docs-32", "rippling-docs-30", "rippling-docs-31", "rippling-docs-6" ] }, { "productId": "rippling", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Rippling markets several embedded 'Rippling AI' capabilities where users can offload tasks—AI-generated reports/dashboards, AI-driven natural-language queries ('Show me headcount vs plan'), AI review of proof-of-relationship documents for benefits approval, and AI-powered employee self-service Q&A—all suggesting a built-in assistant that performs delegated tasks. However these are scattered point features rather than a single unified conversational assistant, and all evidence is first-party marketing copy with no independent hands-on verification of how broadly tasks can be delegated. Missing for 10: a unified, named AI assistant interface spanning the whole product, explicit task-delegation workflow documentation, and independent/community corroboration of real-world use.", "evidenceIds": [ "rippling-docs-5", "rippling-docs-20", "rippling-docs-21", "rippling-docs-42" ] }, { "productId": "rippling", "storyId": "agentic-headless", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Rippling has an official CLI (rippling-cli) with 'Flux' commands letting developers create, manage, and deploy Rippling-hosted integrations, which could be invoked in scripts/CI, but there is no documentation of headless automation of core HR/payroll workflows or CI-specific guidance for the main product itself. missing for 10: evidence of CI-specific usage guides, headless/automation examples beyond integration deployment, and confirmation the CLI covers core product actions (not just integration publishing).", "evidenceIds": [ "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence pack shows Rippling's integration platform, extensions, developer APIs, sandbox, and CLI (rippling-docs-7,8,9,43; rippling-gh-1) but no mention of MCP (Model Context Protocol) support or the ability to plug in MCP servers for tool use. The axis is plausible for a platform with an integrations ecosystem and AI features, but no evidence confirms this capability exists.", "evidenceIds": [ "rippling-docs-7", "rippling-docs-8", "rippling-docs-9", "rippling-docs-43", "rippling-gh-1" ] }, { "productId": "rippling", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Rippling is a SaaS HR/IT platform (not an agent), so the MCP-server axis is applicable, but the evidence pack shows only a developer CLI, APIs, and app-shop integrations—no mention of an official MCP server for connecting AI agents.", "evidenceIds": [ "rippling-docs-43", "rippling-docs-8", "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Some hints of natural-language interaction exist—an AI-generated dashboard prompt ('Show me headcount vs plan'), AI-built reports/dashboards, and AI-based instant answers for benefits questions—but there is no evidence of broad natural-language command control over core operations like running payroll, managing permissions, or workflows. missing for 10: evidence of NL commands driving actual actions (not just queries/reports), broader scope across HR/IT/finance modules, and independent confirmation of this AI interface working as described.", "evidenceIds": [ "rippling-docs-42", "rippling-docs-5", "rippling-docs-21" ] }, { "productId": "rippling", "storyId": "agentic-official-cli", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Rippling does have an official CLI (rippling-cli) referenced on GitHub, enabling developers to create/manage/deploy Rippling-hosted integrations via 'Flux' commands, confirming an official CLI exists. However, evidence does not show this CLI is framed for AI-native/agentic workflows (e.g., no mention of LLM/agent integration, scripting for AI agents, or automation-first design) and lacks independent documentation depth or usage examples. Missing for 10: AI-native framing/use cases, detailed CLI documentation, independent corroboration of adoption.", "evidenceIds": [ "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "agentic-public-api", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Rippling has a developer program with documented APIs, developer docs/sandbox, and a CLI (Flux commands) for building and deploying integrations, which supports programmatic/agentic access. However, there's no evidence of an OpenAPI/REST reference specifically framed for AI-native or agentic consumption, no mention of API rate limits, auth flows, or SDKs beyond the CLI, and no independent corroboration of API usability. missing for 10: detailed public API reference docs, evidence of AI-agent-specific tooling or SDKs, independent developer confirmation of API usability.", "evidenceIds": [ "rippling-docs-8", "rippling-docs-43", "rippling-docs-9", "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Rippling exposes developer APIs, a sandbox, and role-based permissions for employees and apps (rippling-docs-8, rippling-docs-35, rippling-docs-43), but there is no evidence of scoped or least-privilege API credential issuance specifically for AI agents or any agent-oriented credentialing mechanism.", "evidenceIds": [ "rippling-docs-8", "rippling-docs-35", "rippling-docs-43" ] }, { "productId": "rippling", "storyId": "agentic-sdks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Rippling documents developer resources including APIs, a sandbox environment, extensions/development kits, and an official open-source CLI (Flux commands) for building integrations, which is evidence-adjacent to an SDK offering. However, no explicit named SDK (e.g., language-specific client libraries) is cited, and there's no independent developer corroboration of SDK quality or adoption. Missing for 10: named/versioned SDK packages, language coverage, and independent hands-on developer reviews of SDK usage.", "evidenceIds": [ "rippling-docs-7", "rippling-docs-8", "rippling-docs-43", "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "While Rippling has a developer platform, APIs, sandbox, and workflow automation triggers (e.g. Slack alerts based on Zendesk tickets), none of the evidence explicitly mentions webhook subscriptions or an event-based webhook API for external event listening. Missing for 10: explicit webhook documentation, event subscription API, or any mention of 'webhook' functionality.", "evidenceIds": [ "rippling-docs-32", "rippling-docs-43", "rippling-docs-8" ] }, { "productId": "rippling", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Rippling has developer docs, a sandbox, and an APIs/CLI (rippling-docs-8, rippling-docs-43, rippling-gh-1), but nothing in the evidence describes an interactive API reference with runnable/live examples (e.g., a Swagger/OpenAPI explorer or code playground). Missing for 10: any mention of an interactive/try-it-now API console or runnable code examples in the developer docs.", "evidenceIds": [ "rippling-docs-8", "rippling-docs-43", "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Rippling has a developer portal with API access, sandbox, and a CLI, but no mention of a downloadable OpenAPI spec or other machine-readable API specification is present anywhere in the evidence pack.", "evidenceIds": [ "rippling-docs-8", "rippling-docs-43", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "api-sandbox", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Rippling documents developer access to a sandbox environment for building/testing integrations, but the evidence gives no detail on how it isolates data from production, its fidelity, or whether it's usable for general AI-native testing workflows beyond app development. missing for 10: documentation on sandbox data isolation/fidelity, first-party guidance on production-parity testing, independent/hands-on confirmation the sandbox behaves realistically, and any mention of AI-specific sandbox testing workflows.", "evidenceIds": [ "rippling-docs-8" ] }, { "productId": "rippling", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence mentions developer docs, a sandbox environment, and a CLI for building integrations, but nothing about API versioning or a documented deprecation policy is present anywhere in the pack.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "automatic-tax-filing", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Rippling's docs explicitly claim automatic calculation and filing of payroll taxes with correct federal, state, and local agencies at the right time, plus automatic tax calculation/filing worldwide, directly matching the story. Evidence is vendor-sourced only, with no independent/hands-on corroboration of tax filing accuracy or remittance specifics; missing for 10: independent verification of accurate multi-jurisdiction filing/remittance, details on handling agency notices or penalty guarantees.", "evidenceIds": [ "rippling-docs-44", "rippling-docs-40" ] }, { "productId": "rippling", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Rippling documents specific bulk actions (bulk EOI/dependent approval and coverage updates in docs-23/docs-41) and offers a developer CLI/platform APIs (rippling-gh-1, docs-43) that could support programmatic bulk operations, but there's no evidence of a general-purpose bulk operation capability (e.g., bulk edit payroll, HR records, or time entries) exposed for AI-native automation across arbitrary object types. Missing for 10: a documented bulk API/endpoint for arbitrary entities, evidence of AI agents invoking bulk actions, and independent confirmation of bulk operation reliability at scale.", "evidenceIds": [ "rippling-docs-23", "rippling-docs-41", "rippling-gh-1", "rippling-docs-43" ] }, { "productId": "rippling", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Rippling offers custom workflow automation triggered by events (e.g., notify on changes, trigger reminders, automate Slack alerts from Zendesk tickets, auto-provision/deprovision accounts, dynamic rule-based permissions), which supports rule-based event-triggered actions but is framed as admin/no-code workflow building rather than an AI-native, developer-defined rule engine. Missing for 10: documentation of an explicit rules/automation API or AI-native trigger-action framework, examples of natural-language or agent-defined rule creation, and independent/hands-on verification of workflow automation reliability.", "evidenceIds": [ "rippling-docs-3", "rippling-docs-32", "rippling-docs-30", "rippling-docs-35", "rippling-docs-6" ] }, { "productId": "rippling", "storyId": "automation-scheduled-jobs", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Rippling offers workflow automation (custom workflows, triggers, Slack alerts) and flexible payroll run scheduling, which shows some recurring-job/workflow capability, but none of this is framed for AI-native/agentic scheduling or exposed via an API/CLI for programmatic recurring job scheduling. Missing for 10: explicit AI-agent-triggered or API/CLI-based recurring job scheduling, documentation of cron-like triggers, and independent verification of workflow automation depth.", "evidenceIds": [ "rippling-docs-3", "rippling-docs-32", "rippling-docs-38", "rippling-docs-30" ] }, { "productId": "rippling", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence describes version control, review workflows, or rollback capabilities for Rippling's automations/workflows; the CLI and platform docs cover deployment and permissions but nothing about versioning history, diffing changes, or reverting automations. This axis applies to Rippling's workflow-builder capability but there is no supporting evidence.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "cancel-or-correct-payroll", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence only covers catching discrepancies before final approval (pre-submission) and general run-payroll flexibility, but nothing documents an ability to cancel or correct a payroll run that has already been submitted, before employees are actually paid. Missing for 10: any documentation of a 'void/cancel run' or 'off-cycle correction' feature, or evidence of a workflow to halt payment after submission.", "evidenceIds": [ "rippling-docs-1", "rippling-docs-38" ] }, { "productId": "rippling", "storyId": "compliance-alerts", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Rippling documents automatic application of location-based labor policies and flags of potential risks tied to an employee's work location (docs-26/45), plus configurable workflow notifications for 'important changes' (docs-3) and automatic tax filing (docs-40/44), which together gesture at proactive compliance alerting. However, there is no explicit evidence of alerts specifically triggered by a new hire or by legal/regulatory changes (e.g., new state tax registration requirements), only location-based labor-policy risk flags within time-and-attendance. Missing for 10: dedicated compliance-alert feature tied to new-hire events, explicit law-change monitoring/alerting, and independent confirmation of these alerts working in practice.", "evidenceIds": [ "rippling-docs-26", "rippling-docs-45", "rippling-docs-3", "rippling-docs-44" ] }, { "productId": "rippling", "storyId": "embedded-payroll-for-platforms", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Rippling's developer evidence covers building integrations/apps on top of its platform (docs, sandbox, App Shop, CLI, extensions) but nothing indicates a partner API for white-labeling Rippling's payroll engine inside a third party's own product. Missing for 10: any mention of embedded/white-label payroll API, partner/reseller program, or evidence of other companies embedding Rippling payroll under their own brand.", "evidenceIds": [ "rippling-docs-8", "rippling-docs-9", "rippling-docs-43", "rippling-gh-1" ] }, { "productId": "rippling", "storyId": "fast-direct-deposit", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack describes payroll scheduling flexibility, tax filing, and HR-to-payroll data flow, but nowhere claims or documents a specific fast (next-day or 2-day) direct deposit turnaround for employees. Community evidence even references payroll delays (SVB transition, CSV error) rather than confirming fast deposit speed, so there's no basis to credit this specific capability.", "evidenceIds": [ "rippling-docs-38", "rippling-docs-44", "rippling-comm-1", "rippling-comm-2" ] }, { "productId": "rippling", "storyId": "flexible-pay-schedules", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Rippling's payroll docs only mention flexible run frequency ('process payroll as often as you need') without detailing distinct weekly/biweekly/semimonthly/monthly schedules or per-team configuration. missing for 10: explicit documentation of multiple concurrent pay schedule types, evidence of assigning different schedules to different teams/departments, and any hands-on confirmation of this setup.", "evidenceIds": [ "rippling-docs-38" ] }, { "productId": "rippling", "storyId": "global-payroll-eor", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Rippling's docs repeatedly describe paying employees and contractors 'around the world' in a single system with automatic worldwide payroll tax filing and location-based labor-policy compliance, which implies international employment capability, but none of the evidence explicitly names an Employer-of-Record service or owned/local entity setup for hiring abroad. missing for 10: explicit EOR product documentation, description of owned-entity incorporation process, independent case studies confirming EOR hires, and clarity on which countries are covered via EOR vs contractor-only payroll.", "evidenceIds": [ "rippling-docs-16", "rippling-docs-17", "rippling-docs-39", "rippling-docs-40", "rippling-docs-19", "rippling-docs-46", "rippling-docs-26" ] }, { "productId": "rippling", "storyId": "health-benefits-administration", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Docs directly evidence benefits admin with payroll deduction sync: HSA/FSA/commuter deductions always sync with payroll, benefits deductions flow into payroll, one-click enrollment reopen, bulk EOI/dependent approval and coverage updates with automatic payroll deduction adjustment. This covers offering, administering, and syncing enrollments/deductions to payroll as the story requires. Missing for 10: independent/hands-on verification of benefits-payroll sync accuracy (only vendor docs, no third-party corroboration).", "evidenceIds": [ "rippling-docs-24", "rippling-docs-13", "rippling-docs-22", "rippling-docs-23", "rippling-docs-41", "rippling-docs-20" ] }, { "productId": "rippling", "storyId": "international-contractor-payments", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Rippling's docs confirm paying contractors globally without waiting on bank transfers/conversion and unifying global payroll in one system, implying local currency payouts, but there is no explicit mention of compliant contractor agreements/contract generation or EOR/compliance guarantees specific to contractors. missing for 10: explicit evidence of compliant contractor agreement templates or localized contract compliance, independent/hands-on verification of local-currency payouts, and any detail on contractor misclassification protections.", "evidenceIds": [ "rippling-docs-16", "rippling-docs-17", "rippling-docs-39", "rippling-docs-46" ] }, { "productId": "rippling", "storyId": "multi-state-payroll", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Rippling documents automatic multi-state payroll tax calculation and filing with federal, state, and local agencies, plus location-based labor policy application (overtime, breaks) which supports multi-state compliance. However, there is no explicit mention of state tax registration handling, new-state onboarding workflows, or independent/hands-on verification of accuracy across states. Missing for 10: evidence of state registration setup/automation, third-party/hands-on validation of multi-state accuracy, and detail on withholding setup per state.", "evidenceIds": [ "rippling-docs-44", "rippling-docs-26", "rippling-docs-45", "rippling-docs-40" ] }, { "productId": "rippling", "storyId": "off-cycle-payroll-run", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Rippling's docs explicitly support adding one-off bonuses to payroll and running payroll 'as often as you need' rather than on a fixed schedule, which covers the core off-cycle bonus/correction use case, but there's no explicit mention of termination-triggered off-cycle runs or independent/hands-on confirmation of the workflow. Missing for 10: explicit termination off-cycle run support, independent user corroboration of off-cycle payroll UX.", "evidenceIds": [ "rippling-docs-36", "rippling-docs-38", "rippling-docs-13" ] }, { "productId": "rippling", "storyId": "offer-letters-and-documents", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of offer letters, e-signature workflows, or per-employee document storage; onboarding content only vaguely references 'onboarding new hires' without detailing document/e-sign features. missing for 10: any mention of e-signature capability, offer letter templates/workflow, or document storage per employee.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "openness-api-parity", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Rippling documents developer APIs, a CLI, sandbox, extensions/dev kits, and app publishing (rippling-docs-7,8,9,43; rippling-gh-1), showing genuine API/platform surface for building integrations, but there is no evidence establishing full parity between UI functionality and API/CLI coverage. Missing for 10: explicit API reference/endpoint coverage list, confirmation that all UI actions (e.g., payroll runs, benefits admin, approvals) are exposed via API, and independent/hands-on verification of API completeness.", "evidenceIds": [ "rippling-docs-7", "rippling-docs-8", "rippling-docs-9", "rippling-docs-43", "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of any data export/portability feature in open formats, nor mention of account closure/data takeout; evidence covers payroll, benefits, integrations, and CLI for app development, none addressing exportability or vendor lock-in exit. Missing for 10: bulk/open-format data export tools, documented offboarding data portability, or any explicit anti-lock-in export commitment.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows Rippling is a closed commercial SaaS platform with a CLI repo on GitHub, but nothing indicates the core product source is available under an open license; the CLI repo's license status is not documented as open.", "evidenceIds": [ "rippling-gh-1", "rippling-probe-1" ] }, { "productId": "rippling", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Rippling is a cloud-based HR/payroll/IT SaaS platform with no evidence of, or plausible expectation for, a self-hostable core product; self-hosting is not a fair axis for this category of managed compliance-heavy SaaS.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "pay-employees-and-contractors", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Rippling's docs explicitly state it pays both employees and contractors globally from a single system ('Pay employees and contractors around the world in a single system'), with unified payroll processing, tax filing, and HR data flowing into payroll for both worker types. missing for 10: independent/hands-on verification of contractor payment workflow specifically, and no evidence distinguishing 1099-specific compliance handling (e.g., 1099 filing) beyond general contractor payment claims.", "evidenceIds": [ "rippling-docs-16", "rippling-docs-39", "rippling-docs-17", "rippling-docs-40", "rippling-docs-44", "rippling-docs-13" ] }, { "productId": "rippling", "storyId": "payroll-event-webhooks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Rippling has developer APIs, a CLI, sandbox, and workflow automation triggers (e.g. Slack/Zendesk workflows) but nowhere describes webhook subscriptions for payroll lifecycle events like payroll processed, employee onboarded, or payment failed. Without concrete evidence of this webhook capability, the story is unsupported despite the axis being plausible for a platform with APIs.", "evidenceIds": [ "rippling-docs-8", "rippling-docs-32", "rippling-docs-43", "rippling-gh-1" ] }, { "productId": "rippling", "storyId": "payroll-reports-exports", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack describes general payroll processing, tax filing, and some reporting/dashboard capabilities (e.g. docs-34, docs-5), but never mentions payroll registers, gross-to-net reports, or exporting such reports for analysis. Missing for 10: any documentation of payroll register generation, gross-to-net report format, or export functionality (CSV/PDF) for these specific reports.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses data residency, regional storage choice, or data localization controls for Rippling; all citations concern payroll, benefits, HR workflows, integrations, or unrelated security incidents. missing for 10: any mention of data residency/region selection, storage location controls, or compliance certifications tied to geographic data storage.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses AI training data opt-out or data usage controls for AI models; Rippling's docs focus on HR/payroll AI features (e.g., report building, benefits assistance) but never mention training-data policies or opt-out controls.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses data retention policies, deletion controls, or AI-specific data handling for user-controlled deletion; all citations concern payroll, benefits, HR, and integrations features unrelated to data retention/deletion controls.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence anywhere in the pack about telemetry collection, usage tracking, or an opt-out mechanism for Rippling's platform, CLI, or developer tools; the pack only covers payroll/HR/benefits features and unrelated security incidents.", "evidenceIds": [] }, { "productId": "rippling", "storyId": "pto-policies-and-accruals", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Evidence confirms employees can request time off and that time-off data syncs automatically into payroll (rippling-docs-28, rippling-docs-18, rippling-docs-25), implying some PTO-to-payroll integration, but there is no documentation of configurable accrual rules or an approval workflow specific to PTO policies. Missing for 10: explicit accrual policy configuration, approval workflow steps for PTO requests, and any independent confirmation of automatic policy enforcement.", "evidenceIds": [ "rippling-docs-28", "rippling-docs-18", "rippling-docs-25" ] }, { "productId": "rippling", "storyId": "retirement-plan-sync", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Rippling advertises that benefits deductions (docs-13) and specific benefit types like HSA/FSA/commuter (docs-24) sync automatically with payroll, showing the general payroll-benefits sync capability exists, but no evidence specifically names 401(k) or retirement plan administration or its contribution sync. missing for 10: explicit 401(k)/retirement plan offering, contribution sync details, employer-match handling, and any hands-on confirmation of retirement plan integration.", "evidenceIds": [ "rippling-docs-13", "rippling-docs-24" ] }, { "productId": "rippling", "storyId": "run-payroll-end-to-end", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Docs describe the core elements of the story: reviewing timesheets inside a pay run, comparing totals against previous runs, adding one-off items, and submitting on a schedule, which together map to review→preview→submit. However, evidence is entirely first-party marketing copy with no independent walkthrough confirming a single unified flow, and community reports flag real-world payroll execution failures (delayed payouts, CSV errors) that raise reliability concerns around the run process. Missing for 10: independent/hands-on confirmation of the actual UI flow, and resolution of community-reported run-time reliability issues.", "evidenceIds": [ "rippling-docs-1", "rippling-docs-25", "rippling-docs-36", "rippling-docs-38", "rippling-docs-44", "rippling-comm-1", "rippling-comm-2" ] }, { "productId": "rippling", "storyId": "self-serve-employee-onboarding", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence only generically mentions 'onboarding new hires' and HR data flowing into payroll/benefits, without any documentation of a self-serve flow specifically collecting W-4, I-9, or bank details before day one. missing for 10: explicit documentation of W-4/I-9 e-signature collection, bank/direct-deposit setup during onboarding, and a self-serve pre-day-one flow with hands-on or independent corroboration.", "evidenceIds": [ "rippling-docs-33", "rippling-docs-11", "rippling-docs-13" ] }, { "productId": "rippling", "storyId": "time-tracking-into-payroll", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Rippling's docs explicitly state approved hours from Time & Attendance flow instantly into Payroll with no manual entry, and that it automatically applies correct overtime/labor policies by location, flagging risks before payroll runs — directly matching the story of hourly entries and overtime flowing into payroll. Missing for 10: independent/hands-on verification of overtime calculation accuracy and no first-hand customer account of the payroll-time sync working end-to-end.", "evidenceIds": [ "rippling-docs-25", "rippling-docs-26", "rippling-docs-45", "rippling-docs-27", "rippling-docs-18" ] }, { "productId": "rippling", "storyId": "year-end-forms", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Rippling's payroll docs show it automatically calculates and files payroll taxes with agencies and lets employees view 'tax forms' (implying W-2/1099s) alongside pay stubs, suggesting year-end forms are generated and made accessible, but there's no explicit documentation describing automatic W-2/1099 generation, e-filing to SSA/IRS, or proactive distribution timing at year-end. Missing for 10: explicit description of automatic W-2/1099 generation process, confirmation of e-filing with tax authorities, and evidence of proactive distribution (email/notification) to workers at year-end rather than just on-demand viewing.", "evidenceIds": [ "rippling-docs-15", "rippling-docs-44" ] } ]