Gusto vs Rippling

Agent access

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

   weight 2 · round to Gusto
   Gusto✓fullprobed9/10

   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.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.gusto.com/llms.txt # Embedded Payroll Documentation > Documentation for Embedded Payroll ## Guide…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.gusto.com/embedded-payroll/docs/introduction.md --- updatedAt: 2026-02-03T16:33:42.000Z --- Fetch t…”
   • [probe] “official MCP server documented at https://docs.gusto.com/embedded-payroll/docs/dev-assistant-mcp.md”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

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

   weight 2 · round to Gusto
   Gusto~partialclaimed5/10

   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.

   • [claimed-docs] “idempotency ensures that performing the same logical operation multiple times produces the same final result. It protects your integration f…”
   • [claimed-docs] “Idempotency key... Ensures multiple identical requests have the same effect, preventing duplicate creations when retrying the same request.”
   • [claimed-docs] “Idempotency key ... Ensures multiple identical requests have the same effect, preventing duplicate creations when retrying the same request.”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event. Gusto will publish this webhook event when payroll credits…”
   • [claimed-docs] “Demo companies are automatically generated with company info, employees, and previous payrolls so you can begin testing right away.”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”

   proof ↗⚑ flag

   Rippling~partialprobed3/10

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

   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

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

   weight 3 · round to Gusto
   Gusto✓fullprobed8/10

   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.

   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [probe] “official MCP server documented at https://docs.gusto.com/embedded-payroll/docs/dev-assistant-mcp.md”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Rippling
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling~partialprobed5/10

   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.

   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

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

   weight 3 · round to Gusto
   Gusto✓fullprobed9/10

   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.

   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “Gusto Embedded offers official client libraries for several programming languages to help you integrate with our API quickly and reliably.”
   • [claimed-docs] “The Gusto Embedded Payroll React SDK offers component libraries with built-in business logic that helps our developers with the complexity o…”
   • [claimed-docs] “Set your API version using the `X-Gusto-API-Version` header”
   • [claimed-docs] “System access tokens allow you to carry out application-level actions such as: Creating a partner-managed company”
   • [claimed-docs] “idempotency ensures that performing the same logical operation multiple times produces the same final result. It protects your integration f…”
   • [claimed-docs] “all updateable objects returned by the Gusto API include a version field ... If another process has already updated the record and changed t…”
   • [claimed-docs] “To use this feature, add a page and optionally a per parameter to the URL query string. For example https://api.gusto.com/v1/companies/abc12…”
   • [probe] “official MCP server documented at https://docs.gusto.com/embedded-payroll/docs/dev-assistant-mcp.md”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.gusto.com/embedded-payroll/docs/introduction.md --- updatedAt: 2026-02-03T16:33:42.000Z --- Fetch t…”

   proof ↗⚑ flag

   Rippling~partialprobed5/10

   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.

   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [claimed-docs] “Publish to the Rippling App Shop and unlock support through our Choice program.”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Gusto—none0/10

   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.

   • [claimed-docs] “System access tokens allow you to carry out application-level actions such as: Creating a partner-managed company”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Permissions and approvals are dynamic and role-based, automatically governing what each employee can do across every app. Define rules once …”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Gusto
   Gusto✓fullclaimed8/10

   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.

   • [claimed-docs] “The Gusto Embedded Payroll React SDK offers component libraries with built-in business logic that helps our developers with the complexity o…”
   • [claimed-docs] “Gusto Embedded offers official client libraries for several programming languages to help you integrate with our API quickly and reliably.”
   • [claimed-docs] “A React component library for building payroll—deeply customizable and quick-to-deploy”

   proof ↗⚑ flag

   Rippling~partialprobed5/10

   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.

   • [claimed-docs] “Leverage Rippling extensions and development kits”
   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Gusto
   Gusto✓fullclaimed8/10

   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.

   • [claimed-docs] “A webhook is an HTTP request that delivers information about an event as it happens. We recommend that you integrate with Gusto's webhooks i…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event. Gusto will publish this webhook event when payroll credits…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event.”
   • [claimed-docs] “Gusto computes a hash message authentication code (HMAC) of the event payload using the verification_token”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our `payroll.paid` event. Gusto will publish this webhook event when payroll credi…”
   • [claimed-docs] “Create a webhook subscription to receive events of the specified subscription_types whenever there is a state change.”
   • [claimed-docs] “Returns the health status (`healthy`, `unhealthy`, or `unknown`) of the webhooks system based on the last ten minutes of activity.”
   • [claimed-docs] “This `verify` endpoint needs to be called with `verification_token` before webhook events can be sent to the registered webhook URL.”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Use Rippling’s platform capabilities to run reports across your third-party app data or trigger workflows–like automating a Slack alert base…”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [claimed-docs] “Access to developer documentation and sandbox environment”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Rippling
   Gusto—none0/10

   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.

   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”

   proof ↗⚑ flag

   Rippling~partialclaimed6/10

   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.

   • [claimed-docs] “Use AI to build reports and dashboards on labor cost trends, overtime by location, and more.”
   • [claimed-docs] “A tablet displaying an Annual Headcount Plan dashboard with purple line charts and a prompt reading "Show me headcount vs plan."”
   • [claimed-docs] “Have Rippling AI automatically review proof of relationship documents and approve coverage if they’re valid.”
   • [claimed-docs] “Employees can get instant answers to questions, compare plans, and submit qualifying life events with AI, on desktop and mobile.”

   proof ↗⚑ flag

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

   weight 2 · round to Rippling
   Gusto—none0/10

   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.

   • [claimed-docs] “A webhook is an HTTP request that delivers information about an event as it happens. We recommend that you integrate with Gusto's webhooks i…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event. Gusto will publish this webhook event when payroll credits…”
   • [claimed-docs] “We automatically pre-generate scheduled regular payrolls based on the company’s pay schedule and corresponding pay periods.”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”

   proof ↗⚑ flag

   Rippling~partialclaimed5/10

   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.

   • [claimed-docs] “Easily build custom workflows to notify people of important changes and automate administrative tasks—like triggering a reminder to pay a bo…”
   • [claimed-docs] “Use Rippling’s platform capabilities to run reports across your third-party app data or trigger workflows–like automating a Slack alert base…”
   • [claimed-docs] “Automatically provision and deprovision accounts from onboarding to offboarding.”
   • [claimed-docs] “Attribute mapping allows updates made to user fields in Rippling—like photo, department, or preferred name—to automatically apply to your th…”
   • [claimed-docs] “Supergroup rules for app access let you group, manage, and automate user permissions to your integrated apps as roles change across the empl…”

   proof ↗⚑ flag

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

   weight 3 · round to Rippling
   Gusto—none0/10

   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.

   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [probe] “official MCP server documented at https://docs.gusto.com/embedded-payroll/docs/dev-assistant-mcp.md”

   proof ↗⚑ flag

   Rippling~partialclaimed6/10

   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.

   • [claimed-docs] “Use AI to build reports and dashboards on labor cost trends, overtime by location, and more.”
   • [claimed-docs] “Have Rippling AI automatically review proof of relationship documents and approve coverage if they’re valid.”
   • [claimed-docs] “Employees can get instant answers to questions, compare plans, and submit qualifying life events with AI, on desktop and mobile.”
   • [claimed-docs] “A tablet displaying an Annual Headcount Plan dashboard with purple line charts and a prompt reading "Show me headcount vs plan."”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Gusto~partialprobed4/10

   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.

   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [probe] “official MCP server documented at https://docs.gusto.com/embedded-payroll/docs/dev-assistant-mcp.md”

   proof ↗⚑ flag

   Rippling~partialclaimed4/10

   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.

   • [claimed-docs] “A tablet displaying an Annual Headcount Plan dashboard with purple line charts and a prompt reading "Show me headcount vs plan."”
   • [claimed-docs] “Use AI to build reports and dashboards on labor cost trends, overtime by location, and more.”
   • [claimed-docs] “Employees can get instant answers to questions, compare plans, and submit qualifying life events with AI, on desktop and mobile.”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

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

   weight 2 · round to Gusto
   Gusto~partialclaimed4/10

   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.

   • [claimed-docs] “We publish separate collections for each API version.”
   • [claimed-docs] “Set your API version using the `X-Gusto-API-Version` header”
   • [claimed-docs] “Starting from version `2023-02-01`, error messages will have consistent JSON structures.”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

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

   weight 1 · round to Gusto
   Gusto~partialclaimed5/10

   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.

   • [claimed-docs] “Demo companies are automatically generated with company info, employees, and previous payrolls so you can begin testing right away.”

   proof ↗⚑ flag

   Rippling~partialclaimed3/10

   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.

   • [claimed-docs] “Access to developer documentation and sandbox environment”

   proof ↗⚑ flag

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

   weight 2 · round to Gusto
   Gusto~partialclaimed5/10

   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.

   • [claimed-docs] “Set your API version using the `X-Gusto-API-Version` header”
   • [claimed-docs] “We publish separate collections for each API version.”
   • [claimed-docs] “Starting from version `2023-02-01`, error messages will have consistent JSON structures.”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

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

   weight 2 · round to Rippling
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling~partialclaimed5/10

   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.

   • [claimed-docs] “Upload a carrier EOI file and Rippling matches each decision to the right employee, updates their coverage, and adjusts payroll deductions i…”
   • [claimed-docs] “Automatically approve dependents, update coverage, and route EOI in bulk”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”

   proof ↗⚑ flag

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

   weight 3 · round to Rippling
   Gusto~partialclaimed4/10

   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.

   • [claimed-docs] “A webhook is an HTTP request that delivers information about an event as it happens. We recommend that you integrate with Gusto's webhooks i…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event. Gusto will publish this webhook event when payroll credits…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event.”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our `payroll.paid` event. Gusto will publish this webhook event when payroll credi…”
   • [claimed-docs] “Create a webhook subscription to receive events of the specified subscription_types whenever there is a state change.”
   • [claimed-docs] “This `verify` endpoint needs to be called with `verification_token` before webhook events can be sent to the registered webhook URL.”
   • [claimed-docs] “Gusto computes a hash message authentication code (HMAC) of the event payload using the verification_token”

   proof ↗⚑ flag

   Rippling~partialclaimed5/10

   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.

   • [claimed-docs] “Easily build custom workflows to notify people of important changes and automate administrative tasks—like triggering a reminder to pay a bo…”
   • [claimed-docs] “Use Rippling’s platform capabilities to run reports across your third-party app data or trigger workflows–like automating a Slack alert base…”
   • [claimed-docs] “Automatically provision and deprovision accounts from onboarding to offboarding.”
   • [claimed-docs] “Permissions and approvals are dynamic and role-based, automatically governing what each employee can do across every app. Define rules once …”
   • [claimed-docs] “Supergroup rules for app access let you group, manage, and automate user permissions to your integrated apps as roles change across the empl…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Rippling
   Gusto—none0/10

   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.

   • [claimed-docs] “We automatically pre-generate scheduled regular payrolls based on the company’s pay schedule and corresponding pay periods.”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls with processing_statuses=unprocessed.”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”

   proof ↗⚑ flag

   Rippling~partialclaimed4/10

   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.

   • [claimed-docs] “Easily build custom workflows to notify people of important changes and automate administrative tasks—like triggering a reminder to pay a bo…”
   • [claimed-docs] “Use Rippling’s platform capabilities to run reports across your third-party app data or trigger workflows–like automating a Slack alert base…”
   • [claimed-docs] “Run payroll on your schedule Stay flexible and process payroll as often as you need — at no extra charge.”
   • [claimed-docs] “Automatically provision and deprovision accounts from onboarding to offboarding.”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

