Deel vs Justworks

Agent access

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

   weight 2 · round to Deel
   Deel✓fullprobed9/10

   Probe confirms llms.txt exists at developer.deel.com/llms.txt (HTTP 200) and per-page markdown (.md) versions are available, plus dedicated MCP/agent-oriented docs exist. Missing for 10: independent third-party confirmation that agents actually consume llms.txt effectively in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.deel.com/llms.txt # Welcome > Build powerful integrations with Deel's global workforce platfo…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.deel.com/home.md > For clean Markdown of any page, append .md to the page URL. > For a complete…”
   • [probe] “official MCP server documented at https://developer.deel.com/mcp/introduction”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”

   proof ↗⚑ flag

   Justworks—none0/10

   The probe explicitly shows llms.txt returns 404 and no agent-oriented docs (openapi/well-known) exist; no evidence of any AI-agent-facing documentation format.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 3 · round to Deel
   Deel✓fullprobed8/10

   Deel documents an official MCP server exposing tools (listOfContracts, createTimeOffRequest, etc.) that map to Deel API operations, with OAuth2 auto-handled by clients like Claude Desktop, Cursor, VS Code, and ChatGPT, and compatibility with any MCP-over-HTTP client. This is well-documented first-party evidence with no independent hands-on corroboration found. missing for 10: independent/hands-on confirmation of the MCP server working in practice, broader community validation.

   • [claimed-docs] “Connect AI agents to workforce data Expose contracts, people, payroll, and time data to Claude, ChatGPT, or your own agent with Deel's MCP …”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “the `createTimeOffRequest` tool submits a time-off request”
   • [claimed-docs] “Most MCP clients (Cursor, VS Code, Claude Desktop, ChatGPT) handle the OAuth2 authorization flow automatically.”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “The Deel MCP server is compatible with any client that implements the Model Context Protocol over HTTP transport.”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”
   • [probe] “official MCP server documented at https://developer.deel.com/mcp/introduction”

   proof ↗⚑ flag

   Justworks—none0/10

   Justworks is a PEO/HR SaaS platform, so an official MCP server is a plausible axis, but there is no evidence of any MCP server offering; probes for llms.txt and OpenAPI specs both returned 404, and all docs relate to payroll/benefits/integrations with Xero, not agent connectivity.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

