Grok vs Martin

Agent access

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

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

   Martin✓fullprobed9/10

   martin-probe-1 confirms a live llms.txt at docs.trymartin.com/llms.txt returning HTTP 200 with a structured index of docs, and the .md-suffixed doc URLs throughout the evidence pack (e.g. martin-docs-1 through martin-docs-24) show agent-oriented markdown documentation is directly accessible. Missing for 10: no independent/hands-on confirmation that an agent successfully consumed llms.txt to complete a task.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.trymartin.com/llms.txt # Martin ## Docs - [Introduction](https://docs.trymartin.com/introduction.…”
   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”

   proof ↗⚑ flag

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

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

   Martin—none0/10

   Martin's docs describe a fixed set of built-in integrations (calendar, email, Slack, todos, notes) but there is no mention of MCP protocol support or any way for users to plug in arbitrary MCP servers for Martin to use as tools.

   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “Have Martin read, draft, and reply to emails in your inbox.”
   • [claimed-docs] “Have Martin read and send messages in Slack from your account.”
   • [claimed-docs] “You can tell Martin to add, edit, and check off your to-dos on your behalf from any interface.”
   • [claimed-docs] “You can tell Martin to read, add, and edit your notes from any interface.”

   proof ↗⚑ flag

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

   Martin—none0/10

   Martin is a personal-assistant product controlled via chat/email/Slack/phone interfaces, but there is no evidence of a documented public API for developers to programmatically drive it — probes for OpenAPI/Swagger specs all returned 404. missing for 10: a documented public API, SDK, or endpoint reference; any developer-facing API authentication or usage docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trymartin.com/openapi.json, https://docs.trymartin.com/swagger.json, https://docs.tryma…”

   proof ↗⚑ flag

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

   Martin—none0/10

   Martin is a personal assistant that connects to full-access integrations (email, calendar, Slack) but there is no evidence of scoped or least-privilege credential issuance, API key management, or granular permissioning for agent access — no OpenAPI/API docs even exist per probe results.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trymartin.com/openapi.json, https://docs.trymartin.com/swagger.json, https://docs.tryma…”
   • [claimed-docs] “Once connected, you can tell Martin to read, draft, and reply to emails on your behalf.”
   • [claimed-docs] “Once connected, you can tell Martin to read, send, and reply to Slack messages on your behalf.”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

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

   Martin—none0/10

   Martin's evidence pack covers only end-user integrations (calendar, email, Slack, etc.) and consumer interfaces, with no mention of an SDK, API, or developer library; probes for an OpenAPI/Swagger spec all returned 404s, indicating no public API/SDK surface exists to build against.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trymartin.com/openapi.json, https://docs.trymartin.com/swagger.json, https://docs.tryma…”
   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”

   proof ↗⚑ flag