Benefits

1. ops userOffer and administer health insurance with enrollments and deductions synced to payroll

   weight 2 · round to Rippling
   Gusto!disputedcontradicted4/10

   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.

   • [claimed-docs] “Health insurance via SimplyInsured * On-demand pay via Clair * Workers compensation via NEXT Insurance * 401(k) (Guideline)”
   • [community] “I'm at the point where if a company is using Gusto I won't accept their offer since I spent 6 months+ dealing with healthcare billing issues…”
   • [community] “Once we started venturing into offering health insurance to employees though and our employees spread across multiple states/countries we we…”
   • [community] “One thing I don't like about Gusto is a platform lock-in for new features... Things we've been asking about like HSA contributions or prorat…”

   proof ↗⚑ flag

   Rippling✓fullclaimed8/10

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

   • [claimed-docs] “Offer integrated HSA, FSA, and commuter benefits. Deductions always sync with payroll.”
   • [claimed-docs] “With Rippling, HR data—like new hires, salary changes, and benefits deductions—flow directly and automatically into Payroll.”
   • [claimed-docs] “Reopen an employee’s benefits enrollment in one click.”
   • [claimed-docs] “Upload a carrier EOI file and Rippling matches each decision to the right employee, updates their coverage, and adjusts payroll deductions i…”
   • [claimed-docs] “Automatically approve dependents, update coverage, and route EOI in bulk”
   • [claimed-docs] “Have Rippling AI automatically review proof of relationship documents and approve coverage if they’re valid.”

   proof ↗⚑ flag