3. ai-native userUse an official CLI

   weight 2 · round drawn
   Deel—none0/10

   Evidence shows Deel offers a REST API, an MCP server, and sandbox/webhooks, but nowhere is a dedicated CLI tool mentioned or documented; all developer interactions are via HTTP API or MCP, not a command-line interface.

   ⚑ flag

   Justworks—none0/10

   No evidence of an official CLI for Justworks; the evidence pack only covers HR/payroll web UI features and shows failed probes for llms.txt and OpenAPI specs, with no mention of any command-line tool.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 3 · round to Deel
   Deel✓fullprobed9/10

   Deel provides a well-documented public REST API with authentication (API tokens, OAuth2), versioning, sandbox environment, webhooks, and even an official MCP server exposing tools mapped to API operations—giving AI-native users multiple documented ways to drive the product programmatically. Missing for 10: independent third-party developer corroboration of real-world API usage beyond vendor docs.

   • [claimed-docs] “POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “The API Sandbox is a **separate testing environment** where you can safely test API calls without affecting real data or production systems.”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “Deel supports two authentication methods: ... API tokens ... OAuth2”
   • [claimed-docs] “OAuth 2.0 is the industry-standard protocol for authorization. It allows your app to access specific data in user accounts with explicit use…”
   • [claimed-docs] “The Deel API uses **header-based date versioning** as the standard for managing API changes. You specify a version date using the `X-Version…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.deel.com/llms.txt # Welcome > Build powerful integrations with Deel's global workforce platfo…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.deel.com/home.md > For clean Markdown of any page, append .md to the page URL. > For a complete…”
   • [probe] “official MCP server documented at https://developer.deel.com/mcp/introduction”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of a documented public API for Justworks; probes for llms.txt and OpenAPI/swagger specs all returned 404, and the help docs only cover UI-based workflows (payroll, benefits, time off, integrations), not API access.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 2 · round to Deel
   Deel~partialclaimed4/10

   Deel documents two auth methods—static API tokens and OAuth2 (deel-docs-27, deel-docs-28)—and OAuth2 is described as granting access to 'specific data... with explicit user consent,' implying some scoping, and MCP clients handle this OAuth2 flow automatically (deel-docs-17, deel-docs-29). However, there is no explicit documentation of configurable least-privilege scopes/permission sets for API tokens or a scope list for OAuth grants tailored to agent use. Missing for 10: explicit scope/permission catalog for API tokens, documented ability to restrict an agent's OAuth grant to specific resources/actions, and any hands-on confirmation that agents can be issued narrowly scoped credentials.

   • [claimed-docs] “Deel supports two authentication methods: ... API tokens ... OAuth2”
   • [claimed-docs] “OAuth 2.0 is the industry-standard protocol for authorization. It allows your app to access specific data in user accounts with explicit use…”
   • [claimed-docs] “Most MCP clients (Cursor, VS Code, Claude Desktop, ChatGPT) handle the OAuth2 authorization flow automatically.”
   • [claimed-docs] “The Deel MCP server is compatible with any client that implements the Model Context Protocol over HTTP transport.”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any API, API credentials, or scoped/least-privilege access token system; probes for llms.txt and OpenAPI specs both returned 404. This is an applicable axis for an HR platform (many SaaS HR tools expose scoped API tokens), but Justworks shows no such capability in the evidence pack.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round to Deel
   Deel~partialprobed5/10

   Deel provides a rich developer platform — a documented REST API, sandbox environment, webhooks, OAuth2/API-token auth, versioning, and an official MCP server exposing typed tools (createTimeOffRequest, listOfContracts, etc.) that AI agents can call directly — which supports agentic, AI-native integration. However, the evidence never explicitly documents official client SDKs (e.g., language-specific libraries like Python/Node/Go SDKs); all examples are raw REST calls or MCP tool calls, not SDK wrappers. missing for 10: explicit official SDK libraries/language bindings, SDK-specific docs or code samples, independent confirmation of SDK usage.

   • [claimed-docs] “POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “Deel supports two authentication methods: ... API tokens ... OAuth2”
   • [claimed-docs] “The API Sandbox is a **separate testing environment** where you can safely test API calls without affecting real data or production systems.”
   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [probe] “official MCP server documented at https://developer.deel.com/mcp/introduction”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any official SDKs, API client libraries, or developer-facing API documentation; probes for llms.txt and OpenAPI specs both returned 404s, and all docs relate to HR/payroll product usage, not developer integration.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to Deel
   Deel✓fullclaimed8/10

   Deel provides documented webhooks delivering real-time event notifications with HMAC-SHA256 signature security, explicitly framed as an alternative to polling for building integrations—directly matching the AI-native subscribe-to-events story. Missing for 10: no explicit list of supported event types/topics, and no independent/hands-on corroboration of webhook reliability.

   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [claimed-docs] “Webhooks are secured using HMAC-SHA256 signatures”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence in the pack mentions webhooks or event subscription APIs; documentation only covers payroll, benefits, time-off, and Xero integration workflows. Probes for API/OpenAPI specs also returned 404s, indicating no discoverable webhook or event API.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Deel
   Deel~partialprobed5/10

   Deel doesn't advertise a native in-app AI insights/analytics dashboard, but its MCP server explicitly exposes structured tools (e.g., calculateEorVersusEntityHiringCosts, listOfContracts) that let connected AI agents like Claude or ChatGPT pull and reason over contracts, payroll, and time data to generate insights/suggestions such as EOR-vs-entity cost comparisons. This satisfies the spirit of 'AI-generated insights from my data' but only via external agent connection, not a built-in AI feature surfaced directly in Deel's UI. missing for 10: a native in-product AI insights/recommendation feature (e.g., dashboard-level AI suggestions), independent evidence of the MCP-driven insight tools being used in practice.

   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “calculateEorVersusEntityHiringCosts | Compare EOR versus entity hiring costs”
   • [claimed-docs] “Expose contracts, people, payroll, and time data to Claude, ChatGPT, or your own agent with Deel's MCP server.”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”
   • [probe] “official MCP server documented at https://developer.deel.com/mcp/introduction”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence in the pack mentions AI-generated insights, suggestions, analytics recommendations, or any AI/ML feature surfaced to users; the docs cover only manual payroll, benefits, time-off, and Xero integration workflows. Missing for 10: any mention of AI-driven insights, automated suggestions, or predictive analytics within Justworks.

   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles. If you see any inaccuracies, …”
   • [claimed-docs] “Save time each quarter by checking that your employees’ payroll information is accurate at the end of each month.”
   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles.”

   proof ↗⚑ flag

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

   weight 2 · round to Deel
   Deel~partialclaimed5/10

   Deel provides the building blocks for autonomous automation—real-time webhooks that avoid polling, a public API, and an MCP server exposing tools (listOfContracts, createTimeOffRequest, etc.) that AI agents can invoke—so agents could be wired to act on Deel data without human intervention. However, there's no evidence of a native scheduling/orchestration engine or documented example of an agent running unattended background workflows end-to-end. Missing for 10: evidence of built-in automation/workflow engine, documented autonomous/scheduled agent runs, and independent confirmation of agents operating without human-in-the-loop.

   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [claimed-docs] “Webhooks are secured using HMAC-SHA256 signatures”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “the `createTimeOffRequest` tool submits a time-off request”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”
   • [claimed-docs] “The Deel MCP server is compatible with any client that implements the Model Context Protocol over HTTP transport.”
   • [claimed-docs] “Most MCP clients (Cursor, VS Code, Claude Desktop, ChatGPT) handle the OAuth2 authorization flow automatically.”

   proof ↗⚑ flag

   Justworks—none0/10

   Justworks is an HR/payroll PEO platform; the evidence pack shows no mention of automations, workflows, agents, or AI-driven background processes—only manual payroll, benefits, time-off, and integration setup steps. No documented capability for autonomous or agentic automation exists, so this applicable axis is unmet.

   ⚑ flag

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

   weight 3 · round drawn
   Deel—none0/10

   Evidence shows Deel exposes an MCP server so external AI agents (Claude, ChatGPT, custom agents) can query contracts/payroll/time-off data, but this is the opposite direction: it lets outside assistants pull from Deel, not a built-in assistant delegated tasks inside Deel's own product UI. No evidence of a native in-app AI assistant feature.

   • [claimed-docs] “Connect AI agents to workforce data Expose contracts, people, payroll, and time data to Claude, ChatGPT, or your own agent with Deel's MCP …”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any built-in AI assistant or agentic delegation feature within Justworks; all evidence pertains to HR/payroll workflows (payroll, benefits, time off, integrations) with no mention of AI capabilities.

   ⚑ flag

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

   weight 2 · round to Deel
   Deel✓fullprobed8/10

   Deel ships an official MCP server exposing contracts, payroll, and time-off tools that can be invoked by AI agents/assistants (Claude, ChatGPT, Cursor) using natural language, with structured tool definitions like createTimeOffRequest and listOfContracts documented in detail. This directly enables AI-native users to operate Deel via natural-language commands routed through MCP clients rather than a native chat UI. Missing for 10: independent/hands-on validation that these NL-driven MCP interactions work reliably in practice, and no evidence of a native in-product NL command interface outside the MCP integration.

   • [claimed-docs] “Connect AI agents to workforce data Expose contracts, people, payroll, and time data to Claude, ChatGPT, or your own agent with Deel's MCP …”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “the `createTimeOffRequest` tool submits a time-off request”
   • [claimed-docs] “Most MCP clients (Cursor, VS Code, Claude Desktop, ChatGPT) handle the OAuth2 authorization flow automatically.”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “createTimeOffRequest | Create a time-off request”
   • [claimed-docs] “listOfContracts | List contracts in the organization”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”
   • [probe] “official MCP server documented at https://developer.deel.com/mcp/introduction”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any natural-language command interface, chatbot, or AI assistant within Justworks; all documentation describes manual UI navigation (clicking menus, tabs, buttons). Probes for llms.txt and OpenAPI also failed, indicating no AI-native interface infrastructure.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Deel
   Deel~partialclaimed4/10

   Deel provides a sandbox environment with pre-populated data for safely testing API calls (deel-docs-3, deel-docs-4, deel-docs-22, deel-docs-26) and detailed API/MCP tool references, which supports experimentation, but there is no explicit evidence of an interactive in-browser API reference UI with 'try it now' runnable code examples (e.g., Swagger/OpenAPI explorer). Missing for 10: an explicit interactive API reference page with embedded runnable requests, and independent/hands-on confirmation that such a console exists.

   • [claimed-docs] “The API Sandbox is a **separate testing environment** where you can safely test API calls without affecting real data or production systems.”
   • [claimed-docs] “Pre-populated Data**: Use sample contracts, workers, and organizations right away.”
   • [claimed-docs] “Your sandbox comes with ready-to-use data for testing”
   • [claimed-docs] “The Deel API Sandbox is a **completely isolated testing environment** that mirrors production functionality without affecting real data, tri…”
   • [claimed-docs] “The Deel API uses **header-based date versioning** as the standard for managing API changes. You specify a version date using the `X-Version…”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any API reference, interactive docs, or runnable examples; probes for llms.txt and OpenAPI specs both returned 404, and all other evidence is unrelated help-center content about payroll/benefits/time-off features.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Deel—none0/10

   The evidence pack documents Deel's REST API endpoints, versioning headers, sandbox, and MCP server, but nowhere mentions an OpenAPI/Swagger spec file or download link for the API. Missing for 10: any reference to an OpenAPI/Swagger JSON/YAML spec, a spec download endpoint, or explicit machine-readable API schema.

   • [claimed-docs] “POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “The Deel API uses **header-based date versioning** as the standard for managing API changes. You specify a version date using the `X-Version…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.deel.com/llms.txt # Welcome > Build powerful integrations with Deel's global workforce platfo…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.deel.com/home.md > For clean Markdown of any page, append .md to the page URL. > For a complete…”

   proof ↗⚑ flag

   Justworks—none0/10

   Probes explicitly show no OpenAPI/swagger spec or llms.txt is available at any expected location, and no documentation references a machine-readable API spec.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 1 · round to Deel
   Deel✓fullclaimed9/10

   Deel documents a dedicated API Sandbox described as a 'completely isolated testing environment' that mirrors production without affecting real data, triggering payments, or creating legal contracts, and comes pre-populated with sample contracts/workers/orgs plus a reset function to restore clean data. This directly satisfies the ai-native story of testing without touching production. Missing for 10: independent/hands-on confirmation that the sandbox behaves as documented (only first-party docs available).

   • [claimed-docs] “The API Sandbox is a **separate testing environment** where you can safely test API calls without affecting real data or production systems.”
   • [claimed-docs] “Pre-populated Data**: Use sample contracts, workers, and organizations right away.”
   • [claimed-docs] “Resetting will delete all test data you've created and restore the original pre-populated sample data.”
   • [claimed-docs] “Your sandbox comes with ready-to-use data for testing”
   • [claimed-docs] “The Deel API Sandbox is a **completely isolated testing environment** that mirrors production functionality without affecting real data, tri…”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any sandbox or test environment for Justworks; the evidence pack only covers payroll, benefits, time-off, and Xero integration docs, plus failed probes for API/OpenAPI specs. Missing for 10: any mention of a sandbox/test mode, staging environment, or non-production API access.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 2 · round to Deel
   Deel~partialclaimed5/10

   Deel documents header-based date versioning (X-Version) for managing API changes, giving clear evidence of a versioned API scheme, but no evidence pack item describes a documented deprecation policy (e.g., sunset timelines, notice periods, or a changelog of deprecated versions). Missing for 10: explicit deprecation/sunset policy documentation, changelog of version retirements, migration guidance for deprecated versions.

   • [claimed-docs] “The Deel API uses **header-based date versioning** as the standard for managing API changes. You specify a version date using the `X-Version…”
   • [claimed-docs] “Deel supports two authentication methods: ... API tokens ... OAuth2”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any public API, versioning scheme, or deprecation policy; probes for llms.txt and OpenAPI specs both returned 404, and all documentation is about HR/payroll product usage, not developer APIs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Deel—none0/10

   The evidence shows individual REST/MCP operations (single contract creation, single time-off request, single contract listing) but no documented bulk/batch endpoints or batch MCP tools for operating on many items at once. Payroll 'consolidation' and webhook mentions do not describe bulk create/update operations across large item sets.

   • [claimed-docs] “# Create a contractor contract POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “createTimeOffRequest | Create a time-off request”
   • [claimed-docs] “listOfContracts | List contracts in the organization”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”

   proof ↗⚑ flag

   Justworks—none0/10

   The evidence pack shows only individual, single-item workflows (setting up one PTO policy, mapping one pay type, recording one fringe benefit) with no mention of bulk/batch operations, CSV import, multi-select actions, or APIs for programmatic bulk processing. There is no evidence of any bulk-operation capability for AI-native or automated workflows.

   ⚑ flag

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

   weight 3 · round to Deel
   Deel~partialclaimed5/10

   Deel offers webhooks for event notifications (deel-docs-6, deel-docs-7) which could feed automated actions, and its MCP server/API expose tools like createTimeOffRequest that agents could invoke, but there's no evidence of a built-in rules engine or automation/workflow builder where a user defines 'if event X then action Y' logic natively within Deel. missing for 10: a native rules/automation engine or workflow builder, documented trigger-condition-action configuration UI or API, and evidence of end-to-end automated event-to-action chaining without external glue code.

   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [claimed-docs] “Webhooks are secured using HMAC-SHA256 signatures”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “the `createTimeOffRequest` tool submits a time-off request”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”

   proof ↗⚑ flag

   Justworks—none0/10

   Evidence shows only fixed, built-in automations (holiday date rollover, automatic invoice sync) rather than any user-definable rule/trigger-action system; there is no documented workflow builder, conditional rule engine, or custom event-trigger capability in Justworks' help docs or API surface (llms.txt/openapi probes both 404).

   • [claimed-docs] “Justworks will automatically designate these same days as holidays each year. Our software knows that while Thanksgiving is on Thursday, Nov…”
   • [claimed-docs] “Sync method: Manually sync invoices or Allow them to automatically sync the day after processing.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Deel—none0/10

   Evidence shows Deel's API/MCP server exposes discrete tools (create contract, time-off request, list contracts) and webhooks for event-driven notifications, but there is no mention of scheduling, cron-like recurring job triggers, or workflow automation orchestration that an AI-native user could invoke. Webhooks only react to events rather than being scheduled or recurring on a timer.

   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any automation/workflow scheduling capability (e.g., API, webhooks, recurring job triggers) for AI-native or programmatic use; evidence only covers HR/payroll UI features and confirms absence of API/llms.txt endpoints. Missing for 10: any API or automation framework, scheduling/trigger mechanism, or documentation of recurring workflow support.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Deel—none0/10

   Deel's docs cover API/MCP tools, sandbox testing, and webhooks, but there is no evidence of any versioning, review, or rollback mechanism for automations built on Deel (e.g., no changelog, revision history, or rollback feature for workflows/API integrations).

   • [claimed-docs] “The API Sandbox is a **separate testing environment** where you can safely test API calls without affecting real data or production systems.”
   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence anywhere in the pack discusses versioning, reviewing, or rolling back automations; Justworks is an HR/payroll PEO platform with no documented automation-versioning or audit/rollback tooling. missing for 10: any version history feature, review/approval workflow for automations, rollback mechanism, or audit trail of automation changes.

   ⚑ flag

