Grok vs Poke

Agent access

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

   weight 2 · round to Grok
   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

   Poke✓fullprobed8/10

   A live llms.txt file is confirmed via direct probe (HTTP 200) with actual agent-oriented content describing Poke, and Poke also maintains structured docs pages that agents/tools can be pointed at. missing for 10: no docs.md or openapi.json fallback (both 404), and no independent report of an agent successfully consuming llms.txt end-to-end.

   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”
   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [probe] “PROBE docs-md: HTTP 404 at https://poke.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Poke~partialprobed6/10

   Poke's docs explicitly state its API can be called from scripts, CI/CD pipelines, and monitoring tools to trigger messages programmatically, which supports headless/automation use (poke-docs-1, poke-docs-2). However, there's no evidence of a full headless run mode (e.g., batch execution, structured output for CI parsing) and probes show no OpenAPI/swagger spec is exposed, suggesting the API's automation surface is thin and undocumented beyond message-sending. Missing for 10: independent/hands-on CI integration examples, a public OpenAPI schema, and evidence of structured/machine-readable responses needed for reliable CI pipelines.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 3 · round to Poke
   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

   Poke✓fullprobed8/10

   Poke's docs explicitly describe MCP server support, with CLI commands to tunnel local MCP servers and add remote ones ('poke mcp add'), plus a recipe/marketplace ecosystem for sharing MCP-based tools. This is first-party documented and corroborated by a probe confirming the docs page exists, though there's no independent hands-on report of the MCP integration actually working. Missing for 10: independent/hands-on verification of MCP tool usage in practice, and more detail on tool invocation reliability.

   • [claimed-docs] “Poke supports Model Context Protocol (MCP) servers, allowing you to extend Poke with custom tools and data sources.”
   • [claimed-docs] “npx poke@latest tunnel http://localhost:3000/mcp -n "Local Dev MCP"”
   • [claimed-docs] “you earn revenue from MCP usage by users who install your recipe”
   • [claimed-docs] “npx poke@latest mcp add https://mcp.example.com/sse -n "My Server"”
   • [probe] “official MCP server documented at https://poke.com/docs/mcp-servers”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Poke
   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

   Poke~partialclaimed6/10

   Poke ships an official CLI invoked via `npx poke@latest` with subcommands like `login`, `tunnel`, and `mcp add`, confirming a real CLI exists for developer/MCP workflows. However, the documented CLI scope is narrow (mainly MCP server registration/tunneling and login) rather than a general-purpose CLI for broader AI-native automation tasks. Missing for 10: evidence of a fuller command set (e.g. messaging, recipe management, account/config commands) and any independent/hands-on verification of the CLI's reliability.

   • [claimed-docs] “npx poke@latest tunnel http://localhost:3000/mcp -n "Local Dev MCP"”
   • [claimed-docs] “npx poke@latest login”
   • [claimed-docs] “npx poke@latest mcp add https://mcp.example.com/sse -n "My Server"”
   • [claimed-docs] “Poke supports Model Context Protocol (MCP) servers, allowing you to extend Poke with custom tools and data sources.”

   proof ↗⚑ flag

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

   weight 3 · round to Grok
   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

   Poke~partialprobed6/10

   Poke documents a public API for sending messages programmatically and integrating with external triggers (CI/CD, monitoring tools), plus CLI/MCP tooling for extending functionality, showing genuine programmatic access. However, no OpenAPI/Swagger spec or formal API reference was found (404s on standard discovery paths), so the API's documentation depth and completeness are unclear. Missing for 10: a full API reference/spec (OpenAPI schema), authentication details, rate limits, and independent developer corroboration of building against the API.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Poke—none0/10

   Evidence shows Poke supports API access, integrations, and MCP servers, but there's no mention of scoped or least-privilege API credential/key issuance for agents — no API key management, permission scoping, or token-based access control documentation. The prompt-injection incident (poke-comm-1) raises security concerns but is unrelated to credential scoping specifically.

   ⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Poke
   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

   Poke~partialprobed4/10

   Poke exposes a documented API for sending messages programmatically and an official CLI (`npx poke@latest`) for managing MCP servers and recipes, which developers can build against, but there is no evidence of dedicated official SDK packages (e.g., Python/JS client libraries) — probes for OpenAPI/swagger specs and docs.md all returned 404, suggesting no formal SDK artifacts beyond the CLI/API docs. missing for 10: language-specific SDK packages, published OpenAPI/schema spec, independent developer corroboration of SDK usage.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [claimed-docs] “npx poke@latest login”
   • [claimed-docs] “npx poke@latest mcp add https://mcp.example.com/sse -n "My Server"”
   • [probe] “PROBE docs-md: HTTP 404 at https://poke.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Poke
   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

   Poke~partialclaimed4/10

   Poke's API docs mention that external services like GitHub, CI/CD, or monitoring tools can trigger Poke via webhook-style calls, and the API can send messages programmatically, showing some webhook-adjacent integration. However, there's no explicit documentation of Poke exposing an outbound webhook subscription system for AI-native users to subscribe to Poke's own events. missing for 10: explicit outbound webhook/event subscription API, event types list, subscription management docs, independent confirmation of webhook reliability.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Grok
   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

   Poke~partialclaimed4/10

   Poke can extract and visualize data from shared images/spreadsheets into tables and charts, and integrations let it access and act on connected app data conversationally, which implies some data-driven insight generation. However, there's no explicit documentation of proactive AI-generated insights, trend analysis, or suggestions surfaced from a user's own accumulated data/history. missing for 10: dedicated insights/suggestions feature documentation, evidence of proactive analysis of user data patterns, independent/hands-on confirmation of this capability.

   • [claimed-docs] “Poke can now create tables and charts to help you visualize data. Describe what you want to see, or share images of existing data (like spre…”
   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”

   proof ↗⚑ flag

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

   weight 2 · round to Poke
   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

   Poke~partialprobed5/10

   Poke's docs show building blocks for automation—an API that external tools (CI/CD, monitoring) can call to trigger Poke, and a 'recipes' system that can be created and published—plus positioning as a 'proactive AI assistant.' However there is no explicit documentation of scheduled/autonomous background jobs running without an external trigger or user prompt. missing for 10: documented scheduling/cron-like triggers, evidence of recipes running unattended in the background, independent confirmation of autonomous execution.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [claimed-docs] “npx poke@latest login”
   • [claimed-docs] “Publishing a recipe: marks it Published, generates a referral/share link, makes it eligible for payouts”
   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”

   proof ↗⚑ flag

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

   weight 3 · round to Poke
   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

   Poke✓fullprobed8/10

   Poke IS the built-in AI assistant itself — users delegate tasks via natural conversation, integrations, MCP tools, and even real-human task execution (reservations, calls, deploying websites), all documented in first-party docs. Missing for 10: independent hands-on validation of task delegation beyond the security prompt-injection incident, which is off-topic here.

   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”
   • [claimed-docs] “Poke can now bring in real people to take on tasks with a human touch - restaurant reservations, phone calls, placing orders, booking rides,…”
   • [claimed-docs] “Poke can also create and deploy websites for you at yourname.poke.com.”
   • [claimed-docs] “Poke supports Model Context Protocol (MCP) servers, allowing you to extend Poke with custom tools and data sources.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”

   proof ↗⚑ flag

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

   weight 2 · round to Poke
   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

   Poke✓fullprobed8/10

   Poke's entire interface is natural-language texting across WhatsApp/Apple Messages/Telegram, and its docs explicitly state integrations let it 'access information and perform actions across apps and services through natural conversation' (poke-docs-7/19), corroborated by the llms.txt description of Poke texting like a human (poke-probe-1). Missing for 10: independent hands-on user reviews confirming natural-language command reliability beyond vendor docs, and no detail on limits/edge cases of NL command parsing.

   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”
   • [claimed-docs] “Poke can now bring in real people to take on tasks with a human touch - restaurant reservations, phone calls, placing orders, booking rides,…”
   • [claimed-docs] “Poke can now create tables and charts to help you visualize data. Describe what you want to see, or share images of existing data (like spre…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Grok
   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

   Poke—none0/10

   No evidence of an interactive API reference or runnable examples; probes for OpenAPI/Swagger specs and docs.md all returned 404, and only basic prose docs about the messaging API exist.

   • [probe] “PROBE docs-md: HTTP 404 at https://poke.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”
   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”

   proof ↗⚑ flag

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

   weight 2 · round to Grok
   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

   Poke—none0/10

   Direct probes for OpenAPI/swagger spec files all returned 404, and no documentation references a downloadable machine-readable API spec; only an llms.txt file exists, which is not an API spec.

   • [probe] “PROBE docs-md: HTTP 404 at https://poke.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Poke—none0/10

   No evidence pack mentions any sandbox environment, test/staging mode, or way to isolate testing from production data; Poke's docs focus on integrations, MCP servers, and messaging features with no mention of sandboxing.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Poke—none0/10

   There is no evidence of API versioning scheme, changelog for breaking changes, or a documented deprecation policy; probes show no OpenAPI spec available (404s), and docs only describe basic API usage without versioning or deprecation commitments.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”
   • [probe] “PROBE docs-md: HTTP 404 at https://poke.com/docs.md”

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

   Poke~partialprobed5/10

   Poke's docs show it can be triggered by external events (GitHub, CI/CD) and can even delegate real-world tasks to humans (reservations, calls) and act across integrated apps 'through natural conversation,' plus the llms.txt describes it as a 'proactive AI assistant.' However, there is no explicit documentation of a structured multi-step task queue, autonomous background execution status, or a dedicated review/approval step for complex delegated tasks. Missing for 10: explicit multi-step task orchestration docs, background task status/progress tracking, and a defined 'review results' UX beyond ad-hoc chat replies.

   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Poke can now bring in real people to take on tasks with a human touch - restaurant reservations, phone calls, placing orders, booking rides,…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Poke—none0/10

   Poke's docs describe integrations, MCP tool connections, and even outsourcing tasks to humans, but there is no evidence Poke itself drives a web browser to navigate sites or complete web-based research/tasks autonomously. missing for 10: any mention of browser automation, web navigation, or headless browsing capability.

   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Poke can now bring in real people to take on tasks with a human touch - restaurant reservations, phone calls, placing orders, booking rides,…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Poke—none0/10

   Poke's evidence shows it connects to cloud services/integrations and MCP tool servers (poke-docs-7, poke-docs-19, poke-docs-3) but there is no evidence of it seeing a user's screen or directly operating local desktop applications — its automation is limited to API/webhook-based integrations and remote 'recipes,' not computer-use style control of a user's machine.

   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”
   • [claimed-docs] “Poke supports Model Context Protocol (MCP) servers, allowing you to extend Poke with custom tools and data sources.”

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

   Poke—none0/10

   The evidence pack shows Poke's API/integrations for triggering messages from external events (CI/CD, monitoring) and MCP tool extensions, but nothing documents a user-facing scheduler for recurring or one-off tasks that return results later. Missing for 10: any explicit scheduling/reminder feature, recurrence configuration, or hands-on proof of a task running and reporting back autonomously.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”

   proof ↗⚑ flag

Apps

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

   weight 2 · round to Grok
   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

   Poke—none0/10

   Evidence shows Poke operates through existing messaging channels (Apple Messages, WhatsApp, Telegram) rather than shipping its own official iOS/Android app; no documentation or probe evidence mentions a dedicated Poke mobile app.

   • [claimed-docs] “Poke is now available on Apple Messages as the first and only AI product to be verified on the platform.”
   • [claimed-docs] “Poke now works with Telegram as an alternative to WhatsApp while it is temporarily unavailable (except in Italy and Brazil).”
   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”

   proof ↗⚑ flag

Custom bots

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

   weight 2 · round to Poke
   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

   Poke~partialclaimed5/10

   Poke supports 'recipes' that can be created, published, shared via referral link, and monetized, plus MCP servers/integrations that extend its knowledge and behavior — this maps loosely to custom assistants with instructions/knowledge. However, there's no explicit documentation of defining a persistent 'assistant persona' with custom instructions in the way tools like GPTs allow; recipes appear more tool/automation-centric than persona-centric. missing for 10: explicit support for custom system-prompt/persona instructions per assistant, evidence of knowledge-base attachment beyond MCP tool integration, independent user validation of sharing custom assistants.

   • [claimed-docs] “you earn revenue from MCP usage by users who install your recipe”
   • [claimed-docs] “npx poke@latest login”
   • [claimed-docs] “Publishing a recipe: marks it Published, generates a referral/share link, makes it eligible for payouts”
   • [claimed-docs] “Go to poke.com/recipes to browse all first-party and approved third-party recipes.”
   • [claimed-docs] “Poke supports Model Context Protocol (MCP) servers, allowing you to extend Poke with custom tools and data sources.”
   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”

   proof ↗⚑ flag

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

   weight 2 · round to Grok
   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

   Poke—none0/10

   Evidence shows Poke can message, integrate apps, and run recipes/MCP tools, but nothing describes performing bulk operations across many items at once (e.g., batch processing, multi-item automation loops); this remains unevidenced.

   ⚑ flag

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

   weight 3 · round to Poke
   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

   Poke~partialclaimed5/10

   Poke supports external triggers via its API (services like GitHub/CI/CD can trigger Poke) and integrations that let it act across apps, which enables event-driven automation, but there's no documented user-facing rules engine (e.g., 'if X happens, do Y' conditional automation builder) — triggers rely on third-party services calling the API rather than Poke itself defining declarative rules. missing for 10: a native rule/condition definition UI or DSL, evidence of multi-step conditional logic, and independent confirmation of reliability of triggered automations.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   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

   Poke—none0/10

   No evidence describes a scheduling or recurring-job/workflow feature; docs cover API messaging, integrations, MCP servers, and recipes but nothing about setting up recurring or time-based automations. The 'proactive assistant' description in the probe snippet is too vague to confirm recurring job scheduling. missing for 10: any documentation of cron-like scheduling, recurring triggers, or persistent workflow automation.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://poke.com/llms.txt # Poke > Poke is the proactive AI assistant on Apple Messages, WhatsApp, Telegram, an…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Poke—none0/10

   No evidence describes versioning, review workflows, or rollback capability for Poke's automations/recipes; docs mention creating, publishing, and monetizing recipes but nothing about version history or reverting changes.

   ⚑ flag

Connectors

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

   weight 2 · round to Poke
   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

   Poke✓fullclaimed7/10

   Poke docs describe poke.com/recipes as a directory of first-party and approved third-party recipes/integrations that users can browse and add, plus a separate Integrations page for connecting apps/services. This matches the power-user story of browsing and adding connectors. missing for 10: independent/hands-on evidence of the directory's breadth or UX, and no confirmation of search/filtering or ratings within the directory.

   • [claimed-docs] “Go to poke.com/recipes to browse all first-party and approved third-party recipes.”
   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”
   • [claimed-docs] “Webflow - Design and deploy websites visually”
   • [claimed-docs] “Poke supports Model Context Protocol (MCP) servers, allowing you to extend Poke with custom tools and data sources.”

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

   Poke~partialclaimed3/10

   Poke's docs describe a general 'Integrations' system that lets users connect apps/services (with Webflow given as the only named example) and mention an email-address feature, but no evidence names concrete cloud-drive (e.g., Google Drive), email (Gmail/Outlook), or calendar connectors, nor demonstrates search/use of such data in answers. Missing for 10: named cloud-drive integration, named email inbox integration, named calendar integration, and evidence of search/retrieval across them.

   • [claimed-docs] “Integrations let you connect your favorite apps and services to Poke. Once connected, Poke can access information and perform actions across…”
   • [claimed-docs] “Once connected, Poke can access information and perform actions across apps and services through natural conversation.”
   • [claimed-docs] “Webflow - Design and deploy websites visually”
   • [claimed-docs] “You can now set up a @poke.com address to use with your primary email account in Poke.”

   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 Poke
   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

   Poke~partialclaimed4/10

   Poke's docs show it can create tables and charts from described data or shared images (poke-docs-21), but there's no evidence of an underlying code-execution environment, computed numeric answers, or generation of downloadable files. missing for 10: evidence of actual code execution/sandbox, computed-answer capability, downloadable file output.

   • [claimed-docs] “Poke can now create tables and charts to help you visualize data. Describe what you want to see, or share images of existing data (like spre…”

   proof ↗⚑ flag

Artifacts

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

   weight 2 · round drawn
   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

   Poke—none0/10

   Evidence shows Poke can create websites and generate tables/charts from data, but there is no evidence of creating or iteratively editing documents/presentations that can be exported (e.g. Word, PDF, PowerPoint files). Missing for 10: document creation/editing evidence, presentation creation, export functionality for standard file formats.

   • [claimed-docs] “Poke can also create and deploy websites for you at yourname.poke.com.”
   • [claimed-docs] “Poke can now create tables and charts to help you visualize data. Describe what you want to see, or share images of existing data (like spre…”

   proof ↗⚑ flag

Files

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

   weight 3 · round to Grok
   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

   Poke~partialclaimed3/10

   The only relevant evidence is that Poke can 'extract and visualize' data from shared images of spreadsheets to create tables/charts, which is a narrow slice of the story. There is no documentation of direct document or PDF upload, parsing, or accurate content analysis for knowledge-worker use cases. Missing for 10: explicit PDF/document upload support, evidence of accuracy on structured/text-heavy files, and any hands-on validation of analysis quality.

   • [claimed-docs] “Poke can now create tables and charts to help you visualize data. Describe what you want to see, or share images of existing data (like spre…”

   proof ↗⚑ flag

Memory

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

   weight 3 · round to Poke
   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

   Poke~partialclaimed5/10

   Docs mention Poke's Memory as a concept tied to account merging (poke-docs-20), implying persistent memory exists across the assistant, but there's no detailed documentation of how memory is captured, retained, or applied across separate conversations, nor independent confirmation of its effectiveness. Missing for 10: dedicated memory documentation explaining retention/retrieval mechanics, examples of cross-chat context recall, and independent/hands-on verification that it works reliably.

   • [claimed-docs] “This keeps Poke's Memory, Recipes, and Integrations from the selected account, and your messaging channels ... will be connected to it.”

   proof ↗⚑ flag

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

   weight 1 · round to Poke
   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

   Poke~partialclaimed3/10

   The docs mention a 'Memory' feature tied to a user's account (carried over when merging accounts), implying some persistent context storage, but there is no documentation of a dedicated custom-instructions/preferences setting that explicitly shapes every response. Missing for 10: explicit UI/API for setting persistent custom instructions, examples of how such preferences influence responses, and independent confirmation of this behavior.

   • [claimed-docs] “This keeps Poke's Memory, Recipes, and Integrations from the selected account, and your messaging channels ... will be connected to it.”

   proof ↗⚑ flag

Projects

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

   weight 2 · round drawn
   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

   Poke—none0/10

   Poke's docs describe messaging, integrations, MCP servers, and recipes, but there is no mention of organizing chats/files into projects or spaces with shared context/instructions, which is a distinct memory-organization feature not evidenced here.

   ⚑ flag

Images

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

   weight 2 · round to Grok
   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

   Poke—none0/10

   Evidence shows Poke can create tables/charts from data and extract data from images (poke-docs-21), and can create websites, but there is no mention of generating or editing images from natural-language prompts anywhere in the docs or release notes.

   ⚑ flag

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

   weight 2 · round to Grok
   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

   Poke~partialclaimed5/10

   Poke's release notes explicitly state it can 'share images of existing data (like spreadsheets) for Poke to extract and visualize,' showing some image-interpretation capability, but this is limited to structured data extraction rather than general photo/screenshot understanding across varied content. Missing for 10: evidence of accurate interpretation of arbitrary photos/screenshots (e.g., UI screenshots, handwritten notes, general scenes), independent hands-on verification of accuracy, and any first-party documentation describing general vision/OCR capability beyond the spreadsheet example.

   • [claimed-docs] “Poke can now create tables and charts to help you visualize data. Describe what you want to see, or share images of existing data (like spre…”

   proof ↗⚑ flag

Voice

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

   weight 2 · round to Grok
   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

   Poke—none0/10

   Poke is described as a text-based assistant across messaging platforms (WhatsApp, Telegram, Apple Messages) with no evidence of real-time voice call or voice conversation capability; all documented interactions are text/message-based.

   ⚑ flag

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

   weight 2 · round to Grok
   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

   Poke~partialprobed4/10

   Poke exposes a documented API for sending messages programmatically and triggering it from external systems (poke-docs-1, poke-docs-2), plus an MCP server/tunnel mechanism for extending tools (poke-docs-3/4/16). However, there's no evidence of API parity for major UI capabilities like managing integrations, recipes, human-task requests, website deployment, or memory/account management, and no public OpenAPI/spec was found (poke-probe-2, poke-probe-3 both 404). missing for 10: API coverage for integrations/recipes/human-tasks/website-deploy features, published OpenAPI spec, independent confirmation of API-UI parity.

   • [claimed-docs] “The Poke API allows you to send messages programmatically from your applications, scripts, and automation tools.”
   • [claimed-docs] “Services like GitHub, CI/CD pipelines, or monitoring tools can trigger Poke when something happens.”
   • [claimed-docs] “Poke supports Model Context Protocol (MCP) servers, allowing you to extend Poke with custom tools and data sources.”
   • [claimed-docs] “npx poke@latest tunnel http://localhost:3000/mcp -n "Local Dev MCP"”
   • [claimed-docs] “npx poke@latest mcp add https://mcp.example.com/sse -n "My Server"”
   • [probe] “PROBE docs-md: HTTP 404 at https://poke.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://poke.com/openapi.json, https://poke.com/swagger.json, https://poke.com/api/openapi.json, htt…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Poke—none0/10

   No evidence of any data export feature or open-format data portability in Poke's docs; the pack covers messaging API, MCP servers, integrations, and account merging but nothing about exporting user data (memory, conversation history, recipes) in open formats or account closure/data takeout.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Poke—none0/10

   No evidence Poke's source code is published under any open license; Poke is presented as a closed SaaS product with docs, APIs, and integrations but no repository or licensing information is mentioned anywhere in the evidence pack.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   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

   Poke—none0/10

   Poke is a hosted SaaS assistant with no evidence of any self-hostable core product, open-source release, or on-prem deployment option; all docs describe a cloud service accessed via API/integrations/MCP.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Poke—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or storage location controls; Poke's docs cover integrations, MCP, messaging channels, and pricing but nothing about where user data is stored or any regional choice.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Poke—none0/10

   No evidence in the pack addresses data-training opt-out or privacy controls regarding AI model training; the docs focus on messaging, integrations, MCP, and recipes with no mention of data usage policies or opt-out settings.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   Poke—none0/10

   No evidence pack item addresses data retention policies, deletion controls, or export/delete-my-data mechanisms; docs cover memory merging and integrations but not retention/deletion controls, and the prompt-injection report is unrelated to this axis.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Poke—none0/10

   No evidence pack item discusses telemetry, analytics opt-out, or usage-tracking controls for Poke users; docs cover API, MCP, integrations, pricing, and release notes but never privacy/telemetry settings.

   ⚑ flag

Research

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

   weight 3 · round to Grok
   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

   Poke—none0/10

   Poke's evidence pack covers messaging integrations, MCP tool extensibility, recipes, and various assistant features, but nothing describes an autonomous multi-source deep research capability that returns a cited report. No mention of web search breadth, citation generation, or research-report output.

   ⚑ flag

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

   weight 2 · round to Grok
   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

   Poke—none0/10

   No evidence describes Poke performing web search, retrieval-augmented answers, or providing citations back to sources; docs focus on messaging, integrations, MCP tooling, and account features, not grounded research answers.

   ⚑ flag

Data controls

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

   weight 1 · round drawn
   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

   Poke—none0/10

   No evidence in the pack mentions any data export, chat history download, or account data portability feature; documentation covers integrations, MCP, recipes, and messaging channels but nothing about exporting user data.

   ⚑ flag

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

   weight 3 · round drawn
   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

   Poke—none0/10

   No evidence pack item addresses model-training data usage or opt-out controls for conversation data; documentation covers integrations, MCP, pricing, and release notes but nothing about training data policy. Missing for 10: any privacy/data-training policy page, opt-out toggle, or enterprise data-use agreement.

   ⚑ flag