2. ops userOffer a 401(k) or retirement plan whose contributions sync automatically with each payroll

   weight 2 · round to Gusto
   Gusto~partialclaimed5/10

   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.

   • [claimed-docs] “Partners can generate a link for employer payroll admins to access Guideline by using Gusto Embedded's pre-built flows”
   • [claimed-docs] “Health insurance via SimplyInsured * On-demand pay via Clair * Workers compensation via NEXT Insurance * 401(k) (Guideline)”
   • [claimed-docs] “Partners can generate a link for employer payroll admins to access Guideline by using Gusto Embedded’s pre-built flows.”
   • [claimed-docs] “Partners can generate a link for employer payroll admins to access Guideline by using Gusto Embedded's pre-built flows.”
   • [claimed-docs] “For onboarded companies, Partners can generate a link for employer payroll admins to access Guideline by using Gusto Embedded’s pre-built fl…”

   proof ↗⚑ flag

   Rippling~partialclaimed3/10

   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.

   • [claimed-docs] “With Rippling, HR data—like new hires, salary changes, and benefits deductions—flow directly and automatically into Payroll.”
   • [claimed-docs] “Offer integrated HSA, FSA, and commuter benefits. Deductions always sync with payroll.”

   proof ↗⚑ flag

Contractor payments

1. ops userPay both W-2 employees and 1099 contractors from one platform

   weight 3 · round drawn
   Gusto✓fullclaimed8/10

   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.

   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “Handle all aspects of payroll management including regular payroll runs, off-cycle payments, termination processing, and all associated fede…”
   • [claimed-docs] “Contractors can have three types of payment methods: 1. Direct deposit... 2. Check... 3. Historical payment”
   • [claimed-docs] “You can use the POST /v1/companies/{company_id}/contractor_payment_groups/preview to validate inputs, determine how fast a payment can be ma…”
   • [claimed-docs] “Every direct deposit contractor payment that is funded ... requires that a contractor payment receipt be available.”
   • [claimed-docs] “To onboard a company, you'll need: Company details (such as name, EIN), Business locations, Bank account information”
   • [claimed-docs] “To onboard a company, you'll need: Company details (such as name, EIN) Business locations Bank account information”

   proof ↗⚑ flag

   Rippling✓fullclaimed8/10

   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.

   • [claimed-docs] “Pay employees and contractors around the world in a single system”
   • [claimed-docs] “Pay your employees and contractors around the world without waiting on transfers or conversion.”
   • [claimed-docs] “Seamlessly pay workers around the world without waiting for any bank transfers or conversion.”
   • [claimed-docs] “Rippling instantly calculates and files payroll taxes for your employees worldwide.”
   • [claimed-docs] “We automatically calculate payroll taxes and file them with the correct federal, state, and local agencies at precisely the right time.”
   • [claimed-docs] “With Rippling, HR data—like new hires, salary changes, and benefits deductions—flow directly and automatically into Payroll.”

   proof ↗⚑ flag