Benefits

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

   weight 2 · round drawn
   Deel—none0/10

   The evidence pack covers payroll, contracts, EOR, API/MCP integration, and sandbox testing, but contains no mention of health insurance offerings, enrollment workflows, or benefits deductions syncing to payroll. While benefits administration is a plausible axis for an HR/payroll platform like Deel, there is no documentation or feature evidence supporting this specific capability.

   ⚑ flag

   Justworks—none0/10

   The evidence pack covers payroll reports, fringe benefits payments, PTO policies, and Xero integration, but contains no documentation about offering or administering health insurance plans, employee enrollment in benefits, or syncing insurance deductions to payroll. Justworks PEO quoting is mentioned only regarding onboarding pricing, not benefits administration or deduction sync mechanics.

   ⚑ flag

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

   weight 2 · round drawn
   Deel—none0/10

   No evidence in the pack mentions 401(k), retirement plans, or benefits administration syncing with payroll; the pack only covers global payroll, contracts, MCP/API tooling, and unrelated community complaints.

   ⚑ flag

   Justworks—none0/10

   None of the evidence mentions 401(k)/retirement plan offerings or automatic contribution syncing with payroll; the pack only covers PTO, Xero integration, fringe benefits recording, and onboarding topics.

   ⚑ flag

Contractor payments

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

   weight 3 · round to Deel
   Deel✓fullclaimed7/10

   Deel's own marketing and API docs explicitly state it can 'pay every worker type... employees, contractors, and EOR workers' from one platform, and the API supports creating contractor contracts and payroll consolidation (deel-docs-11,19,24,14). This directly matches the ops story of paying both W-2 employees and 1099 contractors together. Missing for 10: explicit mention of US W-2 tax-form handling/classification, and independent/hands-on confirmation beyond vendor marketing copy.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”
   • [claimed-docs] “# Create a contractor contract POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “Consolidate multiple vendors”

   proof ↗⚑ flag

   Justworks—none0/10

   The evidence pack covers Justworks payroll, benefits, time off, and Xero integration features but contains no mention of 1099 contractors or contractor payments anywhere, so there's no evidence the platform supports paying both W-2 employees and 1099 contractors together.

   ⚑ flag