Agentic features

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

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

   Martin~partialclaimed6/10

   Martin generates daily/weekly briefings synthesized from your calendar and inbox data, proactively drafts emails, and triages/labels emails with follow-up suggestions—all forms of AI-generated insights/suggestions surfaced inside the product. However, these are framed as autonomous actions rather than an explicit 'insights' or analytics layer, and there's no dedicated dashboard-style insight generation from broader personal data. Missing for 10: no independent/hands-on evidence corroborating quality of the 'insight' content itself, and no explicit analytics/trend-surfacing feature distinct from task-execution suggestions.

   • [claimed-docs] “Martin can send you daily or weekly briefings via email.”
   • [claimed-docs] “Martin can proactively draft emails for you and send them on your behalf.”
   • [claimed-docs] “Martin can automatically label your emails and take follow up actions on your behalf.”
   • [claimed-docs] “Martin syncs with multiple search engines to find you the most relevant information.”

   proof ↗⚑ flag

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

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

   Martin✓fullcommunity8/10

   Martin's docs describe multiple always-on background automations—daily/weekly briefings, proactive email drafting, email triage, wake-up calls, cc-to-schedule meeting booking, and custom multi-step shortcuts—all of which run without direct user prompting, and community reports (e.g., using Martin as a persistent background agent for todos) corroborate real autonomous use. Missing for 10: independent verification of scheduling/configuration UI for these background jobs and long-term reliability data beyond one HN comment about failure rates improving.

   • [claimed-docs] “Create custom shortcuts that trigger multi-step actions.”
   • [claimed-docs] “Martin can send you daily or weekly briefings via email.”
   • [claimed-docs] “Martin can proactively draft emails for you and send them on your behalf.”
   • [claimed-docs] “Martin can automatically label your emails and take follow up actions on your behalf.”
   • [claimed-docs] “Martin can call you at a specific time every morning to wake you up with the weather and your schedule.”
   • [claimed-docs] “Cc Martin on an email to schedule a meeting.”
   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”
   • [community] “A big piece of product feedback we got was 'I don't trust AI to take actions like sending texts/emails on my behalf if it's not 100% reliabl…”

   proof ↗⚑ flag

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

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

   Martin✓fullcommunity8/10

   Martin IS the built-in AI assistant, and users delegate tasks to it across calendar, email, Slack, reminders, todos, notes, and multi-step shortcuts via chat, phone, SMS, email, or Slack, with hands-on community accounts confirming real task delegation and reliability improvements. missing for 10: independent quality/reliability benchmarking beyond anecdotal HN comments, and no evidence of failure-mode transparency or task-success metrics.

   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “You can tell Martin to add, edit, and check off your to-dos on your behalf from any interface.”
   • [claimed-docs] “You can tell Martin to read, add, and edit your notes from any interface.”
   • [claimed-docs] “Create custom shortcuts that trigger multi-step actions.”
   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”
   • [community] “I’m impressed. I’ll probably cancel ChatGPT Pro subscription and switch to this... it’s handling some complicated requests correctly the fir…”
   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”
   • [community] “A big piece of product feedback we got was 'I don't trust AI to take actions like sending texts/emails on my behalf if it's not 100% reliabl…”

   proof ↗⚑ flag

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

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

   Martin✓fullcommunity8/10

   Martin is explicitly designed around natural-language commands across calendar, email, Slack, reminders, todos, notes, shortcuts, and phone/SMS interfaces, with docs and taglines like 'Text Jon my arrival time' or 'Cc Martin on an email to schedule a meeting' showing conversational control, and community feedback (HN) corroborates real usage of natural-language task delegation. missing for 10: independent hands-on benchmarking of NL command breadth/accuracy beyond anecdotal HN praise, and no formal API/spec confirming NLU robustness.

   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “Tell Martin to remind you to do something, and he will ping you when the time comes.”
   • [claimed-docs] “You can tell Martin to add, edit, and check off your to-dos on your behalf from any interface.”
   • [claimed-docs] “Cc Martin on an email to schedule a meeting.”
   • [claimed-docs] “Text Jon my arrival time.”
   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”
   • [community] “I’m impressed. I’ll probably cancel ChatGPT Pro subscription and switch to this... it’s handling some complicated requests correctly the fir…”
   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”

   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

   Martin—none0/10

   Martin is a personal assistant product with docs pages but no evidence of any interactive API reference or runnable examples; probes explicitly show no OpenAPI/swagger spec found at any candidate path. missing for 10: interactive API reference UI, runnable code examples, OpenAPI spec availability.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trymartin.com/openapi.json, https://docs.trymartin.com/swagger.json, https://docs.tryma…”

   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

   Martin—none0/10

   Martin is a personal assistant product, not a developer API platform, but the axis of publishing a machine-readable API spec still applies as a fair question; the probe explicitly checked all standard OpenAPI/swagger paths and found only 404s, with no evidence of any downloadable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trymartin.com/openapi.json, https://docs.trymartin.com/swagger.json, https://docs.tryma…”

   proof ↗⚑ flag

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

   Martin—none0/10

   Martin is a personal-assistant product with no evidence of any public API, versioning scheme, or deprecation policy; the openapi probe returned 404 on all candidate paths and no docs mention API versioning. missing for 10: any public API reference, version numbers, changelog, deprecation policy documentation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trymartin.com/openapi.json, https://docs.trymartin.com/swagger.json, https://docs.tryma…”

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

   Martin~partialcommunity7/10

   Martin's docs describe multiple background/autonomous capabilities (proactive email drafts, email triage with follow-up actions, cc-to-schedule meeting booking, custom multi-step shortcuts, daily briefings) that match delegating a task for autonomous background work with results delivered back to the user, and community posts corroborate real usage of the cloud-based agent for ongoing tasks (todos) across sessions. However, evidence doesn't clearly show a distinct 'review before finalizing' step for these autonomous actions (e.g., whether drafts are held for approval vs. auto-sent), and independent hands-on validation of the full delegate→work→review loop is thin. Missing for 10: explicit review/approval workflow evidence, and richer independent hands-on accounts of multi-step autonomous task completion.

   • [claimed-docs] “Create custom shortcuts that trigger multi-step actions.”
   • [claimed-docs] “Martin can send you daily or weekly briefings via email.”
   • [claimed-docs] “Martin can proactively draft emails for you and send them on your behalf.”
   • [claimed-docs] “Martin can automatically label your emails and take follow up actions on your behalf.”
   • [claimed-docs] “Cc Martin on an email to schedule a meeting.”
   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”
   • [community] “A big piece of product feedback we got was 'I don't trust AI to take actions like sending texts/emails on my behalf if it's not 100% reliabl…”

   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

   Martin—none0/10

   Martin's documented capabilities cover calendar, email, Slack, notes, reminders, todos, and search-engine lookups, but nothing in the evidence describes it operating a web browser, navigating websites, or completing multi-step tasks on arbitrary sites on the user's behalf.

   • [claimed-docs] “Martin syncs with multiple search engines to find you the most relevant information.”
   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “Have Martin read, draft, and reply to emails in your inbox.”
   • [claimed-docs] “Have Martin read and send messages in Slack from your account.”
   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”

   proof ↗⚑ flag

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

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

   Martin~partialcommunity5/10

   Martin can act inside specific applications via integrations (calendar, email, Slack, notes, to-dos) rather than through general screen/GUI-level control of arbitrary desktop apps — it operates named services via API-like connections, not a computer-use style visual agent. A desktop app exists (martin-comm-4) but evidence only shows it syncing to-dos, not controlling arbitrary programs. Missing for 10: evidence of generic screen/vision-based computer control, ability to operate arbitrary (non-integrated) applications, and independent hands-on proof of this broader 'operate any app' capability.

   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “Have Martin read, draft, and reply to emails in your inbox.”
   • [claimed-docs] “Have Martin read and send messages in Slack from your account.”
   • [claimed-docs] “You can tell Martin to read, add, and edit your notes from any interface.”
   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”

   proof ↗⚑ flag