Global hiring

1. founderEmploy people in other countries through employer-of-record or owned-entity global payroll

   weight 2 · round to Rippling
   Gusto—none0/10

   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.

   • [community] “Gusto doesn't support outside of US folks... the 2 day payroll... capped it at something like $60k even when we have millions in the bank ac…”
   • [community] “Once we started venturing into offering health insurance to employees though and our employees spread across multiple states/countries we we…”
   • [claimed-docs] “An employee must provide federal tax information to file and pay taxes correctly.”
   • [claimed-docs] “Employees are required to configure two types of tax information as part of their onboarding: Federal tax... State tax:”

   proof ↗⚑ flag

   Rippling~partialclaimed5/10

   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.

   • [claimed-docs] “Pay employees and contractors around the world in a single system”
   • [claimed-docs] “Seamlessly pay workers around the world without waiting for any bank transfers or conversion.”
   • [claimed-docs] “Pay your employees and contractors around the world without waiting on transfers or conversion.”
   • [claimed-docs] “Rippling instantly calculates and files payroll taxes for your employees worldwide.”
   • [claimed-docs] “Monitor global compensation trends by department, location, and more, with built-in conversion to your local currency for easy comparison.”
   • [claimed-docs] “Rippling lets you manage global HR, payroll, benefits, spend, devices, apps, and more, all in one affordable platform.”
   • [claimed-docs] “Rippling automatically applies the correct labor policies—from overtime to breaks—based on location, and flags potential risks based on each…”

   proof ↗⚑ flag

2. founderPay international contractors in their local currencies with compliant contracts

   weight 3 · round to Rippling
   Gusto—none0/10

   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.

   • [claimed-docs] “Contractors can have three types of payment methods: 1. Direct deposit... 2. Check... 3. Historical payment”
   • [claimed-docs] “Contractors can have three types of payment methods: Direct deposit... Check... Historical payment”
   • [claimed-docs] “Contractors can have three types of payment methods: Direct deposit ... Check ... Historical payment”
   • [claimed-docs] “Contractors can have three types of payment methods: 1. Direct deposit: Gusto will deposit the funds to the bank account associated with the…”
   • [community] “Gusto doesn't support outside of US folks... the 2 day payroll... capped it at something like $60k even when we have millions in the bank ac…”

   proof ↗⚑ flag

   Rippling~partialclaimed6/10

   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.

   • [claimed-docs] “Pay employees and contractors around the world in a single system”
   • [claimed-docs] “Seamlessly pay workers around the world without waiting for any bank transfers or conversion.”
   • [claimed-docs] “Pay your employees and contractors around the world without waiting on transfers or conversion.”
   • [claimed-docs] “Rippling lets you manage global HR, payroll, benefits, spend, devices, apps, and more, all in one affordable platform.”

   proof ↗⚑ flag

Ai onboarding

1. ai-native userHave an agent onboard a new hire end-to-end via the API — creating the employee, compensation, and tax setup

   weight 3 · round to Gusto
   Gusto~partialprobed5/10

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

   • [claimed-docs] “To onboard a company, you'll need: Company details (such as name, EIN), Business locations, Bank account information”
   • [claimed-docs] “Employees are required to configure two types of tax information as part of their onboarding: Federal tax... State tax:”
   • [claimed-docs] “An employee must provide federal tax information to file and pay taxes correctly.”
   • [claimed-docs] “To use this feature, add a page and optionally a per parameter to the URL query string. For example https://api.gusto.com/v1/companies/abc12…”
   • [claimed-docs] “System access tokens allow you to carry out application-level actions such as: Creating a partner-managed company”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”
   • [probe] “official MCP server documented at https://docs.gusto.com/embedded-payroll/docs/dev-assistant-mcp.md”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Onboard new hires, run payroll, manage performance, and issue devices and corporate cards instantly and without switching systems.”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [claimed-docs] “Access to developer documentation and sandbox environment”

   proof ↗⚑ flag

Employee onboarding

1. ops userSend offer letters and HR documents for e-signature and keep them stored per employee

   weight 1 · round drawn
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