Global hiring

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

   weight 2 · round to Deel
   Deel✓fullclaimed8/10

   Deel's core offering directly matches this story: docs describe EOR and owned-entity payroll across 150+ countries with compliance and cost visibility (deel-docs-11, deel-docs-19, deel-docs-24), plus API/MCP tooling to create contracts and compare EOR vs entity hiring costs (deel-docs-10, deel-docs-14). Community complaints (deel-comm-1/2/3) concern customer service and data-privacy practices, not whether EOR/payroll actually functions, so they don't contradict the core capability. Missing for 10: independent third-party verification of payroll accuracy/compliance across countries beyond vendor marketing copy.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”
   • [claimed-docs] “calculateEorVersusEntityHiringCosts | Compare EOR versus entity hiring costs”
   • [claimed-docs] “# Create a contractor contract POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “Hire, manage, pay, & equip anyone, anywhere.”

   proof ↗⚑ flag

   Justworks—none0/10

   Justworks is a US-focused PEO; the evidence pack covers only domestic payroll, PTO, onboarding, and Xero integration — nothing about employer-of-record services or owned-entity payroll for international employees.

   ⚑ flag

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

   weight 3 · round to Deel
   Deel✓fullclaimed7/10

   Deel's docs describe creating contractor contracts via API and running compliant payroll for contractors across 150+ countries with automated compliance and unified data, directly matching the story's core ask. Missing for 10: explicit documentation of local-currency disbursement mechanics and independent verification of contract compliance quality (community feedback focuses on data-sharing/Wallet friction rather than confirming or denying local-currency payment execution).

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”
   • [claimed-docs] “# Create a contractor contract POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “Create a contractor contract POST https://api.letsdeel.com/rest/contracts”

   proof ↗⚑ flag

   Justworks—none0/10

   None of the evidence mentions international contractor payments, multi-currency payouts, or compliant international contractor agreements — Justworks documentation here covers only US domestic payroll, PEO onboarding, PTO, and Xero integration. Missing for 10: any mention of international contractor support, local currency payout, or compliant global contractor contracts.

   ⚑ 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 Deel
   Deel~partialclaimed5/10

   Deel's API/MCP docs show contract creation, listing contracts, time-off requests, and payroll/EOR cost comparisons, and the API supports creating contracts via POST /rest/contracts, suggesting an agent could programmatically onboard a contractor. However, there is no explicit documented endpoint or MCP tool for full employee onboarding covering compensation setup and tax setup as a single end-to-end workflow — the evidence only shows contract creation and cost comparison tools, not a unified 'create employee + compensation + tax' flow. missing for 10: explicit API/MCP endpoints for employee creation with compensation configuration, dedicated tax-setup endpoint/tool, and a documented end-to-end onboarding workflow example or independent confirmation it works as described.

   • [claimed-docs] “POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “# Create a contractor contract POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “Create a contractor contract POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “calculateEorVersusEntityHiringCosts | Compare EOR versus entity hiring costs”
   • [claimed-docs] “listOfContracts | List contracts in the organization”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any public API for creating employees, compensation, or tax setup — probes for llms.txt and OpenAPI specs both returned 404, and all documentation describes manual UI workflows (Time Off tab, Pay menu, Xero integration setup) rather than programmatic onboarding endpoints.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”
   • [claimed-docs] “Once your start date is confirmed by Justworks PEO, you can let your current providers for payroll, EPLI (if applicable), and health insuran…”
   • [claimed-docs] “Justworks PEO does not provide estimates, rather we provide customized quotes that are reflective of the plans and pricing your company woul…”
   • [claimed-docs] “Companies in expedited enrollment can complete the enrollment process in 2-3 weeks.”

   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
   Deel—none0/10

   The evidence pack covers contracts API, payroll, MCP tools, and sandbox testing, but contains no mention of offer-letter e-signature workflows or per-employee document storage. Missing for 10: e-signature capability documentation, offer letter templates, per-employee document repository evidence.

   ⚑ flag

   Justworks—none0/10

   None of the evidence mentions offer letters, e-signature, or document storage per employee; all cited docs relate to payroll, benefits, time off, and accounting integrations. This is an applicable axis for an HR/PEO platform, but there is no evidence Justworks delivers it.

   ⚑ 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 Justworks
   Deel—none0/10

   The evidence pack covers Deel's API/MCP developer tools, payroll/contract endpoints, and community complaints, but contains no mention of a self-serve onboarding flow, W-4/I-9 collection, or bank detail setup for new hires. Onboarding is plausibly a core Deel HR feature, but no evidence documents this specific capability, so it cannot be credited as delivered.

   ⚑ flag

   Justworks~partialclaimed5/10

   Docs confirm employees self-enroll and Justworks collects W-4 filing/withholding info directly so they don't need to file a W-4 themselves, and general onboarding timelines (2-3 weeks) are documented. However, no evidence explicitly confirms I-9 collection or bank/direct-deposit detail collection as part of a unified self-serve pre-day-one flow. Missing for 10: explicit I-9 collection/verification workflow, explicit bank account/direct deposit setup step, and confirmation these are bundled into one onboarding flow before day one.

   • [claimed-docs] “Justworks collects your employees' filing status, withholding, and exemption information when they enroll with Justworks, so that they don't…”
   • [claimed-docs] “Justworks collects your employees’ filing status, withholding, and exemption information when they enroll with Justworks, so that they don’t…”
   • [claimed-docs] “Companies in expedited enrollment can complete the enrollment process in 2-3 weeks.”
   • [claimed-docs] “Once your start date is confirmed by Justworks PEO, you can let your current providers for payroll, EPLI (if applicable), and health insuran…”

   proof ↗⚑ flag

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

   weight 2 · round to Deel
   Deel~partialclaimed6/10

   Deel exposes a broad REST API and MCP server covering contracts, payroll, time-off, people data, and more, with sandbox/testing and webhook support, indicating substantial parity between API and UI capabilities. However, no evidence explicitly confirms full 1:1 parity between every UI feature and API/MCP tool coverage; documentation shows selected core objects (contracts, time-off, EOR cost calc) rather than an exhaustive UI-equivalence map. Missing for 10: explicit statement or audit confirming all UI actions have API equivalents, and coverage of less common UI workflows (e.g., compliance docs, benefits admin) via API.

   • [claimed-docs] “POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “The Deel MCP server exposes Deel platform operations as tools that AI agents and assistants can invoke directly.”
   • [claimed-docs] “the `createTimeOffRequest` tool submits a time-off request”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “listOfContracts | List contracts in the organization”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”
   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [claimed-docs] “The API Sandbox is a **separate testing environment** where you can safely test API calls without affecting real data or production systems.”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of a public API at all — probes for llms.txt and OpenAPI specs both returned 404, and all docs describe UI-only workflows (payroll, time off, benefits, integrations) with no mention of programmatic access matching UI capabilities.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 3 · round to Deel
   Deel~partialclaimed3/10

   Deel's REST API lets you programmatically retrieve contracts, workers, and payroll data in JSON (an open format) via endpoints like listOfContracts, which could support partial self-service extraction, but there is no documented bulk 'export all my data' feature, account-closure/offboarding data-export workflow, or explicit data-portability guarantee. missing for 10: dedicated full-account data export tool, documented account termination/data takeout process, independent confirmation that all data types (payroll, docs, history) are exportable.

   • [claimed-docs] “POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “listOfContracts | List contracts in the organization”
   • [claimed-docs] “# Create a contractor contract POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “Deel supports two authentication methods: ... API tokens ... OAuth2”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any data export or data portability feature in open formats, nor any documented account-closure/export workflow; evidence only covers payroll, benefits, time off, and Xero integration setup. Probes for llms.txt and OpenAPI both returned 404, suggesting no discoverable API/export tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ 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 drawn
   Deel—none0/10

   Evidence shows Deel's API/MCP exposes contracts, time-off, and EOR cost-comparison tools, and general marketing about running global payroll, but there is no documented payroll-run preview endpoint, no anomaly-detection capability, and no approval workflow surfaced via API/MCP.

   • [claimed-docs] “calculateEorVersusEntityHiringCosts | Compare EOR versus entity hiring costs”
   • [claimed-docs] “listOfContracts | List contracts in the organization”
   • [claimed-docs] “createTimeOffRequest | Create a time-off request”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any API for payroll preview, run automation, or anomaly detection; probes for llms.txt and OpenAPI specs both return 404, and docs describe only manual UI workflows for payroll review.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”
   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles. If you see any inaccuracies, …”
   • [claimed-docs] “Save time each quarter by checking that your employees’ payroll information is accurate at the end of each month.”

   proof ↗⚑ flag