Tasks

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

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

   Martin~partialcommunity6/10

   Martin supports recurring background tasks (daily/weekly briefings, wake-up calls, email triage) and one-off scheduled reminders that ping the user via chosen interface, matching the core of the story. However, there's no unified 'task scheduler' concept with arbitrary custom recurring workflows beyond the specific built-in background tasks listed, and no independent verification of reliability for scheduled/recurring runs. missing for 10: evidence of general-purpose custom recurring task scheduling (not just fixed briefings/wake-up-calls), independent hands-on confirmation of reminder/briefing reliability, and any dashboard/management UI for viewing scheduled tasks.

   • [claimed-docs] “Tell Martin to remind you to do something, and he will ping you when the time comes.”
   • [claimed-docs] “Martin can send you daily or weekly briefings via email.”
   • [claimed-docs] “Martin can automatically label your emails and take follow up actions on your behalf.”
   • [claimed-docs] “Martin can call you at a specific time every morning to wake you up with the weather and your schedule.”
   • [claimed-docs] “Tell Martin to remind you to do something, and he will ping you at the specified time, via the specified interface.”
   • [community] “A big piece of product feedback we got was 'I don't trust AI to take actions like sending texts/emails on my behalf if it's not 100% reliabl…”

   proof ↗⚑ 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
   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

   Martin—none0/10

   Community evidence confirms a Martin desktop app exists (martin-comm-4), and docs mention in-app 'shortcuts' for multi-step actions (martin-docs-7), but there is no evidence of OS-level global keyboard shortcuts or any capability for Martin to read/access what's on the user's screen. missing for 10: evidence of OS-level hotkey integration, evidence of screen-reading/context capture, any documentation describing desktop-native system integration beyond a generic app shell.

   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”
   • [claimed-docs] “Create custom shortcuts that trigger multi-step actions.”

   proof ↗⚑ flag

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

   Martin—none0/10

   Martin's docs describe channel-based access (phone, SMS, WhatsApp, email, Slack, desktop) but no evidence of dedicated, full-featured native iOS/Android apps; a community comment explicitly asks 'I would try this if it had Android support! Is that planned?' indicating no Android app exists, and no iOS app is mentioned anywhere.

   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”
   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”
   • [community] “I would try this if it had Android support! Is that planned?”

   proof ↗⚑ flag