2. ops userSend a new hire a self-serve onboarding flow that collects W-4, I-9, and bank details before day one

   weight 3 · round to Gusto
   Gusto~partialclaimed4/10

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

   • [claimed-docs] “To onboard a company, you'll need: Company details (such as name, EIN), Business locations, Bank account information”
   • [claimed-docs] “Employees are required to configure two types of tax information as part of their onboarding: Federal tax... State tax:”
   • [claimed-docs] “An employee must provide federal tax information to file and pay taxes correctly.”
   • [claimed-docs] “To onboard a company, you'll need: Company details (such as name, EIN) Business locations Bank account information”

   proof ↗⚑ flag

   Rippling~partialclaimed3/10

   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.

   • [claimed-docs] “Onboard new hires, run payroll, manage performance, and issue devices and corporate cards instantly and without switching systems.”
   • [claimed-docs] “Having everything in one system for [all] three countries—including benefits, employee-self-service, and onboarding—just made sense.”
   • [claimed-docs] “With Rippling, HR data—like new hires, salary changes, and benefits deductions—flow directly and automatically into Payroll.”

   proof ↗⚑ flag

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

   weight 2 · round to Gusto
   Gusto~partialclaimed6/10

   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.

   • [claimed-docs] “Partners can launch quickly with pre-built UI Flows, build custom experiences using APIs, or combine multiple approaches to create the ideal…”
   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “Handle all aspects of payroll management including regular payroll runs, off-cycle payments, termination processing, and all associated fede…”
   • [claimed-docs] “Use the time_off_request_management flow to give admins an embedded approval interface, or call the approve/decline endpoints directly from …”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls”
   • [claimed-docs] “The Gusto Embedded Payroll React SDK offers component libraries with built-in business logic that helps our developers with the complexity o…”
   • [claimed-docs] “Gusto Embedded offers official client libraries for several programming languages to help you integrate with our API quickly and reliably.”

   proof ↗⚑ flag

   Rippling~partialprobed4/10

   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.

   • [claimed-docs] “Leverage Rippling extensions and development kits”
   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Publish to the Rippling App Shop and unlock support through our Choice program.”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”
   • [probe] “official CLI documented at https://github.com/Rippling/rippling-cli”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

Ai payroll ops

1. ai-native userHave an agent run a payroll preview via the API and surface anomalies for review before I approve the run

   weight 3 · round to Gusto
   Gusto~partialclaimed5/10

   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.

   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “enables AI-powered code editors like Cursor and Windsurf, as well as general-purpose tools like Claude Desktop, to interact directly with th…”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls with processing_statuses=unprocessed.”
   • [claimed-docs] “You can use the POST /v1/companies/{company_id}/contractor_payment_groups/preview to validate inputs, determine how fast a payment can be ma…”
   • [claimed-docs] “submission_blockers, an array displaying any blockers preventing contractor payments from being made and options for unblocking”

   proof ↗⚑ flag

   Rippling~partialclaimed3/10

   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.

   • [claimed-docs] “Rippling lets you compare your current pay run with previous ones to catch discrepancies before final approval.”
   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”

   proof ↗⚑ flag

Pay runs

1. ops userCancel or correct a submitted payroll before employees are paid

   weight 2 · round to Gusto
   Gusto~partialclaimed4/10

   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.

   • [claimed-docs] “Off-cycle payrolls handle one-off situations like corrections or special bonuses. They use the same withholding rates, deductions, and contr…”
   • [claimed-docs] “Off-cycle payrolls handle one-off situations like corrections or special bonuses.”
   • [claimed-docs] “One-off (or 'off-cycle') payrolls are available if you need to pay your team outside of the regular payroll schedule.”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls with processing_statuses=unprocessed.”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Rippling lets you compare your current pay run with previous ones to catch discrepancies before final approval.”
   • [claimed-docs] “Run payroll on your schedule Stay flexible and process payroll as often as you need — at no extra charge.”

   proof ↗⚑ flag

2. ops userRun an off-cycle payroll for bonuses, corrections, or terminations outside the regular schedule

   weight 3 · round to Gusto
   Gusto✓fullclaimed8/10

   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.

   • [claimed-docs] “Off-cycle payrolls handle one-off situations like corrections or special bonuses. They use the same withholding rates, deductions, and contr…”
   • [claimed-docs] “Off-cycle payrolls handle one-off situations like corrections or special bonuses.”
   • [claimed-docs] “One-off (or 'off-cycle') payrolls are available if you need to pay your team outside of the regular payroll schedule.”
   • [claimed-docs] “All benefits and deductions are default blocked and the payroll is default taxed at a fixed withholding rate when the off_cycle_reason is se…”
   • [claimed-docs] “Handle all aspects of payroll management including regular payroll runs, off-cycle payments, termination processing, and all associated fede…”
   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”

   proof ↗⚑ flag

   Rippling~partialclaimed6/10

   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.

   • [claimed-docs] “Add one-off bonuses to payroll in seconds.”
   • [claimed-docs] “Run payroll on your schedule Stay flexible and process payroll as often as you need — at no extra charge.”
   • [claimed-docs] “With Rippling, HR data—like new hires, salary changes, and benefits deductions—flow directly and automatically into Payroll.”

   proof ↗⚑ flag