Pay runs

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

   weight 2 · round drawn
   Deel—none0/10

   The evidence pack shows Deel's payroll processing, API/MCP tooling, and general platform capabilities, but nothing documents an ability to cancel or correct a submitted payroll run before employees are paid; no API endpoint, MCP tool, or docs reference this workflow. Community comments discuss unrelated complaints (data privacy, wallet terms) and don't address payroll correction/cancellation.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Process payroll globallyConsolidate multiple vendors”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”

   proof ↗⚑ flag

   Justworks—none0/10

   The evidence pack covers payroll data verification, fringe benefits recording, PTO policies, integrations, and onboarding, but contains no mention of canceling, voiding, or correcting a payroll run once submitted before pay date. Missing for 10: any documentation on payroll cancellation/correction workflow, deadlines for edits after submission, or off-cycle correction process.

   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles. If you see any inaccuracies, …”
   • [claimed-docs] “Save time each quarter by checking that your employees’ payroll information is accurate at the end of each month.”
   • [claimed-docs] “You can check this information in A nalytics > Custom Payroll Report and in your employees' Justworks profiles.”
   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Deel—none0/10

   The evidence pack shows general global payroll processing capability (docs-11, docs-19, docs-24) but contains no mention of off-cycle payroll runs, bonus payments, correction runs, or termination-related payroll outside the regular schedule. A community report even notes that 'any exceptions to the rigid workflow breaks the entire process' (deel-comm-3), suggesting non-standard payroll actions may not be well supported, but this is not concrete enough to call it disputed—there's simply no direct evidence the feature exists.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”
   • [community] “how terrible is it to deal with deel? ...any exceptions to the rigid workflow breaks the entire process. Customer service is completely help…”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence pack items mention off-cycle payroll runs, bonus payments, correction runs, or termination pay processing—only recurring payroll, fringe benefits recording, time-off policies, and integrations are documented. Missing for 10: any documentation of off-cycle/supplemental payroll run capability, bonus/termination payment workflows, or scheduling outside the regular cycle.

   ⚑ 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 Justworks
   Deel~partialclaimed3/10

   Deel's marketing pages claim it can 'run accurate, compliant payroll' and 'process payroll globally' across 150+ countries, implying payroll execution capability, but there is no documentation of the actual end-to-end flow (reviewing hours/earnings, previewing totals, submitting) as a single unified action — the API/MCP evidence only covers contracts, time-off requests, and cost comparisons, not a payroll run review-preview-submit sequence. Missing for 10: explicit description or screenshot/API of the review-hours step, a totals-preview step, and a single submit action tying them together.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”
   • [claimed-docs] “Process payroll globallyConsolidate multiple vendors”
   • [claimed-docs] “Consolidate multiple vendors”

   proof ↗⚑ flag

   Justworks~partialclaimed4/10

   Docs confirm ops can review payroll accuracy (via Custom Payroll Report and employee profiles) before running payroll and can record fringe benefits during the pay flow, implying a review-then-run sequence, but there is no explicit description of a 'preview totals' screen or a single continuous submit action tying review, preview, and submission together. missing for 10: explicit preview-totals step, description of final submit/confirmation action, evidence of a single unified flow rather than separate menu actions.

   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles. If you see any inaccuracies, …”
   • [claimed-docs] “Save time each quarter by checking that your employees’ payroll information is accurate at the end of each month.”
   • [claimed-docs] “You need to record taxable fringe benefits that you provided to your employees outside of Justworks by clicking on Pay in the side navigatio…”

   proof ↗⚑ flag