Custom bots

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

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

   Martin—none0/10

   Martin is a personal AI assistant with fixed integrations (calendar, email, Slack, todos, notes, reminders) and shortcuts, but there is no evidence of a feature to build a custom assistant with its own distinct instructions/persona and knowledge base, nor any sharing mechanism for such an assistant. missing for 10: custom assistant creation with configurable instructions/persona, custom knowledge base attachment, and sharing/publishing of a built assistant.

   ⚑ flag

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

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

   Martin~partialclaimed4/10

   Martin's docs show a few multi-item behaviors — e.g. forwarding an email with several events and having 'all of them' added to the calendar (martin-docs-23), and automatic email labeling/triage across an inbox (martin-docs-11) — which imply some batch-like processing, but there is no explicit bulk-operations feature (e.g. batch todo updates, mass note edits, multi-item scheduling command) described anywhere in the docs. missing for 10: explicit bulk-action tooling/API for operating on many items at once, first-party documentation of bulk operations, and independent confirmation of bulk-scale reliability.

   • [claimed-docs] “Got an email with events coming up? Forward it to Martin, and he'll add them all to your calendar.”
   • [claimed-docs] “Martin can automatically label your emails and take follow up actions on your behalf.”

   proof ↗⚑ flag

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

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

   Martin~partialclaimed6/10

   Martin ships several automatic, event-triggered behaviors (email triage that auto-labels and follows up, cc-to-schedule meeting creation, forwarded-email calendar parsing, proactive drafts, wake-up calls, briefings) which act like predefined automation rules, and 'custom shortcuts' let users define multi-step action sequences. However, there's no evidence of a general user-defined rule/trigger engine (e.g., 'if email from X arrives then do Y' configurable conditions) — the automations shown are fixed built-in behaviors rather than arbitrary user-authored event rules. Missing for 10: a documented custom rule/condition builder, evidence of arbitrary event-trigger definitions beyond built-in background tasks, and independent confirmation these automations fire reliably in practice.

   • [claimed-docs] “Create custom shortcuts that trigger multi-step actions.”
   • [claimed-docs] “Martin can automatically label your emails and take follow up actions on your behalf.”
   • [claimed-docs] “Cc Martin on an email to schedule a meeting.”
   • [claimed-docs] “Martin can proactively draft emails for you and send them on your behalf.”
   • [claimed-docs] “Martin can call you at a specific time every morning to wake you up with the weather and your schedule.”
   • [claimed-docs] “Got an email with events coming up? Forward it to Martin, and he'll add them all to your calendar.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

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

   Martin~partialclaimed6/10

   Martin ships several built-in recurring background jobs — daily/weekly briefings, daily wake-up calls, and automatic email triage — which are documented recurring workflows, and shortcuts allow custom multi-step actions. However, there's no evidence of a general-purpose, user-defined recurring job scheduler (e.g., custom cadence for arbitrary tasks/workflows beyond the fixed built-in recurring features). Missing for 10: user-configurable custom recurring schedules beyond the fixed briefing/wake-up-call cadence, and independent confirmation these recurring jobs run reliably at scale.

   • [claimed-docs] “Martin can send you daily or weekly briefings via email.”
   • [claimed-docs] “Martin can call you at a specific time every morning to wake you up with the weather and your schedule.”
   • [claimed-docs] “Martin can automatically label your emails and take follow up actions on your behalf.”
   • [claimed-docs] “Create custom shortcuts that trigger multi-step actions.”
   • [claimed-docs] “Tell Martin to remind you to do something, and he will ping you at the specified time, via the specified interface.”

   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

   Martin—none0/10

   Martin is a personal assistant agent (email, calendar, reminders, shortcuts) with no evidence of version history, review workflows, or rollback for its automations/shortcuts; docs describe creating shortcuts but nothing about versioning or undoing them. Missing for 10: version history UI, review/approval workflow, rollback mechanism.

   • [claimed-docs] “Create custom shortcuts that trigger multi-step actions.”

   proof ↗⚑ flag