3. ops userRun a full payroll cycle end-to-end — review hours and earnings, preview totals, and submit — in one flow

   weight 3 · round to Rippling
   Gusto~partialclaimed6/10

   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.

   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls”
   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls with processing_statuses=unprocessed.”
   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “But Gusto Embedded does the heavy lifting for you, handling everything from tax calculations to bank transfers.”
   • [claimed-docs] “One-off (or 'off-cycle') payrolls are available if you need to pay your team outside of the regular payroll schedule.”
   • [claimed-docs] “You can use the POST /v1/companies/{company_id}/contractor_payment_groups/preview to validate inputs, determine how fast a payment can be ma…”

   proof ↗⚑ flag

   Rippling~partialcommunity7/10

   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.

   • [claimed-docs] “Rippling lets you compare your current pay run with previous ones to catch discrepancies before final approval.”
   • [claimed-docs] “Approved hours from T&A flow instantly to Payroll—no more manual data entry or syncing issues. You can even review timesheets right inside e…”
   • [claimed-docs] “Add one-off bonuses to payroll in seconds.”
   • [claimed-docs] “Run payroll on your schedule Stay flexible and process payroll as often as you need — at no extra charge.”
   • [claimed-docs] “We automatically calculate payroll taxes and file them with the correct federal, state, and local agencies at precisely the right time.”
   • [community] “SF payroll firm Rippling delayed payouts after SVB collapse; some paychecks arrived late due to bank transition, but Rippling covered overdr…”
   • [community] “Someone put an extra comma in a CSV file and payroll was delayed for about 20k US employees who did not get paid timely. They covered any ov…”

   proof ↗⚑ flag

Pay schedules

1. ops userSet up multiple pay schedules (weekly, biweekly, semimonthly, monthly) across different teams

   weight 2 · round to Gusto
   Gusto~partialclaimed6/10

   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.

   • [claimed-docs] “Companies can have multiple work locations across different states. They might want everyone paid at the same time, or prefer different pay …”
   • [claimed-docs] “Companies can have multiple work locations across different states. They might want everyone paid at the same time, or prefer different pay …”
   • [claimed-docs] “We automatically pre-generate scheduled regular payrolls based on the company’s pay schedule and corresponding pay periods.”
   • [claimed-docs] “To onboard a company, you'll need: Company details (such as name, EIN), Business locations, Bank account information”

   proof ↗⚑ flag

   Rippling~partialclaimed3/10

   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.

   • [claimed-docs] “Run payroll on your schedule Stay flexible and process payroll as often as you need — at no extra charge.”

   proof ↗⚑ flag

Payment speed