Pay schedules

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

   weight 2 · round drawn
   Deel—none0/10

   Evidence pack covers Deel's global payroll marketing claims, API/MCP docs, and community complaints, but nothing specifically documents configuring multiple pay schedules (weekly, biweekly, semimonthly, monthly) across different teams. Missing for 10: any docs, UI screenshots, or API reference showing pay schedule/frequency configuration per team.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”

   proof ↗⚑ flag

   Justworks—none0/10

   None of the evidence discusses configuring multiple pay schedules (weekly, biweekly, semimonthly, monthly) or assigning different schedules to different teams; the pack covers payroll accuracy checks, fringe benefits recording, PTO policies, Xero integration mapping, and onboarding — none address pay frequency setup. Missing for 10: any documentation of pay schedule configuration, frequency options, or per-team/department schedule assignment.

   ⚑ flag

Payment speed

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

   weight 2 · round drawn
   Deel—none0/10

   The evidence pack contains general claims about running global payroll (150+ countries, unified data) but no specific mention of direct deposit speed (next-day or 2-day) or check-replacement wire/ACH capability for employees. Community evidence even suggests Deel pushed a proprietary 'Deel Wallet' card rather than standard bank deposit, but this isn't framed against a documented claim. Missing for 10: any documentation of direct deposit timing, ACH/bank transfer speed, or comparison to check payments.

   ⚑ flag

   Justworks—none0/10

   No evidence in the pack mentions direct deposit speed, next-day/2-day pay, or check-writing alternatives; the payroll docs cover custom reports, W-4 collection, and fringe benefits but not deposit timing or methods. Missing for 10: any mention of direct deposit, payment speed options, or replacing paper checks.

   ⚑ flag

Embedded payroll

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

   weight 3 · round to Deel
   Deel~partialclaimed4/10

   Deel exposes a documented REST API and MCP tools for contracts, payroll, and time-off data (e.g., deel-docs-1, deel-docs-11, deel-docs-19, deel-docs-27) that a developer could integrate into their own product, with OAuth2/API tokens and a sandbox for testing (deel-docs-3, deel-docs-26, deel-docs-28). However, none of the evidence mentions a formal 'white-label' or partner-branding program, reseller terms, or embedded-finance partnership model — the API is presented as direct integration, not white-label embedding. Missing for 10: explicit white-label/partner API program docs, branding customization options, and partner agreement terms.

   • [claimed-docs] “POST https://api.letsdeel.com/rest/contracts”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Deel supports two authentication methods: ... API tokens ... OAuth2”
   • [claimed-docs] “OAuth 2.0 is the industry-standard protocol for authorization. It allows your app to access specific data in user accounts with explicit use…”
   • [claimed-docs] “The API Sandbox is a **separate testing environment** where you can safely test API calls without affecting real data or production systems.”
   • [claimed-docs] “The Deel API Sandbox is a **completely isolated testing environment** that mirrors production functionality without affecting real data, tri…”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any partner/embeddable API, white-label payroll offering, or developer platform; probes for OpenAPI/llms.txt returned 404s and all docs are end-user help articles about running payroll within Justworks' own UI, not embedding it into third-party products.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   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 Deel
   Deel~partialclaimed6/10

   Deel's docs confirm a webhooks system delivering real-time notifications for 'key platform events' with HMAC-SHA256 signed payloads, avoiding polling — directly supporting event-driven downstream automation. However, the evidence never enumerates specific payroll lifecycle events like 'payroll processed', 'employee onboarded', or 'payment failed', so it's unclear the exact event catalog matches the story's examples. Missing for 10: an explicit list of supported webhook event types/payloads, and any hands-on/community confirmation of reliability in production use.

   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”
   • [claimed-docs] “Webhooks are secured using HMAC-SHA256 signatures”

   proof ↗⚑ flag

   Justworks—none0/10

   No evidence of any webhook or event subscription capability; probes for API/OpenAPI specs returned 404s and no documentation mentions payroll lifecycle event notifications. Missing for 10: webhook subscription mechanism, documented event types (payroll processed, onboarding, payment failed), any developer API reference.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Deel—none0/10

   No evidence pack items mention data residency, region selection, or where data is stored; the API/MCP/sandbox docs cover functionality but not storage location or residency controls. Community items are unrelated to data residency and are ignored. missing for 10: any documentation of region/residency options, data center locations, or configurable data storage location.

   ⚑ flag

   Justworks—none0/10

   No evidence in the pack addresses data residency, regional storage options, or any data locality controls for Justworks; all cited docs concern payroll, benefits, time off, and Xero integration. Missing for 10: any mention of data center regions, residency options, or storage location controls.

   ⚑ flag

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

   weight 3 · round drawn
   Deel—none0/10

   The evidence pack contains no documentation, settings, or policy statements about opting out of AI model training on user data—only API/MCP integration docs and unrelated community complaints about data sharing for marketing. Since Deel exposes workforce data via MCP to AI agents, this is a fair privacy question, but nothing in the pack addresses training-data controls.

   ⚑ flag

   Justworks—none0/10

   Justworks is a PEO/HR payroll platform; the evidence pack contains only payroll, benefits, time-off, and Xero integration docs with no mention of AI model training, data usage policies, or opt-out controls for AI training. No evidence exists that this capability is addressed at all.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Deel—none0/10

   No evidence pack item describes any Deel feature letting an AI-native user configure data retention periods or delete data used by AI agents/MCP integrations; sandbox reset only pertains to test data, not production or AI-agent data. Community reports (deel-comm-1) even suggest Deel retains and reuses data (e.g., marketing outreach) beyond user control, but this doesn't confirm a specific retention/deletion control feature exists to be disputed.

   ⚑ flag

   Justworks—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or any AI-specific privacy/data governance features for Justworks; all evidence concerns payroll, benefits, time off, and Xero integration workflows.

   ⚑ flag

