Perplexity vs Grok

Agent access

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

   weight 2 · round drawn
   Perplexity✓fullprobed9/10

   Perplexity's docs site directly serves an llms.txt file (HTTP 200) plus per-page .md variants that explicitly point agents to the llms.txt index for full documentation, confirming a genuine agent-oriented docs surface; this is corroborated by an OpenAPI spec, official MCP server, and CLI docs also structured for agent consumption. Missing for 10: independent third-party confirmation that agents actually consume this llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.perplexity.ai/llms.txt # Perplexity > Perplexity API documentation for building with the Agent API…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.perplexity.ai/docs/getting-started/overview.md > ## Documentation Index > Fetch the complete documen…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
   • [claimed-docs] “The pplx CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and co…”

   proof ↗⚑ flag

   Grok✓fullprobed9/10

   The docs site serves a discoverable llms.txt (HTTP 200, describing itself as official xAI developer documentation) and every doc page is also available in plain markdown form, which is exactly the agent-oriented docs pattern the story asks for. Missing for 10: independent/community confirmation that agents actually consume this llms.txt successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.x.ai/llms.txt # SpaceXAI API Documentation > Official SpaceXAI (xAI) developer documentation at ht…”
   • [claimed-docs] “Grok 4.6, SpaceXAI's frontier model for coding, agentic tasks, and knowledge work, is now available on the xAI API. It has a 500k context wi…”
   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”

   proof ↗⚑ flag

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

   weight 2 · round to Perplexity
   Perplexity✓fullprobed7/10

   Perplexity provides an OpenAI-compatible Agent API with structured JSON output, model fallback, sandboxed code execution, and reusable profiles, plus a dedicated `pplx` CLI explicitly designed for shell pipelines and coding agents that need current web results — all suitable for headless/CI automation. missing for 10: no independent/hands-on report confirming real-world CI pipeline usage, and no documented rate-limit/quota guidance specifically for automated batch workloads.

   • [claimed-docs] “The pplx CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and co…”
   • [claimed-docs] “The `pplx` CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and …”
   • [claimed-docs] “The `pplx` CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and …”
   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer”
   • [claimed-docs] “Structured output makes the model return JSON that conforms to a schema you define, so you can deserialize it directly.”
   • [claimed-docs] “Model fallback enables specifying multiple models in a `models` array. The API tries each model in order until one succeeds, providing autom…”
   • [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
   • [probe] “official CLI documented at https://docs.perplexity.ai/docs/cli/overview”

   proof ↗⚑ flag

   Grok~partialprobed6/10

   The xAI API (REST, OpenAPI spec confirmed via probe, streaming, structured outputs, quickstart script) provides a clear headless programmatic interface suitable for automation/CI, and community mentions a 'terminal' mode for Grok Build. However there is no explicit CI/CD documentation, GitHub Actions example, or non-interactive automation guide. missing for 10: dedicated CI/CD integration docs, GitHub Actions or pipeline examples, explicit 'headless mode' documentation.

   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”
   • [claimed-docs] “Send a coding prompt to Grok Build (`grok-4.6`) and get a response.”
   • [claimed-docs] “Streaming outputs is **supported by all models with text output capability**”
   • [claimed-docs] “Structured Outputs lets the API return responses in a specific format, for example, a JSON object matching a schema you define”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.x.ai/openapi.json — contains "openapi" key”
   • [community] “still waiting for a proper gui for grok build - terminal is nice but codex desktop app is very useful”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Grok
   Perplexity—none0/10

   All MCP evidence describes Perplexity acting as an MCP *server* (Computer MCP server, Perplexity MCP Server) that other AI assistants can connect to, not Perplexity itself consuming external MCP servers as a client to gain new tools. There is no documentation of a settings/config surface where a user adds arbitrary third-party MCP servers for Perplexity to call.

   • [claimed-docs] “Through the Model Context Protocol, your MCP client can delegate complex, multi-step work to Computer and receive structured results.”
   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “**Connect to 400+ services** through a managed connector framework with one-click OAuth”
   • [claimed-docs] “Browser Control Computer includes a full cloud browser for tasks that go beyond search.”
   • [claimed-docs] “The Perplexity MCP Server enables AI assistants to access Perplexity's powerful search and reasoning capabilities directly within their work…”
   • [claimed-docs] “Give AI assistants the ability to complete real-world tasks using Perplexity Computer through the Model Context Protocol (MCP).”

   proof ↗⚑ flag

   Grok✓fullclaimed7/10

   xAI docs explicitly describe adding custom MCP connectors and tunneling a local MCP server so Grok can reach it and use its tools, alongside built-in OAuth connectors for other tools (grok-docs-2, grok-docs-3, grok-docs-38, grok-docs-19). Missing for 10: independent/hands-on confirmation that custom MCP tool-calling works reliably in practice, and more detail on protocol/version compatibility.

   • [claimed-docs] “Expose any internal API, database, or SaaS tool to Grok. Define your own tools with custom schemas and logic.”
   • [claimed-docs] “A tunneling service solves this by exposing your local server through a public URL that Grok can connect to.”
   • [claimed-docs] “When you add a custom MCP connector, Grok's servers need to reach your MCP server over the public internet.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Perplexity
   Perplexity✓fullprobed8/10

   Perplexity documents an official `pplx` CLI that returns structured JSON from the Search API, explicitly designed for shell pipelines, terminal work, and coding agents, with an independent probe confirming the docs page exists. Missing for 10: independent hands-on community review of the CLI itself (evidence is entirely first-party docs/probe) and detail on install/auth flows.

   • [claimed-docs] “The pplx CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and co…”
   • [claimed-docs] “The `pplx` CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and …”
   • [claimed-docs] “The `pplx` CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and …”
   • [claimed-docs] “The `pplx` CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and …”
   • [probe] “official CLI documented at https://docs.perplexity.ai/docs/cli/overview”

   proof ↗⚑ flag

   Grok~partialcommunity3/10

   There's no official CLI documentation for Grok, but a community comment references a terminal-based interface for 'Grok Build' ('terminal is nice but codex desktop app is very useful'), suggesting some CLI-like coding tool exists even though it isn't documented in the official docs pack. missing for 10: official CLI documentation/reference, installation instructions, and command examples confirming a first-party CLI product.

   • [community] “still waiting for a proper gui for grok build - terminal is nice but codex desktop app is very useful”
   • [claimed-docs] “Send a coding prompt to Grok Build (`grok-4.6`) and get a response.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Perplexity✓fullprobed9/10

   Perplexity publishes a documented public API (Agent API, Search API, embeddings) with an OpenAPI spec, supports structured output, model fallback, sandbox tool use, and profiles, plus a CLI and MCP integrations for programmatic/agentic access, confirmed by both docs and live probes returning valid OpenAPI/docs endpoints. Missing for 10: independent third-party developer corroboration of API reliability/robustness in production use.

   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer”
   • [claimed-docs] “Structured output makes the model return JSON that conforms to a schema you define, so you can deserialize it directly.”
   • [claimed-docs] “Model fallback enables specifying multiple models in a `models` array. The API tries each model in order until one succeeds, providing autom…”
   • [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage.”
   • [claimed-docs] “The pplx CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and co…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.perplexity.ai/llms.txt # Perplexity > Perplexity API documentation for building with the Agent API…”
   • [probe] “official CLI documented at https://docs.perplexity.ai/docs/cli/overview”

   proof ↗⚑ flag

   Grok✓fullprobed9/10

   xAI publishes a full public REST API with documented endpoints for text, image, video, tool use, structured outputs, and an OpenAPI spec confirmed live by probe, plus a quickstart guide, satisfying the AI-native/agentic driving story. missing for 10: independent third-party benchmarking of API reliability/completeness beyond xAI's own docs and anecdotal community chatter about tool-calling quirks.

   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”
   • [claimed-docs] “Send a coding prompt to Grok Build (`grok-4.6`) and get a response.”
   • [claimed-docs] “Expose any internal API, database, or SaaS tool to Grok. Define your own tools with custom schemas and logic.”
   • [claimed-docs] “Structured Outputs lets the API return responses in a specific format, for example, a JSON object matching a schema you define”
   • [claimed-docs] “Streaming outputs is **supported by all models with text output capability**”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.x.ai/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.x.ai/llms.txt # SpaceXAI API Documentation > Official SpaceXAI (xAI) developer documentation at ht…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Perplexity—none0/10

   The evidence pack covers API endpoints, MCP servers, CLI, and browser/app features, but contains no mention of API key scoping, granular permissions, or least-privilege credential issuance for agents. This is a fair capability to expect from an API platform, so absence of evidence means 'none' rather than 'na'.

   ⚑ flag

   Grok—none0/10

   The xAI API is a developer product with API keys, so scoped/least-privilege credential issuance is a fair capability to expect, but the evidence pack contains no mention of API key scopes, roles, granular permissions, or least-privilege credential controls — only OAuth-based connector authentication (grok-docs-19) for built-in tools, which is about connecting Grok to external services, not issuing scoped agent credentials.

   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “Expose any internal API, database, or SaaS tool to Grok. Define your own tools with custom schemas and logic.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Perplexity
   Perplexity~partialprobed4/10

   Perplexity documents a REST-based Agent API with an OpenAI-compatible endpoint and publishes an openapi.json spec, which supports SDK-style integration, but there is no explicit evidence of first-party official SDK libraries (e.g., a Perplexity Python/Node/Go client package) in the pack. missing for 10: explicit official SDK packages/libraries, language-specific SDK docs, independent developer corroboration of SDK usage.

   • [claimed-docs] “Unified access to open-weight models hosted by Perplexity through one OpenAI-compatible endpoint.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”

   proof ↗⚑ flag

   Grok~partialprobed3/10

   The evidence shows an official xAI developer API with a published OpenAPI spec, quickstart docs, and text-generation/tool-use guides (grok-docs-20, grok-docs-27, grok-probe-3), which implies programmatic access an AI-native builder could use, but none of the evidence explicitly names or documents an official SDK (e.g., Python/JS client library) as opposed to raw REST/OpenAPI usage. Missing for 10: explicit documentation of a first-party SDK package, install instructions, or code samples showing SDK usage, plus any independent/community confirmation of SDK quality or adoption.

   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”
   • [claimed-docs] “Send a coding prompt to Grok Build (`grok-4.6`) and get a response.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.x.ai/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.x.ai/llms.txt # SpaceXAI API Documentation > Official SpaceXAI (xAI) developer documentation at ht…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Perplexity—none0/10

   No evidence anywhere in the pack of a webhook subscription mechanism for events (e.g., completed jobs, search results, agent tasks); documentation covers APIs, CLI, MCP servers, and apps but no event-driven webhook system.

   ⚑ flag

   Grok—none0/10

   No evidence of any webhook subscription mechanism for Grok events; the docs describe connectors, tools, image/video generation, and inbound MCP tunneling, but nothing about outbound event notifications or webhook endpoints. Missing for 10: any webhook subscription API, event types, or delivery/registration mechanism.

   ⚑ flag

Agentic features

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

   weight 2 · round to Grok
   Perplexity~partialcommunity4/10

   Perplexity's Assistant (drafting emails, scheduling, booking) and the browser extension's 'Contextual Understanding' (answers tied to current page/domain) and 'Your Library' (curation of past discoveries) show the product surfacing suggestions tied to a user's own activity/context, but there's no explicit feature for uploading or connecting personal datasets (docs, CRM, files) and generating proactive analytical insights from them — the core product is web search/answers, not user-data analytics. missing for 10: dedicated personal-data ingestion/analysis capability, proactive insight-generation dashboards, independent evidence these 'insights' features work well in practice (community reports flag research features stalling and answer quality issues).

   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Your Library: More than search history, it's a curation of your discoveries.”
   • [claimed-docs] “Contextual Understanding: Get answers relevant to your current page or even specific to your current domain.”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok~partialcommunity6/10

   Grok's connectors (Gmail/Calendar, Google Drive, Microsoft Teams, Salesforce, custom APIs/MCP) let it read and act on a user's own data inside the chat, and features like Realtime Multi-agent Research suggest Grok can analyze and synthesize that data into insights. However, the evidence is mostly first-party docs describing data access rather than concrete examples of proactive 'insights and suggestions,' and one hands-on report notes Grok has 'real trouble with agentic tool calling,' undercutting confidence in reliable in-context analysis. Missing for 10: independent hands-on demonstration of Grok surfacing unprompted insights/suggestions from connected data, and confirmation that tool-calling reliability issues don't undermine this in practice.

   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “Search emails using Gmail search operators (`from:`, `to:`, `subject:`, `newer_than:`, `has:attachment`, etc.).”
   • [claimed-docs] “The Google Drive connector lets Grok search, read, and manage files in your Google Drive.”
   • [claimed-docs] “Search across channels and chats, read messages, send new messages, reply to threads, and create chats — all without leaving Grok.”
   • [claimed-docs] “Realtime Multi-agent Research enables Grok to orchestrate multiple AI agents that work together in real time to perform deep, multi-step res…”
   • [community] “I experimented with Grok 4 for openclaw... It was more verbally fluid than 5.5, but had real trouble with agentic tool calling - the model f…”

   proof ↗⚑ flag

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

   weight 2 · round to Grok
   Perplexity—none0/10

   The evidence describes on-demand features (Assistant drafting emails/booking, Computer/MCP multi-step delegation, Agent API) that execute when invoked, but nothing documents scheduled, recurring, or persistent background automations that run autonomously without a user actively initiating each session. Missing for 10: any documented scheduling/trigger mechanism, recurring task execution, or evidence of an automation running unattended over time.

   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “Browser Control Computer includes a full cloud browser for tasks that go beyond search.”
   • [claimed-docs] “Give AI assistants the ability to complete real-world tasks using Perplexity Computer through the Model Context Protocol (MCP).”

   proof ↗⚑ flag

   Grok~partialclaimed4/10

   Grok Bot is described as an AI teammate running on a 'persistent cloud computer' and Grok supports multi-agent orchestration for research tasks, hinting at some background/autonomous agent capability, but there is no documentation of scheduling, triggers, or recurring/timed automation setup. Missing for 10: explicit scheduling/trigger mechanism, details on how automations run without user prompting, and independent confirmation of autonomous background execution.

   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Realtime Multi-agent Research enables Grok to orchestrate multiple AI agents that work together in real time to perform deep, multi-step res…”

   proof ↗⚑ flag

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

   weight 3 · round to Grok
   Perplexity!disputedcontradicted5/10

   Perplexity ships a built-in 'Assistant' and 'Computer' agent that can draft emails, book reservations, browse the web, run code, and connect to 400+ services (perplexity-docs-9, -17, -19, -29, -30, -38), which is a genuine in-product delegation capability. However, hands-on community reports say the Computer/agentic research feature 'often fails to trigger via the UI, and when it does work, sessions frequently stall without returning an answer' (perplexity-comm-7), directly contradicting the vendor's smooth-delegation claims. Missing for 10: independent corroboration that the assistant reliably completes delegated multi-step tasks, and resolution of the reported stalling/failure-to-trigger issue.

   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “**Connect to 400+ services** through a managed connector framework with one-click OAuth”
   • [claimed-docs] “Browser Control Computer includes a full cloud browser for tasks that go beyond search.”
   • [claimed-docs] “When a task requires interacting with a website, filling forms, or accessing login-gated content, Computer launches a browser session automa…”
   • [claimed-docs] “Give AI assistants the ability to complete real-world tasks using Perplexity Computer through the Model Context Protocol (MCP).”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok!disputedcontradicted6/10

   xAI docs describe strong built-in agentic delegation — Grok Bot hands work to 'AI teammates on a persistent cloud computer,' Realtime Multi-agent Research orchestrates multiple agents for research tasks, and connectors let Grok act on email/calendar/Salesforce from chat (grok-docs-15, grok-docs-26, grok-docs-11, grok-docs-16, grok-docs-19). However, hands-on community testing directly contradicts smooth agentic delegation: a user reports Grok 'had real trouble with agentic tool calling - the model felt like it hadn't been trained to think of tool calling as one of its primary modalities' (grok-comm-6), and another notes the lack of a proper GUI for Grok Build limiting usability (grok-comm-7). Missing for 10: independent verification that Grok Bot/multi-agent research reliably completes delegated tasks end-to-end, and resolution of the reported tool-calling weakness.

   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Realtime Multi-agent Research enables Grok to orchestrate multiple AI agents that work together in real time to perform deep, multi-step res…”
   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”
   • [claimed-docs] “Create new records - Add Leads, Opportunities, Accounts, Cases, or records on custom objects directly from chat.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [community] “I experimented with Grok 4 for openclaw... It was more verbally fluid than 5.5, but had real trouble with agentic tool calling - the model f…”
   • [community] “still waiting for a proper gui for grok build - terminal is nice but codex desktop app is very useful”

   proof ↗⚑ flag

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

   weight 2 · round to Grok
   Perplexity!disputedcontradicted6/10

   Perplexity's core product is a natural-language chat/search interface (voice and text queries, cited answers) and its 'Assistant'/Computer agent claims to handle draft emails, scheduling, and multi-step web tasks purely via NL commands. However, hands-on community reports say the agentic 'Computer' research feature frequently fails to trigger via the UI and stalls without returning results, directly contradicting the docs' claims of reliable NL-driven task execution. missing for 10: independent verification that the Assistant reliably completes booking/scheduling tasks, and resolution of the reported reliability failures.

   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “**Connect to 400+ services** through a managed connector framework with one-click OAuth”
   • [claimed-docs] “· Voice: Instant, up-to-date answers whether you type or say it.”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok~partialcommunity6/10

   Grok's docs describe a chat/voice interface where natural-language input drives text generation, image/video creation, and connector actions like creating Salesforce records or searching email 'directly from chat' (grok-docs-11, grok-docs-16, grok-docs-35, grok-docs-40), which is core evidence for NL-command operation. However, hands-on community testing reports real trouble with agentic tool calling, saying the model 'hadn't been trained to think of tool calling as one of its primary modalities' (grok-comm-6), which tempers confidence that NL commands reliably trigger tool/connector actions. Missing for 10: independent benchmarks or user reports specifically confirming reliable NL-to-action execution across the built-in connectors, and no clear resolution of the tool-calling reliability concern.

   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”
   • [claimed-docs] “Create new records - Add Leads, Opportunities, Accounts, Cases, or records on custom objects directly from chat.”
   • [claimed-docs] “Search emails using Gmail search operators (`from:`, `to:`, `subject:`, `newer_than:`, `has:attachment`, etc.).”
   • [claimed-docs] “Talk to Grok hands-free with voice.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [community] “I experimented with Grok 4 for openclaw... It was more verbally fluid than 5.5, but had real trouble with agentic tool calling - the model f…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Perplexity~partialprobed4/10

   Perplexity publishes a machine-readable OpenAPI spec (openapi.json) and structured API docs (quickstart, building-agents guides) that would typically power an interactive reference, but the evidence pack never explicitly shows a 'try it' playground or runnable code examples within the docs UI. missing for 10: explicit interactive 'try it now' console screenshots/docs, confirmation of runnable code snippets executed in-browser, independent user report of using the interactive reference.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.perplexity.ai/llms.txt # Perplexity > Perplexity API documentation for building with the Agent API…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.perplexity.ai/docs/getting-started/overview.md > ## Documentation Index > Fetch the complete documen…”

   proof ↗⚑ flag

   Grok~partialprobed4/10

   xAI publishes machine-readable docs (llms.txt, openapi.json) and a quickstart with example prompts/code, showing a structured API reference exists, but there is no evidence of an interactive 'try it now' console or in-browser runnable examples typical of tools like Swagger UI or Postman-style explorers. Missing for 10: interactive in-browser code execution/sandbox, live request/response try-it widget, independent confirmation of an interactive reference UI.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.x.ai/llms.txt # SpaceXAI API Documentation > Official SpaceXAI (xAI) developer documentation at ht…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.x.ai/openapi.json — contains "openapi" key”
   • [claimed-docs] “Send a coding prompt to Grok Build (`grok-4.6`) and get a response.”
   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Perplexity✓fullprobed9/10

   A probe confirms a live, machine-readable OpenAPI spec at https://docs.perplexity.ai/openapi.json returning HTTP 200 with an 'openapi' key, alongside an llms.txt documentation index, directly satisfying the story. Missing for 10: independent/community confirmation of the spec's completeness or usage in the wild.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.perplexity.ai/llms.txt # Perplexity > Perplexity API documentation for building with the Agent API…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.perplexity.ai/docs/getting-started/overview.md > ## Documentation Index > Fetch the complete documen…”

   proof ↗⚑ flag

   Grok✓fullprobed9/10

   A direct probe confirms https://docs.x.ai/openapi.json returns HTTP 200 and contains an 'openapi' key, i.e., a downloadable, machine-readable OpenAPI spec for the xAI API, and this is corroborated by extensive first-party API docs describing the full endpoint surface (text, images, video, tools). Missing for 10: independent/community confirmation that developers actually consume this spec (e.g., via SDK codegen) beyond the automated probe.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.x.ai/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.x.ai/llms.txt # SpaceXAI API Documentation > Official SpaceXAI (xAI) developer documentation at ht…”
   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Perplexity—none0/10

   Evidence only shows a code-execution sandbox (isolated Linux container) used by Perplexity's agent/Computer tools for running code within an answer, not a separate staging/test environment that lets a developer exercise the Perplexity API or product without touching live production data or billing. No mention of test API keys, staging endpoints, or a sandbox mode for the platform itself.

   • [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer”
   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “Computer can: **Search and browse** the web for real-time information, including login-gated pages * **Write and execute code** in an intera…”

   proof ↗⚑ flag

   Grok—none0/10

   No evidence of a sandbox/staging environment or test mode that isolates from production data; docs cover connectors, tunneling for custom tools, and general product features but nothing about a dedicated sandbox for testing without touching production data. missing for 10: sandbox/test environment documentation, data isolation guarantees, staging API keys or environments.

   ⚑ flag

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

   weight 2 · round drawn
   Perplexity—none0/10

   Evidence shows Perplexity has an API with an OpenAPI spec and 'versioned' profiles for agent configurations, but nothing documents API version numbering or a deprecation/sunset policy for endpoints or models. Missing for 10: explicit API versioning scheme (e.g., v1/v2 paths), documented deprecation/sunset timeline, and any changelog or migration guide referenced in the evidence pack.

   • [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.perplexity.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

   Grok—none0/10

   The evidence shows model version slugs (grok-4.6, grok-4.5) and an OpenAPI spec, but no documentation of a formal deprecation policy, sunset timelines, or versioning guarantees for the API. Release notes describe new features and model updates but never state how/when older model versions are retired.

   • [claimed-docs] “Grok 4.6, SpaceXAI's frontier model for coding, agentic tasks, and knowledge work, is now available on the xAI API. It has a 500k context wi…”
   • [claimed-docs] “grok-4.6` and `grok-4.5` support the `reasoning_effort` parameter, which controls how much effort the model spends thinking before respondin…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.x.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

Agent mode

1. power-userDelegate a multi-step task that the assistant works on autonomously in the background and returns for my review

   weight 3 · round to Grok
   Perplexity!disputedcontradicted5/10

   Perplexity's 'Computer' (Labs/Assistant) is documented as an autonomous background agent that can browse the web, execute code, use 400+ connectors, and complete tasks like drafting emails or booking reservations, returning structured results — matching the delegate-and-review story (perplexity-docs-9,10,17-19,29,30,38). However, a hands-on community report says the Computer/research feature 'often fails to trigger via the UI, and when it does work, sessions frequently stall without returning an answer,' directly contradicting reliable autonomous completion (perplexity-comm-7). missing for 10: independent corroboration that Computer reliably completes tasks and returns results, resolution of the reported stalling/failure-to-trigger issue.

   • [claimed-docs] “Through the Model Context Protocol, your MCP client can delegate complex, multi-step work to Computer and receive structured results.”
   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Perplexity Labs: Bring your reports and projects to life faster than ever before.”
   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “**Connect to 400+ services** through a managed connector framework with one-click OAuth”
   • [claimed-docs] “Browser Control Computer includes a full cloud browser for tasks that go beyond search.”
   • [claimed-docs] “When a task requires interacting with a website, filling forms, or accessing login-gated content, Computer launches a browser session automa…”
   • [claimed-docs] “Give AI assistants the ability to complete real-world tasks using Perplexity Computer through the Model Context Protocol (MCP).”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok~partialcommunity6/10

   Docs describe 'Grok Bot' as handing 'real work to AI teammates on a persistent cloud computer' and a 'Realtime Multi-agent Research' feature that orchestrates multi-step research autonomously, directly matching the story's core idea of background delegation and review. However, evidence is vendor-doc only with no independent confirmation of the async review workflow (notifications, task state, resuming), and community feedback (grok-comm-6) notes real trouble with agentic tool calling, suggesting reliability caveats. Missing for 10: independent hands-on validation of the background-task lifecycle, detail on how results are surfaced for review, and confirmation tool-calling reliability issues don't undermine multi-step autonomy.

   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Realtime Multi-agent Research enables Grok to orchestrate multiple AI agents that work together in real time to perform deep, multi-step res…”
   • [community] “I experimented with Grok 4 for openclaw... It was more verbally fluid than 5.5, but had real trouble with agentic tool calling - the model f…”
   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”

   proof ↗⚑ flag

2. power-userHave the assistant operate a web browser on my behalf to research and complete tasks on websites

   weight 3 · round to Perplexity
   Perplexity!disputedcontradicted5/10

   Perplexity documents a 'Computer' agent with a full cloud browser that can search, browse, fill forms, and access login-gated pages, launched automatically for such tasks and accessible via MCP (perplexity-docs-17, -29, -30, -38) — squarely matching the story. However, hands-on community reporting says this same 'Computer' feature 'often fails to trigger via the UI, and when it does work, sessions frequently stall without returning an answer' (perplexity-comm-7), directly contradicting reliable operation. missing for 10: independent corroboration that browser automation completes tasks reliably, and no rebuttal to the stall/failure reports.

   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “Browser Control Computer includes a full cloud browser for tasks that go beyond search.”
   • [claimed-docs] “When a task requires interacting with a website, filling forms, or accessing login-gated content, Computer launches a browser session automa…”
   • [claimed-docs] “Give AI assistants the ability to complete real-world tasks using Perplexity Computer through the Model Context Protocol (MCP).”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok—none0/10

   The evidence shows connectors for APIs, email, calendar, Salesforce, and a vague 'Grok Bot' cloud computer teammate, but nothing documents Grok actually driving a web browser to navigate sites or complete tasks (no browsing/computer-use agent feature is described). Multi-agent research (grok-docs-26) is about research orchestration, not website interaction, so this applicable-but-unevidenced capability is 'none'.

   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “Realtime Multi-agent Research enables Grok to orchestrate multiple AI agents that work together in real time to perform deep, multi-step res…”

   proof ↗⚑ flag

3. power-userLet the assistant see and operate applications on my computer to complete work

   weight 2 · round to Perplexity
   Perplexity!disputedcontradicted4/10

   Perplexity's 'Computer' (via MCP) and Assistant app claim to browse the web, execute code in a sandbox, connect to 400+ services, and perform tasks like booking/scheduling — a form of 'operate applications' — but this is a cloud browser/sandbox, not literal control of apps on the user's own computer, and community hands-on reports say the Computer research feature 'often fails to trigger via the UI, and when it does work, sessions frequently stall without returning an answer.' This directly contradicts the vendor's claims of reliable task completion. missing for 10: evidence of actually operating local desktop applications (not just cloud browser/sandbox), reliability data contradicting the stalling reports, independent success case studies.

   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “Computer can: **Search and browse** the web for real-time information, including login-gated pages * **Write and execute code** in an intera…”
   • [claimed-docs] “**Connect to 400+ services** through a managed connector framework with one-click OAuth”
   • [claimed-docs] “Browser Control Computer includes a full cloud browser for tasks that go beyond search.”
   • [claimed-docs] “When a task requires interacting with a website, filling forms, or accessing login-gated content, Computer launches a browser session automa…”
   • [claimed-docs] “Give AI assistants the ability to complete real-world tasks using Perplexity Computer through the Model Context Protocol (MCP).”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok—none0/10

   Grok offers connectors (Gmail, Drive, Teams, Salesforce, custom MCP) and a 'Grok Bot' that operates on a persistent *cloud* computer, but there is no evidence of Grok seeing or controlling applications running on the user's own local machine/desktop (e.g., screen/GUI control akin to computer-use agents). Missing for 10: any documented local-computer screen/GUI control, first-party or hands-on evidence of operating a user's own desktop apps.

   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “When you add a custom MCP connector, Grok's servers need to reach your MCP server over the public internet.”

   proof ↗⚑ flag

Tasks

1. power-userSchedule recurring or one-off tasks that run automatically and come back to me with results

   weight 2 · round drawn
   Perplexity—none0/10

   Evidence shows search, Q&A, Computer/MCP agent capabilities, and an Assistant that can draft emails or book reservations, but nothing describes a mechanism for scheduling recurring or one-off tasks that run automatically in the background and return results later. Community evidence even notes the 'Computer' research feature often fails to trigger or stalls without returning an answer, but there's no documented scheduling/task-runner feature at all.

   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “Browser Control Computer includes a full cloud browser for tasks that go beyond search.”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok—none0/10

   The evidence pack shows connectors, tool integrations, and a 'Grok Bot' persistent cloud agent for handing off work, but no mention of scheduling recurring or one-off tasks that run automatically and report back results.

   ⚑ flag

Apps

1. power-userUse an official desktop app with OS-level shortcuts and access to what is on my screen

   weight 2 · round drawn
   Perplexity—none0/10

   The evidence pack only documents Perplexity's mobile apps (iOS/Android), a Chrome browser extension, a CLI, and MCP/API integrations — none describe an official desktop app with OS-level keyboard shortcuts or screen-content access.

   • [claimed-docs] “Perplexity Pro Search & Deep Research: Guided AI search for deeper exploration.”
   • [claimed-docs] “Instant Page Summaries: Make sense of any article or webpage at a glance.”
   • [claimed-docs] “This free app syncs across devices and leverages the power of the top AI models from OpenAI, Anthropic, Meta, and more.”
   • [claimed-docs] “The pplx CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and co…”

   proof ↗⚑ flag

   Grok—none0/10

   The evidence pack shows only cross-platform sign-in sync and hands-free voice, but no mention of an official desktop app with OS-level shortcuts or screen-reading/access capability; a community comment even notes the lack of a proper GUI for Grok's coding product ('still waiting for a proper gui for grok build ... codex desktop app is very useful'), suggesting no such desktop tool exists.

   • [claimed-docs] “Sign in once and your conversations, settings, and subscription stay in sync across every platform.”
   • [claimed-docs] “Talk to Grok hands-free with voice.”
   • [community] “still waiting for a proper gui for grok build - terminal is nice but codex desktop app is very useful”

   proof ↗⚑ flag

2. knowledge-workerUse full-featured official mobile apps for iOS and Android

   weight 2 · round to Perplexity
   Perplexity✓fullclaimed8/10

   Perplexity has official iOS and Android apps (App Store and Play Store listings) with a broad feature set: Pro Search/Deep Research, Assistant tasks, voice, citations, library/history sync across devices, and cross-model access — indicating full-featured rather than bare-bones apps. Missing for 10: independent hands-on app-store review/rating evidence and no direct community commentary specifically on mobile app quality (community feedback cited is about the web/desktop product and Computer feature, not mobile apps specifically).

   • [claimed-docs] “Perplexity Pro Search & Deep Research: Guided AI search for deeper exploration.”
   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Perplexity Labs: Bring your reports and projects to life faster than ever before.”
   • [claimed-docs] “Voice: Instant, up-to-date answers whether you type or say it.”
   • [claimed-docs] “Trust Built In: Cited sources for every answer.”
   • [claimed-docs] “Your Library: More than search history, it's a curation of your discoveries.”
   • [claimed-docs] “Discover: Learn new things from the community.”
   • [claimed-docs] “This free app syncs across devices and leverages the power of the top AI models from OpenAI, Anthropic, Meta, and more.”
   • [claimed-docs] “Cut through the clutter and get straight to credible, up-to-date answers.”
   • [claimed-docs] “Thread Follow-Ups: Keep the conversation going for a deeper understanding.”

   proof ↗⚑ flag

   Grok~partialclaimed4/10

   Docs mention voice mode ('Talk to Grok hands-free with voice') and cross-platform sync of conversations/settings/subscriptions, implying mobile app support, but there is no explicit confirmation of dedicated full-featured iOS and Android apps, no app-store links, and no community/hands-on feedback about mobile app quality or feature parity with desktop/web. Missing for 10: explicit iOS/Android app documentation, feature-parity details, and independent user reviews of the mobile apps themselves.

   • [claimed-docs] “Talk to Grok hands-free with voice.”
   • [claimed-docs] “Sign in once and your conversations, settings, and subscription stay in sync across every platform.”

   proof ↗⚑ flag

Custom bots

1. power-userBuild and share custom assistants with their own instructions and knowledge

   weight 2 · round drawn
   Perplexity—none0/10

   The evidence pack covers Perplexity's search products, apps, CLI, MCP servers, and Agent API (including 'profiles' as reusable API configs), but nothing describes a user-facing feature for building a custom assistant with its own persistent instructions plus an attached knowledge base that can be shared with others (e.g., a Spaces/custom-GPT-like capability).

   ⚑ flag

   Grok—none0/10

   The evidence pack covers connectors, tool integrations, MCP, image/video generation, and enterprise features, but there is no mention of a feature to create and share custom assistants/personas with their own instructions and knowledge base (akin to OpenAI's GPTs or Claude Projects).

   ⚑ flag

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

   weight 2 · round to Grok
   Perplexity—none0/10

   No evidence of a batch/bulk API, batch endpoint, or multi-item processing mode; the CLI and Agent API are described as single-call/pipeline-oriented tools that a user could script externally, but Perplexity itself does not document any bulk-operation capability.

   • [claimed-docs] “The `pplx` CLI returns structured JSON from the Perplexity Search API, making it useful for shell pipelines, interactive terminal work, and …”
   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer”

   proof ↗⚑ flag

   Grok~partialclaimed4/10

   The docs mention batch generation of multiple images and support for up to 5 source images in a single edit, which is a narrow form of bulk operation, but there's no evidence of general-purpose bulk operations (e.g., bulk file processing, bulk record updates, batch text API) across many items or arbitrary data types. Missing for 10: a true batch/bulk API for text or file processing, bulk actions on connector data (e.g., mass email/calendar updates), and independent confirmation that these batch features work reliably at scale.

   • [claimed-docs] “Generate images from text prompts with Grok Imagine models. The API supports batch generation of multiple images, and control over aspect ra…”
   • [claimed-docs] “Image editing now accepts up to 5 source images per request (was 3).”
   • [claimed-docs] “Use up to five source images for a single image edit.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Perplexity—none0/10

   No evidence of a rules/trigger/automation engine (event-based conditions triggering actions) anywhere in the docs — Perplexity's evidence covers search, chat, APIs, MCP/Computer agent tasks, and CLI, but nothing about defining persistent rules that fire automatically on events.

   ⚑ flag

   Grok—none0/10

   Grok's docs describe connectors, tool integrations, and a persistent 'Grok Bot' cloud agent, but nothing describes user-defined rules that trigger actions automatically on external events (e.g., webhooks, triggers, if-this-then-that automations, or scheduled event listeners). The axis is plausible for an AI-native product with tool/connector access, so this is 'none' rather than 'na'.

   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “Expose any internal API, database, or SaaS tool to Grok. Define your own tools with custom schemas and logic.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Perplexity—none0/10

   No evidence of scheduling, cron-like triggers, or recurring workflow automation anywhere in the docs, apps, or API references; the Agent API, CLI, MCP servers, and assistant features described are all single-invocation or on-demand tools with no persistent job scheduler.

   ⚑ flag

   Grok—none0/10

   No evidence of scheduling, cron-like recurrence, or persistent recurring workflow features anywhere in the docs; Grok Bot ('persistent cloud computer') and connectors describe on-demand agents/tools, not scheduled recurring jobs.

   ⚑ flag

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

   weight 1 · round to Perplexity
   Perplexity~partialclaimed3/10

   The Agent API's 'profiles' feature is described as a reusable, versioned configuration that can be saved and managed, offering a thin sliver of version control for automation configs, but there is no documented review workflow or rollback mechanism for automations. missing for 10: rollback/restore functionality, review/diff UI, versioning for Computer/MCP-based automations, evidence of actual usage beyond a single doc line.

   • [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage.”

   proof ↗⚑ flag

   Grok—none0/10

   No evidence describes any versioning, review, diffing, or rollback mechanism for automations/agents/connectors built with Grok; the docs cover connectors, generation capabilities, and workspace management but nothing about tracking or reverting automation history.

   ⚑ flag

Connectors

1. power-userBrowse a directory of third-party apps and connectors and add them to the assistant

   weight 2 · round to Grok
   Perplexity~partialclaimed4/10

   Docs mention Perplexity's Computer feature can 'connect to 400+ services through a managed connector framework with one-click OAuth,' implying a connector catalog exists, but there is no evidence of an actual browsable directory UI, categories, or user-facing app marketplace, and no independent/hands-on confirmation of this experience. Missing for 10: dedicated connector/app directory UI evidence, list of example connectors, independent user reports of browsing/adding connectors.

   • [claimed-docs] “**Connect to 400+ services** through a managed connector framework with one-click OAuth”
   • [claimed-docs] “Give AI assistants the ability to complete real-world tasks using Perplexity Computer through the Model Context Protocol (MCP).”

   proof ↗⚑ flag

   Grok~partialclaimed6/10

   Docs show Grok exposes a set of built-in, OAuth-authenticated connectors (Salesforce, Gmail, Google Calendar, Google Drive, Microsoft Teams) plus custom/MCP connectors that a user can add to reach external tools (grok-docs-16,19,35,36,37,2,3). This matches the 'add third-party apps/connectors' part of the story, but there's no explicit evidence of a browsable directory/marketplace UI, ratings, or a curated catalog page for discovering connectors. missing for 10: a documented directory/marketplace UI for browsing connectors, independent user confirmation of the browse experience.

   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “Create new records - Add Leads, Opportunities, Accounts, Cases, or records on custom objects directly from chat.”
   • [claimed-docs] “Search emails using Gmail search operators (`from:`, `to:`, `subject:`, `newer_than:`, `has:attachment`, etc.).”
   • [claimed-docs] “The Google Drive connector lets Grok search, read, and manage files in your Google Drive.”
   • [claimed-docs] “Search across channels and chats, read messages, send new messages, reply to threads, and create chats — all without leaving Grok.”
   • [claimed-docs] “Expose any internal API, database, or SaaS tool to Grok. Define your own tools with custom schemas and logic.”
   • [claimed-docs] “A tunneling service solves this by exposing your local server through a public URL that Grok can connect to.”

   proof ↗⚑ flag

2. knowledge-workerConnect my cloud drive, email, and calendar so the assistant can search and use them in answers

   weight 3 · round to Grok
   Perplexity~partialcommunity5/10

   Perplexity's Computer/MCP docs claim a 'managed connector framework' connecting to 400+ services via one-click OAuth, and the Assistant feature claims it can draft emails and schedule appointments, which implies email/calendar integration, but no evidence names specific connectors like Google Drive, Gmail, or Google/Outlook Calendar, nor shows search results being grounded in those personal sources. Community reports also note the 'Computer' feature (where this connector framework lives) often fails to trigger via the UI and stalls without returning an answer, raising doubts about reliability. Missing for 10: named cloud-drive/email/calendar connector examples, documentation of how connected-source data is surfaced in answers, and independent confirmation the connector framework works reliably.

   • [claimed-docs] “**Connect to 400+ services** through a managed connector framework with one-click OAuth”
   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “· Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok✓fullclaimed8/10

   Grok docs explicitly describe built-in OAuth connectors for Gmail, Google Calendar, and Google Drive that let it search emails, read files, and manage calendar items right inside chat, plus a broader connectors framework for other SaaS tools. This directly matches the story of connecting cloud drive, email, and calendar for search/use in answers. Missing for 10: independent/hands-on confirmation of these specific connectors working reliably in practice (community evidence largely covers coding/chat quality, not connector behavior).

   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “Search emails using Gmail search operators (`from:`, `to:`, `subject:`, `newer_than:`, `has:attachment`, etc.).”
   • [claimed-docs] “The Google Drive connector lets Grok search, read, and manage files in your Google Drive.”

   proof ↗⚑ flag

Analysis

1. power-userHave the assistant write and run code on my data to produce charts, computed answers, and downloadable files

   weight 3 · round to Perplexity
   Perplexity!disputedcontradicted4/10

   Perplexity documents a code-execution sandbox (Computer MCP / Agent API 'sandbox' tool) that can write and run Python/Node code and return outputs, and Labs is pitched for 'reports and projects,' suggesting some support for computing answers/files from data. However, hands-on community reporting says the 'Computer' feature 'often fails to trigger via the UI, and when it does work, sessions frequently stall without returning an answer,' directly contradicting reliable delivery of this workflow. missing for 10: explicit evidence of chart generation, working with user-uploaded datasets, downloadable file outputs, and independent confirmation the sandbox reliably works in the consumer product.

   • [claimed-docs] “Computer can: Search and browse the web for real-time information, including login-gated pages; Write and execute code in an interactive Lin…”
   • [claimed-docs] “Computer can: **Search and browse** the web for real-time information, including login-gated pages * **Write and execute code** in an intera…”
   • [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer”
   • [claimed-docs] “Perplexity Labs: Bring your reports and projects to life faster than ever before.”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”

   proof ↗⚑ flag

   Grok—none0/10

   The evidence describes Grok's coding assistant (Grok Build), connectors for email/calendar/files, image/video generation, and multi-agent research, but nothing documents a code-interpreter style capability where Grok writes and executes code against user-supplied data to produce charts, computed answers, or downloadable output files. Community comments discuss coding quality and agentic tool-calling issues but not this specific data-analysis/file-output workflow.

   • [claimed-docs] “Send a coding prompt to Grok Build (`grok-4.6`) and get a response.”
   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”
   • [claimed-docs] “The Google Drive connector lets Grok search, read, and manage files in your Google Drive.”
   • [community] “I experimented with Grok 4 for openclaw... It was more verbally fluid than 5.5, but had real trouble with agentic tool calling - the model f…”

   proof ↗⚑ flag

Artifacts

1. knowledge-workerHave the assistant create and iteratively edit documents, presentations, and other files I can export

   weight 2 · round to Perplexity
   Perplexity~partialclaimed3/10

   Perplexity Labs is described as helping 'bring your reports and projects to life,' hinting at document/report generation, but the evidence pack gives no detail on iterative editing, presentation creation, or exporting files to common formats. Missing for 10: iterative document/presentation editing workflow, export format support (PDF/DOCX/PPT), and any independent confirmation these outputs are usable/editable.

   • [claimed-docs] “Perplexity Labs: Bring your reports and projects to life faster than ever before.”

   proof ↗⚑ flag

   Grok—none0/10

   The evidence pack shows Grok connectors for reading/searching Google Drive, Gmail, Calendar, and Salesforce, plus image/video generation and coding via Grok Build, but nothing describes a document/presentation authoring or iterative-editing feature (e.g., a canvas-style doc editor) with export to file formats like Word/PowerPoint/PDF.

   • [claimed-docs] “The Google Drive connector lets Grok search, read, and manage files in your Google Drive.”
   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Send a coding prompt to Grok Build (`grok-4.6`) and get a response.”
   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”

   proof ↗⚑ flag

Files

1. knowledge-workerUpload documents, spreadsheets, and PDFs and get accurate analysis of their contents

   weight 3 · round to Grok
   Perplexity—none0/10

   The evidence pack contains no mention of document, spreadsheet, or PDF upload/analysis features anywhere in Perplexity's docs, API, CLI, MCP server, or app store listings — coverage focuses on web search, citations, sandboxed code execution, and browser automation. Missing for 10: any documentation of file/PDF/spreadsheet upload, parsing, or analysis capability, and any user or hands-on evidence of accurate document Q&A.

   ⚑ flag

   Grok~partialclaimed5/10

   Docs show Grok can ingest images and connect to Google Drive/Gmail to search and read files, and boasts a 500k context window for knowledge work, implying some document handling, but there is no explicit documentation of native PDF or spreadsheet upload/parsing in the core chat UI, nor any accuracy benchmarks or hands-on validation of document analysis. Missing for 10: explicit PDF/spreadsheet upload feature docs, accuracy testing/validation, independent user reports confirming reliable document analysis.

   • [claimed-docs] “Grok 4.6, SpaceXAI's frontier model for coding, agentic tasks, and knowledge work, is now available on the xAI API. It has a 500k context wi…”
   • [claimed-docs] “Connect your tools so Grok can reach your email, files, and calendar right inside a chat.”
   • [claimed-docs] “Some models allow images in the input. The model will consider the image context when generating the response.”
   • [claimed-docs] “The Google Drive connector lets Grok search, read, and manage files in your Google Drive.”

   proof ↗⚑ flag

Memory

1. power-userHave the assistant remember relevant context from previous chats and apply it in new conversations

   weight 3 · round drawn
   Perplexity—none0/10

   Evidence shows only within-conversation context ('conversation context across turns', 'Thread Follow-Ups') and a searchable history/library, but no documented feature where the assistant recalls or applies context from previous separate chats into new conversations. Missing for 10: any explicit cross-session memory feature, opt-in/opt-out memory controls, or evidence of persisted user facts being reused in new threads.

   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [claimed-docs] “Thread Follow-Ups: Keep the conversation going for a deeper understanding.”
   • [claimed-docs] “Your Library: More than search history, it's a curation of your discoveries.”

   proof ↗⚑ flag

   Grok—none0/10

   The evidence pack shows conversation storage (grok-docs-21) and cross-device sync of conversations/settings (grok-docs-41), but nothing describing a memory feature that recalls relevant context from past chats and applies it to new, unrelated conversations. No docs or community reports confirm persistent cross-chat memory recall.

   ⚑ flag

2. power-userSet persistent custom instructions and preferences that shape every response

   weight 1 · round to Perplexity
   Perplexity~partialclaimed3/10

   The only related evidence is the Agent API 'profiles' feature (a reusable, versioned configuration you save and manage), which could function as persistent settings shaping responses, but this is a developer/API concept, not documented as a consumer-facing custom-instructions or persona feature. Missing for 10: explicit evidence of user-facing custom instructions/preferences in the consumer app, confirmation that profiles persist across all conversations/responses, and independent corroboration of this working as claimed.

   • [claimed-docs] “A profile is a reusable, versioned configuration that you save and manage.”
   • [claimed-docs] “Your Library: More than search history, it's a curation of your discoveries.”

   proof ↗⚑ flag

   Grok—none0/10

   No evidence pack items describe a settings feature for persistent custom instructions or personality/preference profiles that shape all future responses; only per-request system prompts, connectors, and server-side storage of past prompts/responses are documented.

   ⚑ flag

Projects

1. knowledge-workerOrganize related chats and files into a project or space that shares context and instructions

   weight 2 · round drawn
   Perplexity—none0/10

   The evidence pack mentions a 'Library' for curating search history but nothing about a 'Spaces'/'Projects' feature that groups chats and files with shared context or custom instructions, which is the core of this story. Missing for 10: any mention of collections/spaces, file upload grounding within a project, or persistent custom instructions per project.

   ⚑ flag

   Grok—none0/10

   The evidence describes team 'workspaces' for licensing, SSO, and sharing conversations among teammates, plus connectors for external tools, but there is no mention of a project/space construct that groups related chats and files together with shared custom instructions or context, unlike dedicated 'Projects' features in other chat products.

   • [claimed-docs] “In your team workspace, enjoy enterprise-grade privacy protections... Additionally, unlock the full capabilities of SuperGrok, including hig…”
   • [claimed-docs] “Share conversations only with team members who have active licenses.”
   • [claimed-docs] “Switch between workspaces to access team-specific features and ensure your conversations are protected under business plan terms.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”

   proof ↗⚑ flag

Images

1. knowledge-workerGenerate and edit images from natural-language prompts

   weight 2 · round to Grok
   Perplexity—none0/10

   The evidence pack shows Perplexity is focused on web-grounded search, citations, code sandboxes, MCP/CLI integrations, and browser automation via 'Computer,' but contains no mention of image generation or editing capabilities from natural-language prompts anywhere in the docs, app store listings, or community reports.

   ⚑ flag

   Grok✓fullclaimed9/10

   Grok Imagine and the API both explicitly support text-to-image generation and image editing (including multi-image edits up to 5 sources, aspect ratio control) with docs describing prompt-driven creation and editing directly relevant to knowledge-worker use. Missing for 10: independent hands-on community corroboration specifically of image generation/editing quality (community evidence pack focuses on coding/text/voice, not images).

   • [claimed-docs] “Create images and video with Grok Imagine.”
   • [claimed-docs] “Generate images from text prompts with Grok Imagine models. The API supports batch generation of multiple images, and control over aspect ra…”
   • [claimed-docs] “Edit an existing image by providing a source image along with your prompt. The model understands the image content and applies your requeste…”
   • [claimed-docs] “Use up to five source images for a single image edit.”
   • [claimed-docs] “Image editing now accepts up to 5 source images per request (was 3).”
   • [claimed-docs] “New aspect ratios. Image generation and editing accept 21:9 (cinematic widescreen) and 5:2 (wide banners).”
   • [claimed-docs] “Requests to the slug will be served by grok-imagine-image-2.0 with quality set to low, with no change to the request or response shape”

   proof ↗⚑ flag

2. knowledge-workerShare screenshots and photos and have the assistant accurately interpret what is in them

   weight 2 · round to Grok
   Perplexity—none0/10

   The evidence pack contains no mention of image/screenshot upload or visual interpretation capability anywhere in the docs, app store listings, or API references—only text search, voice, browsing, and coding features are described.

   ⚑ flag

   Grok✓fullclaimed7/10

   Docs confirm image understanding is a first-class capability: models accept image input and 'consider the image context when generating the response' (grok-docs-25), plus related image editing docs show the model 'understands the image content' (grok-docs-29). No independent hands-on report specifically tests screenshot/photo interpretation accuracy. missing for 10: independent/community corroboration of accuracy on real screenshots or photos, detail on multi-image or OCR-style interpretation limits.

   • [claimed-docs] “Some models allow images in the input. The model will consider the image context when generating the response.”
   • [claimed-docs] “Edit an existing image by providing a source image along with your prompt. The model understands the image content and applies your requeste…”
   • [claimed-docs] “Use up to five source images for a single image edit.”

   proof ↗⚑ flag

Voice

1. knowledge-workerHave a natural, real-time voice conversation with the assistant

   weight 2 · round to Grok
   Perplexity~partialclaimed4/10

   Perplexity's mobile app docs mention a 'Voice' feature ('Instant, up-to-date answers whether you type or say it'), indicating voice input/output exists, but there's no evidence describing a natural, continuous, real-time back-and-forth voice conversation mode (like a dedicated voice-chat UI) or its quality/latency. Missing for 10: details on conversational turn-taking, interruption handling, voice mode UX specifics, and independent hands-on validation of voice conversation quality.

   • [claimed-docs] “Voice: Instant, up-to-date answers whether you type or say it.”
   • [claimed-docs] “· Voice: Instant, up-to-date answers whether you type or say it.”

   proof ↗⚑ flag

   Grok✓fullcommunity6/10

   xAI documents hands-free voice conversations directly in Grok ('Talk to Grok hands-free with voice') and separately documents real-time streaming speech-to-text with VAD tuning, indicating a live voice-conversation feature exists. However, missing for 10: independent/hands-on corroboration of voice conversation naturalness or latency, and no detail on turn-taking/interruption handling beyond the VAD parameter.

   • [claimed-docs] “Talk to Grok hands-free with voice.”
   • [claimed-docs] “Speech to Text now accepts a vad_threshold parameter (streaming query param and batch multipart field) to tune the voice-activity gate”
   • [community] “I am excited for the voice mode promised in 'a week' or so. ChatGPT Advanced Voice has been a big disappointment for me... If Grok 3 voice m…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Perplexity~partialclaimed5/10

   The API/Agent API exposes web-grounded search, citations, sandboxed code execution, structured output, model fallback, and CLI/MCP integrations, covering much of what the UI offers, but UI-only consumer features like Assistant task automation (email drafting, scheduling, reservations), Voice, Library/Discover, and browser extension page-context features have no documented API equivalents. missing for 10: API parity for Assistant actions (email/scheduling/booking), Voice interface, Library/Discover/curation features, browser-extension contextual page understanding, and independent confirmation that all UI capabilities are API-accessible.

   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [claimed-docs] “The `sandbox` tool gives the agent an isolated Linux container to run real code and use the output in its answer”
   • [claimed-docs] “Structured output makes the model return JSON that conforms to a schema you define, so you can deserialize it directly.”
   • [claimed-docs] “Model fallback enables specifying multiple models in a `models` array. The API tries each model in order until one succeeds, providing autom…”
   • [claimed-docs] “Assistant: Draft emails, schedule appointments, book reservations, and more.”
   • [claimed-docs] “Voice: Instant, up-to-date answers whether you type or say it.”
   • [claimed-docs] “Your Library: More than search history, it's a curation of your discoveries.”
   • [claimed-docs] “Discover: Learn new things from the community.”
   • [claimed-docs] “Contextual Understanding: Get answers relevant to your current page or even specific to your current domain.”

   proof ↗⚑ flag

   Grok~partialprobed5/10

   The xAI API exposes core Grok model capabilities (text, images, video, tools, structured outputs, multi-agent research, connectors) documented alongside an OpenAPI spec, so much of the UI functionality is API-accessible. However, UI-only features like Grok Bot persistent cloud computer, team workspace/SSO/billing management, and built-in OAuth connectors (Gmail, Calendar, Teams, Salesforce) appear tied to the consumer/business app rather than exposed as general API endpoints, and there's no evidence of full parity. Missing for 10: confirmation that workspace/team management, SSO, billing, and native connector orchestration are API-accessible rather than UI-exclusive, plus independent corroboration of full feature parity.

   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”
   • [claimed-docs] “Expose any internal API, database, or SaaS tool to Grok. Define your own tools with custom schemas and logic.”
   • [claimed-docs] “Built-in connectors are maintained by xAI and integrate natively with Grok. Each one authenticates via OAuth, so you connect once and Grok c…”
   • [claimed-docs] “Grok Bot — hand real work to AI teammates on a persistent cloud computer.”
   • [claimed-docs] “Secure and streamline logins by integrating Single Sign-On (SSO) with your preferred Identity Provider (IdP).”
   • [claimed-docs] “Visit grok.com/?_s=billing while logged in to manage your billing directly from the website (change plan, update payment, or cancel).”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.x.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Perplexity—none0/10

   No evidence of a data export/portability feature for user account data (chat history, library, settings) in open formats; the docs cover API access to models/search but nothing about exporting personal user data or account deletion workflows. missing for 10: any documented data export tool, format spec (JSON/CSV/etc.), or account-deletion-with-export flow.

   ⚑ flag

   Grok—none0/10

   No evidence pack item mentions any data export feature, open format (e.g., JSON/Markdown conversation export) or account data portability tool for Grok; documentation covers connectors, models, and billing but never data export/leave-with-your-data capability.

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Perplexity—none0/10

   Perplexity is a closed, proprietary product; the evidence pack shows API docs, apps, CLI, and MCP integrations but no mention of open-sourcing the product itself or any open-license source code repository.

   ⚑ flag

   Grok—none0/10

   The evidence pack contains only proprietary API/product documentation and community commentary; there is no mention of any open-source license, public source repository, or open-weights release for Grok. As a mainstream capability question applicable to AI products, absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Perplexity—none0/10

   Perplexity is offered exclusively as a hosted SaaS (web app, mobile apps, browser extension, cloud API/CLI/MCP) with no evidence of any self-hostable core product, open-source release, or on-prem deployment option.

   ⚑ flag

   Grok—none0/10

   Grok is a closed, proprietary API/cloud service; no evidence anywhere in the pack of open-sourced weights or a self-hostable core model/product, only hosted APIs, connectors, and SaaS features. Absence of any self-hosting capability for an applicable axis (models can in principle be released for self-hosting, as some competitors do) yields none rather than na.

   • [claimed-docs] “Generate text, have conversations, use tools, and build AI-powered applications.”
   • [claimed-docs] “previous input prompts, reasoning content, and model responses are saved and stored on xAI's servers”
   • [claimed-docs] “Visit grok.com/?_s=billing while logged in to manage your billing directly from the website (change plan, update payment, or cancel).”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Perplexity—none0/10

   No evidence in the pack mentions data residency, regional storage options, or any user-selectable region controls; Perplexity's docs focus on models, search, MCP/CLI integrations, and app features but never address data storage location or residency choices.

   ⚑ flag

   Grok—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location choices for Grok; docs only confirm data is stored on xAI's servers without any residency options (grok-docs-21). Missing for 10: any mention of regional data storage options, residency controls, or compliance certifications tied to geography.

   • [claimed-docs] “previous input prompts, reasoning content, and model responses are saved and stored on xAI's servers”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Perplexity—none0/10

   No evidence in the pack of any opt-out setting, privacy policy statement, or documented control letting users prevent their data from being used for AI training; the evidence pack only covers product features (search, CLI, MCP, browser extension) and unrelated community complaints about crawling/robots.txt behavior. Missing for 10: any documentation of a training opt-out toggle, privacy settings page, or data-use policy addressing model training.

   ⚑ flag

   Grok—none0/10

   The evidence pack documents data retention (prompts and responses stored on xAI's servers, grok-docs-21) and vague 'enterprise-grade privacy protections' for team workspaces (grok-docs-13), but nowhere mentions an opt-out toggle, training-data exclusion setting, or policy statement about excluding user conversations from model training. This axis clearly applies to a consumer/enterprise AI chat product, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “previous input prompts, reasoning content, and model responses are saved and stored on xAI's servers”
   • [claimed-docs] “In your team workspace, enjoy enterprise-grade privacy protections... Additionally, unlock the full capabilities of SuperGrok, including hig…”
   • [claimed-docs] “Switch between workspaces to access team-specific features and ensure your conversations are protected under business plan terms.”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Perplexity—none0/10

   The evidence pack contains no documentation of data retention settings, deletion controls, export options, or privacy dashboard features for Perplexity users; the only privacy-adjacent items concern the company's own web-crawling/robots.txt controversy, which is off-topic for user data control. This axis clearly applies to a consumer AI assistant, so absence of evidence yields 'none'.

   ⚑ flag

   Grok—none0/10

   Docs confirm that inputs, reasoning, and responses are stored on xAI's servers (grok-docs-21) and mention vague 'enterprise-grade privacy protections' for team workspaces (grok-docs-13), but there is no documented mechanism for users to view, control, or delete their stored data/conversation history. Missing for 10: explicit data retention settings, a user-facing deletion/export tool, and any policy detailing retention periods or opt-out controls.

   • [claimed-docs] “previous input prompts, reasoning content, and model responses are saved and stored on xAI's servers”
   • [claimed-docs] “In your team workspace, enjoy enterprise-grade privacy protections... Additionally, unlock the full capabilities of SuperGrok, including hig…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Perplexity—none0/10

   No evidence in the pack describes any telemetry opt-out, privacy settings, or usage-tracking controls; the community items discuss crawling/robots.txt disputes and product quality, not telemetry opt-out. Missing for 10: any documentation of a privacy settings page, data-collection opt-out toggle, or telemetry policy.

   ⚑ flag

   Grok—none0/10

   The evidence pack confirms xAI stores prompts, reasoning, and responses on its servers (grok-docs-21) but contains no documentation of any telemetry/usage-tracking opt-out setting, privacy toggle, or data-collection preference control for individual or ai-native users.

   • [claimed-docs] “previous input prompts, reasoning content, and model responses are saved and stored on xAI's servers”

   proof ↗⚑ flag

Research

1. knowledge-workerLaunch a deep research run that autonomously searches many sources and returns a cited report

   weight 3 · round to Grok
   Perplexity!disputedcontradicted5/10

   Perplexity's docs explicitly advertise 'Pro Search & Deep Research: Guided AI search for deeper exploration' with citations built into every answer, matching the story's core capability. However, hands-on community reports directly contradict reliable delivery: one user found citations/references 'frequently mismatched to the text' and quality declining over time, and another reports the 'Computer' research feature 'often fails to trigger via the UI, and when it does work, sessions frequently stall without returning an answer,' leading them to prefer other tools for actual research. Missing for 10: independent verification of successful autonomous multi-source runs, resolution of the stalling/citation-mismatch complaints, and clearer documentation distinguishing 'Deep Research' reliability from the separate 'Computer' agent.

   • [claimed-docs] “Perplexity Pro Search & Deep Research: Guided AI search for deeper exploration.”
   • [claimed-docs] “Features: · Perplexity Pro Search & Deep Research: Guided AI search for deeper exploration.”
   • [claimed-docs] “Trust Built In: Cited sources for every answer.”
   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [community] “User used a free 12-month Perplexity Pro offer: initially useful for quick queries like recipes or manuals, but quality declined as the comp…”
   • [community] “The 'Computer' research feature in Perplexity often fails to trigger via the UI, and when it does work, sessions frequently stall without re…”
   • [community] “For actual research, the user now prefers Claude or ChatGPT over Perplexity, saying results are higher quality and more accurate despite bei…”

   proof ↗⚑ flag

   Grok~partialclaimed6/10

   Grok's docs describe a dedicated 'Realtime Multi-agent Research' capability that orchestrates multiple AI agents to perform deep, multi-step research tasks, matching the core of the story [grok-docs-26]. However, the docs don't explicitly describe the output format (a cited report with sources) and there is no independent/hands-on corroboration of this specific feature in the evidence pack. Missing for 10: explicit documentation of citation/report formatting in the research output, and independent user validation that the feature works as described.

   • [claimed-docs] “Realtime Multi-agent Research enables Grok to orchestrate multiple AI agents that work together in real time to perform deep, multi-step res…”

   proof ↗⚑ flag

2. knowledge-workerGet answers grounded in current web results with citations back to the sources

   weight 2 · round to Grok
   Perplexity!disputedcontradicted5/10

   Perplexity's docs and consumer apps clearly document web-grounded answers with inline citations across the API, apps, and browser extension (perplexity-docs-2, -12, -24, -31), and this is a core, heavily marketed feature. However, hands-on community reports concretely contradict citation quality: users report citations/links frequently mismatched to the text and Perplexity citing AI-generated 'best software' listicle spam, undermining trust in the grounding (perplexity-comm-6, perplexity-comm-11), with some users switching to Claude/ChatGPT for research quality (perplexity-comm-9). missing for 10: independent verification that citation accuracy holds up at scale, and resolution of reported citation/source mismatch issues.

   • [claimed-docs] “Get web-grounded answers with built-in citations in one call, or access third-party models from OpenAI, Anthropic, Google, and xAI with web …”
   • [claimed-docs] “Trust Built In: Cited sources for every answer.”
   • [claimed-docs] “Cut through the clutter and get straight to credible, up-to-date answers.”
   • [claimed-docs] “Get accurate, up-to-date answers grounded in real-time web search, with inline citations in a single call, and conversation context across t…”
   • [community] “User used a free 12-month Perplexity Pro offer: initially useful for quick queries like recipes or manuals, but quality declined as the comp…”
   • [community] “For actual research, the user now prefers Claude or ChatGPT over Perplexity, saying results are higher quality and more accurate despite bei…”
   • [community] “Report claims Perplexity cites AI-generated 'best software' listicle sites en masse, raising concerns about it being manipulated by SEO/AEO …”

   proof ↗⚑ flag

   Grok~partialcommunity4/10

   Evidence shows Grok has a 'Realtime Multi-agent Research' capability for deep, multi-step research tasks and community notes suggest it can discuss current events from live X/web data, implying some grounding, but nothing in the pack explicitly documents inline citations or source links back to web results in Grok's answers. missing for 10: explicit documentation of citation formatting/source links, first-party description of real-time web search grounding, and independent verification that citations are reliably attached to responses.

   • [claimed-docs] “Realtime Multi-agent Research enables Grok to orchestrate multiple AI agents that work together in real time to perform deep, multi-step res…”
   • [community] “I am excited for the voice mode promised in 'a week' or so. ChatGPT Advanced Voice has been a big disappointment for me... If Grok 3 voice m…”

   proof ↗⚑ flag

Admin

1. team-adminManage members, permissions, and data policies for my organization's workspace

   weight 2 · round to Grok
   Perplexity—none0/10

   No evidence in the pack mentions team/workspace admin controls, member management, permission roles, or data policy settings; all evidence covers API features, apps, CLI, and MCP integrations. This is a fair axis for a team-oriented product like Perplexity (which offers Enterprise/Team plans), but absence of any admin-console or policy documentation means it cannot be credited.

   ⚑ flag

   Grok~partialclaimed6/10

   Docs show a business/team workspace admin story: inviting members via email (grok-docs-18), SSO integration with IdP (grok-docs-17), workspace switching with business-plan-protected conversations (grok-docs-39), license-gated sharing (grok-docs-14), and 'enterprise-grade privacy protections' (grok-docs-13). This covers member invitation, authentication/SSO, and some data-policy framing for admins. Missing for 10: detailed role/permission granularity (e.g., admin vs member roles, per-connector access control), explicit data retention/DLP policy configuration UI, and any independent/community corroboration of the admin console working as documented.

   • [claimed-docs] “Secure and streamline logins by integrating Single Sign-On (SSO) with your preferred Identity Provider (IdP).”
   • [claimed-docs] “Invite new team members to join your Grok Business workspace with a simple email invitation process.”
   • [claimed-docs] “Switch between workspaces to access team-specific features and ensure your conversations are protected under business plan terms.”
   • [claimed-docs] “Share conversations only with team members who have active licenses.”
   • [claimed-docs] “In your team workspace, enjoy enterprise-grade privacy protections... Additionally, unlock the full capabilities of SuperGrok, including hig…”

   proof ↗⚑ flag

Data controls

1. knowledge-workerExport my complete chat history and account data

   weight 1 · round drawn
   Perplexity—none0/10

   No evidence in the pack mentions a data export feature, account data download, or chat history export capability for Perplexity's consumer product; documentation focuses on API, MCP, CLI, and app features with no trust-controls/export functionality described.

   ⚑ flag

   Grok—none0/10

   No evidence in the pack mentions a data export or account-data download feature for Grok; docs cover connectors, models, billing, SSO, and workspace features but never a 'export my chat history/data' capability. This is a fair trust-controls axis for a consumer chat product, so absence of evidence yields 'none' rather than 'na'.

   ⚑ flag

2. knowledge-workerControl whether my conversations are used to train models

   weight 3 · round drawn
   Perplexity—none0/10

   No evidence in the pack addresses privacy settings, opt-out of training, or data-usage controls for conversations; all citations concern product features (search, MCP, CLI, apps) or unrelated crawler/quality controversies. This axis applies to any consumer AI product handling user conversations, so absence of evidence yields 'none'.

   ⚑ flag

   Grok—none0/10

   Docs mention 'enterprise-grade privacy protections' for team workspaces and that prompts are stored on xAI servers, but there is no documented setting or toggle letting a knowledge-worker control whether their conversations are used to train models. Community commentary raises general distrust but does not confirm or deny a specific training opt-out control.

   • [claimed-docs] “In your team workspace, enjoy enterprise-grade privacy protections... Additionally, unlock the full capabilities of SuperGrok, including hig…”
   • [claimed-docs] “previous input prompts, reasoning content, and model responses are saved and stored on xAI's servers”
   • [community] “Musk already has too much power, won't trust him with my AI conversations.”

   proof ↗⚑ flag