1. founderPay employees by fast (next-day or 2-day) direct deposit instead of writing checks

   weight 2 · round to Gusto
   Gusto!disputedcontradicted5/10

   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.

   • [claimed-docs] “Gusto supports next-day, 2-day, and the standard 4-day payroll processing.”
   • [claimed-docs] “Gusto offers expedited payroll for qualifying companies, requiring submission only two business days (2-day payroll) or one business day (ne…”
   • [claimed-docs] “But Gusto Embedded does the heavy lifting for you, handling everything from tax calculations to bank transfers.”
   • [community] “Gusto doesn't support outside of US folks... the 2 day payroll... capped it at something like $60k even when we have millions in the bank ac…”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Run payroll on your schedule Stay flexible and process payroll as often as you need — at no extra charge.”
   • [claimed-docs] “We automatically calculate payroll taxes and file them with the correct federal, state, and local agencies at precisely the right time.”
   • [community] “SF payroll firm Rippling delayed payouts after SVB collapse; some paychecks arrived late due to bank transition, but Rippling covered overdr…”
   • [community] “Someone put an extra comma in a CSV file and payroll was delayed for about 20k US employees who did not get paid timely. They covered any ov…”

   proof ↗⚑ flag

Embedded payroll

1. developerEmbed white-label payroll into my own product through a partner API

   weight 3 · round to Gusto
   Gusto✓fullprobed8/10

   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.

   • [claimed-docs] “we've created Gusto Embedded Payroll— to help companies like you build and embed modern payroll and HR tools into your platforms in a fracti…”
   • [claimed-docs] “Gusto Embedded Payroll— to help companies like you build and embed modern payroll and HR tools into your platforms in a fraction of the time…”
   • [claimed-docs] “Partners can launch quickly with pre-built UI Flows, build custom experiences using APIs, or combine multiple approaches to create the ideal…”
   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “Handle all aspects of payroll management including regular payroll runs, off-cycle payments, termination processing, and all associated fede…”
   • [claimed-docs] “The Gusto Embedded Payroll React SDK offers component libraries with built-in business logic that helps our developers with the complexity o…”
   • [claimed-docs] “Gusto Embedded offers official client libraries for several programming languages to help you integrate with our API quickly and reliably.”
   • [claimed-docs] “System access tokens allow you to carry out application-level actions such as: Creating a partner-managed company”
   • [probe] “official MCP server documented at https://docs.gusto.com/embedded-payroll/docs/dev-assistant-mcp.md”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Publish to the Rippling App Shop and unlock support through our Choice program.”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”

   proof ↗⚑ flag

Payroll events

1. developerSubscribe to payroll lifecycle events (payroll processed, employee onboarded, payment failed) via webhooks to drive downstream automations

   weight 2 · round to Gusto
   Gusto~partialclaimed6/10

   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.

   • [claimed-docs] “A webhook is an HTTP request that delivers information about an event as it happens. We recommend that you integrate with Gusto's webhooks i…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event. Gusto will publish this webhook event when payroll credits…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event.”
   • [claimed-docs] “Gusto computes a hash message authentication code (HMAC) of the event payload using the verification_token”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our `payroll.paid` event. Gusto will publish this webhook event when payroll credi…”
   • [claimed-docs] “Create a webhook subscription to receive events of the specified subscription_types whenever there is a state change.”
   • [claimed-docs] “Returns the health status (`healthy`, `unhealthy`, or `unknown`) of the webhooks system based on the last ten minutes of activity.”
   • [claimed-docs] “This `verify` endpoint needs to be called with `verification_token` before webhook events can be sent to the registered webhook URL.”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [claimed-docs] “Use Rippling’s platform capabilities to run reports across your third-party app data or trigger workflows–like automating a Slack alert base…”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Gusto—none0/10

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

   • [community] “Gusto doesn't support outside of US folks... the 2 day payroll... capped it at something like $60k even when we have millions in the bank ac…”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

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

   weight 3 · round drawn
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

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

   weight 2 · round drawn
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

Accounting sync

1. ops userSync payroll journal entries automatically to my accounting software like QuickBooks or Xero

   weight 3 · round to Rippling
   Gusto~partialclaimed2/10

   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.

   • [claimed-docs] “We work with many types of apps, including accounting, applicant tracking, performance management, time tracking, and business operations so…”

   proof ↗⚑ flag

   Rippling~partialclaimed5/10

   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.

   • [claimed-docs] “Integrate with industry-leading accounting systems like Xero, QuickBooks, and NetSuite.”
   • [claimed-docs] “With Rippling, HR data—like new hires, salary changes, and benefits deductions—flow directly and automatically into Payroll.”
   • [claimed-docs] “Using multiple systems for your global team? That creates data silos and busy work. Rippling unifies all your systems.”

   proof ↗⚑ flag

2. ai-native userHave an agent pull payroll journal data via API or export and reconcile the entries into my ledger

   weight 3 · round drawn
   Gusto~partialclaimed4/10

   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.

   • [claimed-docs] “Upcoming regular payrolls can be retrieved by calling GET /v1/companies/{company_uuid}/payrolls”
   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “We work with many types of apps, including accounting, applicant tracking, performance management, time tracking, and business operations so…”
   • [claimed-docs] “A webhook is an HTTP request that delivers information about an event as it happens. We recommend that you integrate with Gusto's webhooks i…”
   • [claimed-docs] “When a payroll is paid out, your application may leverage our payroll.paid event. Gusto will publish this webhook event when payroll credits…”
   • [claimed-docs] “The Embedded Dev Assistant Model Context Protocol (MCP) server enables AI-powered code editors like Cursor and Windsurf, as well as general-…”

   proof ↗⚑ flag

   Rippling~partialclaimed4/10

   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.

   • [claimed-docs] “Integrate with industry-leading accounting systems like Xero, QuickBooks, and NetSuite.”
   • [claimed-docs] “Leverage Rippling’s unified platform and APIs to build custom apps that extend functionality across HR, IT, and finance.”
   • [claimed-docs] “Access to developer documentation and sandbox environment”
   • [github] “The Flux commands as part of the Rippling CLI allow both first-party and third-party App developers to create, manage and deploy Rippling-ho…”

   proof ↗⚑ flag

Reports

1. ops userGenerate payroll registers and gross-to-net reports and export them for analysis

   weight 2 · round to Gusto
   Gusto~partialclaimed3/10

   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.

   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”

   proof ↗⚑ flag

   Rippling—none0/10

   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.

   ⚑ flag

Compliance monitoring

1. founderGet proactive alerts when a new hire, location, or law change creates a compliance obligation

   weight 2 · round to Rippling
   Gusto—none0/10

   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.

   ⚑ flag

   Rippling~partialclaimed4/10

   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.

   • [claimed-docs] “Rippling automatically applies the correct labor policies—from overtime to breaks—based on location, and flags potential risks based on each…”
   • [claimed-docs] “Rippling automatically applies the correct labor policies—from overtime to breaks—based on location, and flags potential risks based on each…”
   • [claimed-docs] “Easily build custom workflows to notify people of important changes and automate administrative tasks—like triggering a reminder to pay a bo…”
   • [claimed-docs] “We automatically calculate payroll taxes and file them with the correct federal, state, and local agencies at precisely the right time.”

   proof ↗⚑ flag

Tax filing

1. ops userHave federal, state, and local payroll taxes calculated, filed, and remitted automatically

   weight 3 · round to Rippling
   Gusto!disputedcontradicted6/10

   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.

   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “Handle all aspects of payroll management including regular payroll runs, off-cycle payments, termination processing, and all associated fede…”
   • [claimed-docs] “But Gusto Embedded does the heavy lifting for you, handling everything from tax calculations to bank transfers.”
   • [claimed-docs] “Employees are required to configure two types of tax information as part of their onboarding: Federal tax... State tax:”
   • [claimed-docs] “Multi-location management * Department organization * Tax configuration and compliance * Bank account and payment setup”
   • [community] “10 days ago our 2021 W-2 forms... were updated by Gusto with W-2c forms that combine payments from two different tax IDs... 2021 Q1 payroll …”
   • [community] “Gusto has horrible customer support. We switched to JustWorks... For high stakes tax work they need professionals who take this work serious…”

   proof ↗⚑ flag

   Rippling✓fullclaimed8/10

   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.

   • [claimed-docs] “We automatically calculate payroll taxes and file them with the correct federal, state, and local agencies at precisely the right time.”
   • [claimed-docs] “Rippling instantly calculates and files payroll taxes for your employees worldwide.”

   proof ↗⚑ flag

2. ops userRun payroll for employees across multiple states with the right registrations and withholdings per state

   weight 3 · round to Gusto
   Gusto✓fullclaimed8/10

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

   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “Companies can have multiple work locations across different states. They might want everyone paid at the same time, or prefer different pay …”
   • [claimed-docs] “Handle all aspects of payroll management including regular payroll runs, off-cycle payments, termination processing, and all associated fede…”
   • [claimed-docs] “Employees are required to configure two types of tax information as part of their onboarding: Federal tax... State tax:”
   • [claimed-docs] “Companies can have multiple work locations across different states. They might want everyone paid at the same time, or prefer different pay …”

   proof ↗⚑ flag

   Rippling~partialclaimed6/10

   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.

   • [claimed-docs] “We automatically calculate payroll taxes and file them with the correct federal, state, and local agencies at precisely the right time.”
   • [claimed-docs] “Rippling automatically applies the correct labor policies—from overtime to breaks—based on location, and flags potential risks based on each…”
   • [claimed-docs] “Rippling automatically applies the correct labor policies—from overtime to breaks—based on location, and flags potential risks based on each…”
   • [claimed-docs] “Rippling instantly calculates and files payroll taxes for your employees worldwide.”

   proof ↗⚑ flag

3. ops userHave W-2s and 1099s generated and distributed to workers automatically at year-end

   weight 3 · round to Rippling
   Gusto!disputedcontradicted4/10

   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.

   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “Multi-location management * Department organization * Tax configuration and compliance * Bank account and payment setup”
   • [claimed-docs] “An employee must provide federal tax information to file and pay taxes correctly.”
   • [community] “10 days ago our 2021 W-2 forms... were updated by Gusto with W-2c forms that combine payments from two different tax IDs... 2021 Q1 payroll …”
   • [community] “Gusto has horrible customer support. We switched to JustWorks... For high stakes tax work they need professionals who take this work serious…”

   proof ↗⚑ flag

   Rippling~partialclaimed5/10

   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.

   • [claimed-docs] “Reduce HR requests by letting current and past employees view pay stubs and tax forms at any time.”
   • [claimed-docs] “We automatically calculate payroll taxes and file them with the correct federal, state, and local agencies at precisely the right time.”

   proof ↗⚑ flag

Time off

1. ops userDefine PTO policies with accruals and approvals that apply automatically to payroll

   weight 2 · round to Gusto
   Gusto~partialclaimed6/10

   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.

   • [claimed-docs] “This guide covers implementing time off requests and approvals using the Gusto Embedded Payroll time off request APIs. It covers the full re…”
   • [claimed-docs] “Use the time_off_request_management flow to give admins an embedded approval interface, or call the approve/decline endpoints directly from …”
   • [claimed-docs] “This guide covers implementing time off requests and approvals using the Gusto Embedded Payroll time off request APIs. It covers the full re…”
   • [claimed-docs] “It covers the full request lifecycle — from balance checking and submission through admin approval — and payroll integration.”
   • [claimed-docs] “Decline a pending or approved time off request. Requires an employer_note.”
   • [claimed-docs] “Partners with their own time off system can record approved time off in Gusto without re-implementing the approval workflow.”

   proof ↗⚑ flag

   Rippling~partialclaimed5/10

   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.

   • [claimed-docs] “Let employees clock in, request time off, and view timesheets—all in a single, easy-to-use app.”
   • [claimed-docs] “Sync hours, time off, deductions, and more with payroll from a single global system.”
   • [claimed-docs] “Approved hours from T&A flow instantly to Payroll—no more manual data entry or syncing issues. You can even review timesheets right inside e…”

   proof ↗⚑ flag

Time tracking

1. ops userHave hourly time entries and overtime flow directly into the payroll run

   weight 2 · round to Rippling
   Gusto~partialclaimed3/10

   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.

   • [claimed-docs] “We work with many types of apps, including accounting, applicant tracking, performance management, time tracking, and business operations so…”
   • [claimed-docs] “This guide covers implementing time off requests and approvals using the Gusto Embedded Payroll time off request APIs. It covers the full re…”
   • [claimed-docs] “Process regular and off-cycle payrolls * Calculate and file taxes automatically * Import historical payroll data * Handle multi-state tax re…”
   • [claimed-docs] “We automatically pre-generate scheduled regular payrolls based on the company’s pay schedule and corresponding pay periods.”

   proof ↗⚑ flag

   Rippling✓fullclaimed8/10

   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.

   • [claimed-docs] “Approved hours from T&A flow instantly to Payroll—no more manual data entry or syncing issues. You can even review timesheets right inside e…”
   • [claimed-docs] “Rippling automatically applies the correct labor policies—from overtime to breaks—based on location, and flags potential risks based on each…”
   • [claimed-docs] “Rippling automatically applies the correct labor policies—from overtime to breaks—based on location, and flags potential risks based on each…”
   • [claimed-docs] “Surface duplicate punches, missed clock-outs, and shift mismatches before payroll runs, not after.”
   • [claimed-docs] “Sync hours, time off, deductions, and more with payroll from a single global system.”

   proof ↗⚑ flag