Accounting sync

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

   weight 3 · round to Justworks
   Deel—none0/10

   Evidence covers Deel's global payroll processing, API/webhooks, sandbox, and MCP server, but there is no mention of a QuickBooks/Xero accounting sync or automated GL journal-entry export capability anywhere in the pack.

   ⚑ flag

   Justworks✓fullclaimed8/10

   Docs describe a documented Xero integration where pay types map to Chart of Accounts, with department/office/employee-level overrides, and invoices can auto-sync the day after payroll processing (justworks-docs-12, -5, -19, -6, -13, -20, -25). This directly matches the story of syncing payroll journal entries to accounting software automatically. Missing for 10: explicit QuickBooks integration details (only Xero is documented) and independent/hands-on corroboration beyond vendor help docs.

   • [claimed-docs] “Before you can start setting up, you’ll first need to connect your Xero account. Clicking “Connect Xero” will redirect you to login to Xero.”
   • [claimed-docs] “Now that you've set up your preferences, you'll need to map each pay type in Justworks to an account or sub-account from your Chart of Accou…”
   • [claimed-docs] “you'll need to map each pay type in Justworks to an account or sub-account from your Chart of Accounts in Xero.”
   • [claimed-docs] “Once you've set up your default company mappings you'll have the option to override the same line items by department to their own accounts …”
   • [claimed-docs] “You are also able to override line items at the individual employee level.”
   • [claimed-docs] “Similar to departments, you are able to override line items at the individual Office level.”
   • [claimed-docs] “Sync method: Manually sync invoices or Allow them to automatically sync the day after processing.”
   • [claimed-docs] “You are also able to override line items at the individual employee level. This is optional and you do not need to map each line item and on…”

   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 to Deel
   Deel~partialclaimed5/10

   Deel's API and MCP server expose payroll data (and contracts, people, time data) that an agent could pull via API calls or MCP tools like listOfContracts, and sandbox/webhook infrastructure supports building such integrations. However, there is no explicit evidence of a 'payroll journal' entry format, GL-code export, or reconciliation-into-ledger capability (e.g., no mention of accounting export formats or ledger-sync tools). missing for 10: dedicated payroll journal/GL export endpoint, explicit reconciliation or ledger-sync tooling, evidence of accounting-system integration.

   • [claimed-docs] “Connect AI agents to workforce data Expose contracts, people, payroll, and time data to Claude, ChatGPT, or your own agent with Deel's MCP …”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “The Deel MCP server exposes tools that map to Deel API operations. Each tool accepts structured input parameters and returns JSON results.”
   • [claimed-docs] “listOfContracts | List contracts in the organization”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”
   • [claimed-docs] “Deel Webhooks deliver real-time notifications for key platform events, allowing you to build efficient and responsive integrations without r…”

   proof ↗⚑ flag

   Justworks~partialprobed4/10

   Justworks provides a Custom Payroll Report in Analytics and native Xero GL-mapping/sync (with department/office/employee-level overrides and manual or automatic invoice sync) that could serve as an export/reconciliation path, but there is no evidence of a public API, and probes explicitly show no OpenAPI spec or llms.txt endpoint, so an agent could not pull data programmatically as described. missing for 10: documented payroll/journal API for agent access, evidence of agent-friendly export automation, confirmation that Custom Payroll Report can be pulled without manual UI steps.

   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles. If you see any inaccuracies, …”
   • [claimed-docs] “Now that you've set up your preferences, you'll need to map each pay type in Justworks to an account or sub-account from your Chart of Accou…”
   • [claimed-docs] “Once you've set up your default company mappings you'll have the option to override the same line items by department to their own accounts …”
   • [claimed-docs] “Before you can start setting up, you’ll first need to connect your Xero account. Clicking “Connect Xero” will redirect you to login to Xero.”
   • [claimed-docs] “You are also able to override line items at the individual employee level.”
   • [claimed-docs] “Sync method: Manually sync invoices or Allow them to automatically sync the day after processing.”
   • [claimed-docs] “You are also able to override line items at the individual employee level. This is optional and you do not need to map each line item and on…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://help.justworks.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.justworks.com/openapi.json, https://help.justworks.com/swagger.json, https://help.justw…”

   proof ↗⚑ flag

Reports

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

   weight 2 · round to Justworks
   Deel—none0/10

   Evidence confirms Deel runs global payroll and exposes payroll data via API/MCP, but there is no mention of payroll register reports, gross-to-net breakdowns, or export/analysis features for ops users. Missing for 10: payroll register report generation, gross-to-net report format, export functionality (CSV/Excel) for analysis.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”

   proof ↗⚑ flag

   Justworks~partialclaimed5/10

   Evidence confirms an Analytics > Custom Payroll Report exists for checking payroll data, implying report generation, but there's no explicit mention of gross-to-net reports or export/download functionality for analysis. Missing for 10: explicit gross-to-net report detail, export/download format confirmation (CSV/Excel), and independent corroboration of reporting depth.

   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles. If you see any inaccuracies, …”
   • [claimed-docs] “You can check this information in A nalytics > Custom Payroll Report and in your employees' Justworks profiles.”
   • [claimed-docs] “You can check this information in Analytics > Custom Payroll Report and in your employees' Justworks profiles.”
   • [claimed-docs] “Save time each quarter by checking that your employees’ payroll information is accurate at the end of each month.”

   proof ↗⚑ flag