Connectors

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

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

   Martin—none0/10

   Evidence shows Martin ships a small fixed set of first-party integrations (Calendar, Inbox, Slack) rather than a browsable directory/marketplace of third-party apps and connectors that a power-user can explore and add. No docs, UI, or community mentions describe an app directory or connector marketplace.

   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “Have Martin read, draft, and reply to emails in your inbox.”
   • [claimed-docs] “Have Martin read and send messages in Slack from your account.”

   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

   Martin~partialclaimed5/10

   Martin has well-documented calendar and email (inbox) integrations letting it read, draft, reply, and add events on the user's behalf, plus a general search capability across connected sources. However, no evidence mentions a cloud drive (e.g., Google Drive/Dropbox) connector, so the story's full connector set is only partially covered. missing for 10: cloud drive integration, independent verification that search actually spans all connected sources.

   • [claimed-docs] “Have Martin read, create, and update events in your calendar.”
   • [claimed-docs] “Have Martin read, draft, and reply to emails in your inbox.”
   • [claimed-docs] “Martin syncs with multiple search engines to find you the most relevant information.”
   • [claimed-docs] “Once connected, you can tell Martin to add an event to your calendar, and he will add it at the specified time with the specified details.”
   • [claimed-docs] “Once connected, you can tell Martin to read, draft, and reply to emails on your behalf.”
   • [claimed-docs] “Got an email with events coming up? Forward it to Martin, and he'll add them all to your calendar.”

   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

   Martin—none0/10

   Martin is a personal-assistant product focused on calendar, email, Slack, reminders, notes, and todos; no evidence anywhere in the pack mentions document, spreadsheet, or PDF upload/analysis capabilities. This is a plausible axis for an AI assistant but there's no supporting documentation or community mention of file/document analysis features.

   ⚑ flag

Memory

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

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

   Martin~partialclaimed4/10

   Martin's notes, to-dos, and reminders (martin-docs-6, martin-docs-22, martin-docs-5) provide persistent storage that Martin can read back across interfaces, giving it some ability to carry information forward. However, there is no explicit documentation of the assistant automatically recalling relevant context from prior conversations and applying it in new, unrelated chats — memory here is user-invoked (explicit notes) rather than an automatic contextual-memory feature. Missing for 10: explicit memory/context-recall feature description, evidence of automatic application of past-conversation context in new sessions, independent confirmation of this behavior.

   • [claimed-docs] “You can tell Martin to read, add, and edit your notes from any interface.”
   • [claimed-docs] “Call Martin and say "Note down everything we talked about on this call and call it 'Brain Dump'."”
   • [claimed-docs] “You can tell Martin to add, edit, and check off your to-dos on your behalf from any interface.”
   • [claimed-docs] “Tell Martin to remind you to do something, and he will ping you at the specified time, via the specified interface.”

   proof ↗⚑ flag

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

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

   Martin—none0/10

   No evidence in the pack describes a persistent custom-instructions or preferences feature that shapes all of Martin's responses; the docs cover integrations, reminders, notes, and background tasks but nothing about setting persona/style preferences persistently.

   ⚑ flag