Compliance monitoring

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

   weight 2 · round drawn
   Deel—none0/10

   Evidence covers Deel's API, MCP server, sandbox, and general payroll/compliance marketing claims, but nothing describes proactive alerts or notifications tied to compliance obligations triggered by new hires, location changes, or law changes; webhooks exist for platform events generally, not compliance-specific alerting. Community evidence is unrelated to this axis. No evidence of a compliance-alerting feature.

   ⚑ flag

   Justworks—none0/10

   No evidence pack items mention proactive compliance alerts for new hires, new locations, or law changes; the docs cover payroll accuracy checks, benefits recording, PTO setup, and Xero integration but nothing about automated compliance notifications. Missing for 10: any mention of proactive alerting, multi-state/location compliance triggers, or law-change notifications.

   ⚑ flag

Tax filing

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

   weight 3 · round to Justworks
   Deel—none0/10

   Evidence only offers generic claims of 'automated compliance' and global payroll processing across 150+ countries, with no specific mention of federal/state/local tax calculation, filing, or remittance automation for US payroll. Missing for 10: any documentation of US tax jurisdiction handling, filing cadence, remittance to tax authorities, or compliance guarantees specific to federal/state/local payroll taxes.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”

   proof ↗⚑ flag

   Justworks~partialclaimed4/10

   Evidence shows Justworks collects employee withholding/filing status info and provides payroll accuracy checks, implying tax handling is embedded in payroll runs, but no documentation explicitly confirms automatic calculation, filing, and remittance of federal/state/local payroll taxes. Missing for 10: explicit docs on tax filing cadence, remittance to agencies, and multi-jurisdiction tax compliance guarantees.

   • [claimed-docs] “Justworks collects your employees' filing status, withholding, and exemption information when they enroll with Justworks, so that they don't…”
   • [claimed-docs] “Justworks collects your employees’ filing status, withholding, and exemption information when they enroll with Justworks, so that they don’t…”
   • [claimed-docs] “Save time each quarter by checking that your employees’ payroll information is accurate at the end of each month.”

   proof ↗⚑ flag

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

   weight 3 · round to Deel
   Deel~partialclaimed4/10

   Deel's marketing pages claim 'automated compliance' and payroll processing across 150+ countries, implying broad tax/compliance handling, but no evidence specifically addresses U.S. multi-state payroll registrations or per-state withholding mechanics. Missing for 10: documentation on state-specific tax registration setup, per-state withholding calculation details, and any hands-on/independent verification of multi-state payroll accuracy.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Run accurate, compliant payroll for employees, contractors, and EOR workers across 150+ countries with unified data, automated compliance, a…”
   • [claimed-docs] “Process payroll globallyConsolidate multiple vendors”

   proof ↗⚑ flag

   Justworks—none0/10

   Evidence covers general payroll setup, W-4-equivalent withholding collection, benefits recording, and PTO/Xero integration, but nothing addresses multi-state employer tax registrations or per-state withholding/compliance handling that the story specifically asks about.

   ⚑ flag

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

   weight 3 · round drawn
   Deel—none0/10

   Evidence pack covers Deel's API, MCP server, sandbox, and general global payroll/EOR marketing claims, but contains no mention of W-2/1099 tax form generation or year-end distribution to workers.

   ⚑ flag

   Justworks—none0/10

   None of the evidence items mention W-2/1099 generation or year-end tax form distribution; the pack only covers payroll reporting, benefits recording, PTO setup, onboarding, and Xero integration. Absence of evidence for this applicable payroll-compliance capability yields 'none'. missing for 10: any documentation of W-2/1099 generation, e-filing, or worker distribution at year-end.

   ⚑ flag

Time off

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

   weight 2 · round to Justworks
   Deel—none0/10

   Evidence only shows a generic 'createTimeOffRequest' MCP/API tool for submitting a time-off request; there is no documentation of defining PTO accrual policies, approval workflows, or automatic application of those policies to payroll runs. missing for 10: PTO policy configuration, accrual rule definitions, approval workflow documentation, and evidence linking time-off data to payroll processing.

   • [claimed-docs] “the `createTimeOffRequest` tool submits a time-off request”
   • [claimed-docs] “createTimeOffRequest | Create a time-off request”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”

   proof ↗⚑ flag

   Justworks~partialclaimed6/10

   Docs confirm PTO policy setup (name, dates, policy type, timecard sync) and integration with payroll/timecards via docs-3, docs-11, docs-16, plus automated holiday handling (docs-24). However, evidence does not detail accrual rules/rates or an explicit approval workflow for time-off requests feeding into payroll. missing for 10: explicit accrual rate configuration details, documented approval workflow for PTO requests, and independent confirmation that approved PTO flows automatically into payroll processing.

   • [claimed-docs] “On the setup page you'll be able to enter these key policy details: Policy name ... Policy start date ... Policy end date ... Policy type ..…”
   • [claimed-docs] “Getting set up for PTO with Justworks is easy. From Home, select Time Off from the main navigation.”
   • [claimed-docs] “Start by selecting into the Time Off tab in the left-hand side menu of your Justworks Payroll account. Then, click the Policies tab, followe…”
   • [claimed-docs] “Justworks will automatically designate these same days as holidays each year. Our software knows that while Thanksgiving is on Thursday, Nov…”

   proof ↗⚑ flag

Time tracking

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

   weight 2 · round drawn
   Deel—none0/10

   Evidence shows Deel's payroll platform and MCP tools cover contracts, people, payroll, and time-off requests, but nothing documents hourly time entry tracking or overtime calculations flowing into a payroll run. Missing for 10: hourly time entry logging, overtime calculation rules, and explicit integration of time-tracking data into payroll processing.

   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “Pay every worker type, in every country, from one platform. Run accurate, compliant payroll for employees, contractors, and EOR workers acro…”
   • [claimed-docs] “createTimeOffRequest | Create a time-off request”
   • [claimed-docs] “Each tool maps to a Deel API operation. For example, the `listOfContracts` tool retrieves contracts, and the `createTimeOffRequest` tool sub…”

   proof ↗⚑ flag

   Justworks—none0/10

   Evidence covers PTO policy setup, payroll accuracy checks, integrations, and fringe benefits, but there is no mention of hourly time entry tracking or overtime calculation flowing into payroll runs.

   ⚑ flag