Images

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

   Martin—none0/10

   No evidence in the pack mentions image, screenshot, or photo interpretation capabilities; Martin's documented features focus on text-based channels (email, Slack, SMS, calendar, notes, reminders) with no mention of vision/multimodal input handling.

   ⚑ 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

   Martin~partialclaimed6/10

   Martin supports real phone-call interactions — users can call Martin to dictate notes, and Martin can call users for wake-up briefings — indicating a live voice channel exists (martin-docs-22, martin-docs-24, martin-docs-12). However, there is no documentation or independent evidence describing the naturalness, latency, or conversational fluidity of these voice interactions, and community feedback focuses on text/action reliability rather than voice quality. Missing for 10: hands-on/independent evidence of real-time conversational voice quality, documentation of voice-specific features like interruption handling or natural turn-taking.

   • [claimed-docs] “Call Martin and say "Note down everything we talked about on this call and call it 'Brain Dump'."”
   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”
   • [claimed-docs] “Martin can call you at a specific time every morning to wake you up with the weather and your schedule.”

   proof ↗⚑ 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

   Martin—none0/10

   Martin's documented surface is entirely conversational interfaces (email, Slack, phone, SMS, WhatsApp) with no mention of a public/developer API; explicit probes for an OpenAPI/swagger spec at all standard paths returned 404, indicating no programmatic API exists to mirror these UI capabilities.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.trymartin.com/openapi.json, https://docs.trymartin.com/swagger.json, https://docs.tryma…”
   • [claimed-docs] “Martin is reachable through all your communication channels, including phone, SMS, WhatsApp, email, and Slack.”

   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

   Martin—none0/10

   No evidence anywhere in the pack of a data export feature or open-format data portability; Martin's docs focus on integrations, reminders, and briefings but never mention exporting user data or account deletion/export tools.

   ⚑ 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

   Martin—none0/10

   No evidence Martin's source code is available under any license; a community comment explicitly calls for Martin to 'make that system open source' as a trust-building step, implying it currently is not.

   • [community] “You should create a system where you cannot access user data, and it can never be shared with third parties. Make that system open source to…”

   proof ↗⚑ 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

   Martin—none0/10

   Martin is offered exclusively as a cloud-based assistant (email, Slack, calendar interfaces, cloud-based agent per martin-comm-4); no evidence of a self-hostable core product, open-source release, or on-prem deployment option. One community comment (martin-comm-3) even calls for open-sourcing the data-handling system, implying it is not currently available.

   • [community] “oh, martin desktop is finally here! I use Martin to manage my todo list while i'm coding (on an hourly basis) - having it aside VSC is so ha…”
   • [community] “You should create a system where you cannot access user data, and it can never be shared with third parties. Make that system open source to…”

   proof ↗⚑ 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

   Martin—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or storage location controls; docs focus entirely on assistant features and integrations. Community comments raise general privacy/security concerns but do not address data residency options. missing for 10: any mention of region selection, data residency policy, or storage location controls.

   • [community] “I want this, but very concerned about the security and privacy - you're talking about getting my most personal of personals (email, calendar…”
   • [community] “You should create a system where you cannot access user data, and it can never be shared with third parties. Make that system open source to…”

   proof ↗⚑ 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

   Martin—none0/10

   No evidence pack item addresses AI-training data opt-out or data-usage policy; community comments explicitly raise privacy/trust concerns without any documented answer or control from Martin. Missing for 10: any privacy policy statement, opt-out setting, or documented no-training-data commitment.

   • [community] “I want this, but very concerned about the security and privacy - you're talking about getting my most personal of personals (email, calendar…”
   • [community] “You should create a system where you cannot access user data, and it can never be shared with third parties. Make that system open source to…”

   proof ↗⚑ 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

   Martin—none0/10

   No evidence describes data retention policies, deletion controls, export tools, or privacy settings; community comments even raise unaddressed concerns about lack of transparency around data handling. Missing for 10: any documentation of data retention periods, user-initiated deletion mechanism, or privacy controls.

   • [community] “I want this, but very concerned about the security and privacy - you're talking about getting my most personal of personals (email, calendar…”
   • [community] “You should create a system where you cannot access user data, and it can never be shared with third parties. Make that system open source to…”

   proof ↗⚑ 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

   Martin—none0/10

   No evidence of any telemetry opt-out, privacy settings, or data collection controls; community comments even raise unresolved privacy/trust concerns (martin-comm-2, martin-comm-3) with no documented response or opt-out mechanism.

   • [community] “I want this, but very concerned about the security and privacy - you're talking about getting my most personal of personals (email, calendar…”
   • [community] “You should create a system where you cannot access user data, and it can never be shared with third parties. Make that system open source to…”

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

   Martin—none0/10

   Martin's docs mention a basic search capability that 'syncs with multiple search engines to find relevant information' (martin-docs-8), but there is no evidence of an autonomous multi-source deep-research mode that returns a structured, cited report — no mention of citation formatting, report generation, or a dedicated 'deep research' feature.

   • [claimed-docs] “Martin syncs with multiple search engines to find you the most relevant information.”

   proof ↗⚑ flag

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

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

   Martin~partialclaimed4/10

   Martin claims to sync with multiple search engines to find relevant information (martin-docs-8), suggesting web-grounded answers, but there is no evidence of citation formatting, source linking, or hands-on verification that answers include traceable citations back to web sources. Missing for 10: documentation or examples showing inline citations/source links, independent corroboration of search-grounded answer quality, and detail on which search engines/sources are used.

   • [claimed-docs] “Martin syncs with multiple search engines to find you the most relevant information.”

   proof ↗⚑ flag

Admin

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

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

   Martin—none0/10

   Martin's evidence pack is entirely about individual personal-assistant features (calendar, email, Slack, reminders, to-dos) with no mention of organization workspaces, member management, permission controls, or data-policy settings for teams. missing for 10: any admin console, member/role management, workspace-level permissions, or data governance policy documentation.

   ⚑ 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

   Martin—none0/10

   No evidence in the pack mentions data export, chat history download, or account data portability features; community comments even raise privacy concerns without any mention of export tools. Missing for 10: any documentation or feature reference to exporting chat history or account data, data portability API, or GDPR-style export mechanism.

   ⚑ 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

   Martin—none0/10

   No evidence in the pack mentions any setting, policy, or statement about whether user conversations/data are used for model training; community comments explicitly raise privacy/trust concerns without any documented opt-out or training-control mechanism (martin-comm-2, martin-comm-3).

   • [community] “I want this, but very concerned about the security and privacy - you're talking about getting my most personal of personals (email, calendar…”
   • [community] “You should create a system where you cannot access user data, and it can never be shared with third parties. Make that system open source to…”

   proof ↗⚑ flag