{ "data": { "a": { "slug": "grok-bot", "name": "Grok Bot", "vendor": "SpaceXAI and Cursor (Anysphere, Inc.)", "vendorUrl": "https://x.ai/bot", "kind": "platform", "category": "personal-assistants", "summary": "Hosted assistant from SpaceXAI and Cursor. Named Bots work on a persistent cloud computer with a browser, files and terminal, reached from desktop and mobile apps, Slack and X, with routines that run on a schedule.", "url": "https://www.anchorterminal.com/tools/grok-bot", "markdownUrl": "https://www.anchorterminal.com/tools/grok-bot.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/grok-bot.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/grok-bot.json", "license": "Proprietary", "transports": [], "packages": [], "auth": "mixed", "authNotes": "A person signs in with a Cursor account in the browser, or with Sign in with Grok for a Grok Business seat. SAML 2.0 single sign-on applies to teams, and SCIM is Enterprise only. Connectors are added from Connect apps and authenticated in the browser by OAuth, or configured with a key or token. OAuth tokens stay on Cursor's backend. For passwords, passkeys, two-factor codes, CAPTCHAs and payment confirmations the Bot hands the computer to the owner, and a secure secret request masks a value and keeps it out of the transcript and away from the model. Browser sessions then persist on the cloud computer shared by all of the user's Bots (https://docs.x.ai/grok-bot/security; https://docs.x.ai/grok-bot/approvals-security-and-privacy; https://docs.x.ai/grok-bot/team-bots). No API key or public API for the assistant was found. An Admin API for team settings is linked from the docs and was not read.", "pricing": "paid", "pricingNotes": "No separate subscription. Grok Bot is included with every paid individual Cursor plan (Pro, Pro+, Ultra) and with Cursor Teams, or through a linked individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, or a seat on a self-serve Grok Business plan. Cursor's pricing page shows Individual at $20 a month and Teams at $40 a user a month. The Pro+ and Ultra prices sit behind tabs our reader did not see. Each tier includes weekly usage with no amount published, metered by agent steps and tokens. After that, on-demand usage is billed through Cursor up to a monthly limit the owner sets, which is not a hard stop in the middle of a run. A free trial is a usage credit with a 7-day window and never becomes a paid plan. SuperGrok Lite is not included, and a SuperGrok link cannot be undone or moved (https://cursor.com/help/grok-bot/plans; https://cursor.com/pricing; checked 2026-10-12).", "priceSummary": "$20 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Grok Bot docs, the plans page or the Grok Bot Terms (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://docs.x.ai/grok-bot/overview", "llmsTxt": "https://docs.x.ai/llms.txt", "capabilities": [ "assistant.proactive", "assistant.accounts", "assistant.memory", "assistant.messaging", "agent.mcp-client" ], "tags": [ "hosted", "closed-source", "desktop-app", "mobile-app", "computer-use", "scheduled-routines", "slack", "status-page", "iso27001", "soc2", "llms-txt", "paid" ], "graded": true, "anchor": { "graded": true, "score": 45.2, "grade": "E", "agentReady": false, "rank": 893, "ranked": true, "rankOf": 986, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 20, "payments": 25, "reliability": 40, "schema": 40, "security": 68, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": 0, "verdict": "Connector tokens stay on Cursor's backend and each user gets a separate microVM, with approvals, drafts and a review model before risky actions. All of a user's Bots share one computer and its sign-ins, the review model skips memory writes, and the status page shows seven major Grok Bot incidents since 3 September 2026.", "bestFor": "A person or team already paying for Cursor or SuperGrok who wants named assistants that keep working on a cloud computer, with routines and Slack or X entry points, and who will write approval rules.", "strengths": [ "Connector OAuth tokens stay on Cursor's backend. Bots call tools without receiving them, and tokens are never stored on the cloud computer", "Each user's work runs in a dedicated Firecracker microVM. A Bot has no identity of its own and holds no more access than the signed-in member", "Approvals from routines, triggers or other Bots expire after about 10 minutes and the action does not run", "Email and Slack messages can appear as editable drafts with Send and Discard buttons, and passwords, two-factor codes and payment confirmations are handed to the owner", "Markdown copies of every docs page and an llms.txt, with a security page that states what the controls do not cover" ], "weaknesses": [ "All of one user's Bots share one cloud computer, with its files, browser sessions and command-line credentials. The docs say separate Bots are not a security boundary", "The review model does not check memory writes or most settings changes, and the Grok Bot Terms call approval controls aids only", "Deleting a Bot leaves shared files and browser sessions on the computer. No way to view or delete single memories was found in the docs read", "Seven incidents marked major named Grok Bot on status.cursor.com between 3 September and 6 October 2026, the longest about six and a half hours", "Audit logs, Action Recording, network allowlists and enforced review rules are Enterprise only. Other teams default to allow-all network access", "Cursor chooses the model with no picker and no fixed set of model vendors, and no Grok Bot changelog was found" ], "agentNotes": [ "State in each request what the Bot may change and where it must stop. Which actions pause for approval depends on the tool, the risk and the owner's Auto-review rules", "Add narrow Ask first rules for sending, publishing, purchasing and deleting. Ask first wins over Allow automatically when both match", "Treat any sign-in or file on the cloud computer as available to every Bot on the account. Give a workload its own Cursor user when it needs separate credentials", "Run Test run with safe inputs. A test run performs real work and can call connected tools", "To remove access, pause routines, sign out of sites on the computer, uninstall connectors and revoke them at the source service. Deleting the Bot is not enough" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.2 } ], "editorialScores": { "ergonomics": 50, "maintenance": 20, "payments": 25, "reliability": 40, "schema": 40, "security": 68, "transparency": 48 }, "provenanceScore": 84 }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/grok-bot" }, "sameCompany": [ "cursor-cli" ], "area": "frameworks", "unitPrices": [ { "item": "Cursor Individual plan, as shown on the pricing page", "unit": "month", "usd": 20, "note": "Includes Grok Bot with weekly usage. On-demand usage extra" }, { "item": "Cursor Teams plan", "unit": "seat-month", "usd": 40, "note": "Includes Grok Bot for every member. On-demand usage on by default" } ], "provenance": { "legalEntity": "Anysphere, Inc.", "domain": "cursor.com", "domainRegistered": "1995-12-20", "endpointOnVendorDomain": null, "terms": "https://cursor.com/en-US/terms/grok-bot", "privacy": "https://cursor.com/privacy", "statusPage": "https://status.cursor.com", "changelog": "", "securityTxt": "valid", "checked": "2026-10-12", "notes": [ "The Grok Bot Terms (last updated 3 September 2026) supplement the agreement that governs the customer's use of the Services and define the Provider as the entity under that agreement. For a Cursor account that agreement is Cursor's Terms of Service (last updated 3 September 2026), which name Anysphere, Inc., 2261 Market Street STE 86466, San Francisco, CA 94114 (https://cursor.com/terms-of-service).", "The product docs are on docs.x.ai, titled SpaceXSI Docs, and name SpaceXAI. The Grok Bot Terms say they create no contractual relationship between the customer and any affiliate of the Provider. No page read states how the two companies are related.", "The privacy policy (last updated 11 October 2026) is Anysphere's and says it does not apply where Anysphere processes data for commercial customers as a processor.", "cursor.com/.well-known/security.txt gives a GitHub security page and security-reports@cursor.com as contacts and has no Expires field.", "The docs name api2.cursor.sh and *.cursorvm.com as the hosts the app and the cloud computer use. There is no endpoint an outside agent calls.", "RDAP for cursor.com gives a registration date of 1995-12-20.", "No changelog for Grok Bot was found. Cursor's changelog entries from 29 July to 6 October 2026 do not mention it.", "docs.x.ai's robots.txt allows every path with Content-Signal ai-input=yes. x.ai's robots.txt does the same, but x.ai/bot and status.x.ai answered HTTP 403." ], "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/grok-bot.json", "live": { "slug": "grok-bot", "vendorStatus": { "page": "https://status.cursor.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-12T18:56:36.692375788Z" }, "updatedAt": "2026-10-12T18:56:36.692375788Z" } }, "answer": "Grok Bot scores 45.2 (E) on agent readiness against Zo Computer's 43.1 (E), and leads in 4 of 7 scored categories. Zo Computer leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "zo-computer", "name": "Zo Computer", "vendor": "Zo Computer Company", "vendorUrl": "https://www.zo.computer", "kind": "http-api", "category": "personal-assistants", "summary": "Hosted personal assistant from Zo Computer Company that runs on a cloud Linux computer assigned to each user. It answers by web chat, SMS, email, Slack, Discord and Telegram, runs scheduled automations, and has an HTTP API and MCP endpoint.", "url": "https://www.anchorterminal.com/tools/zo-computer", "markdownUrl": "https://www.anchorterminal.com/tools/zo-computer.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zo-computer.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zo-computer.json", "license": "Proprietary service under Zo Computer Company's terms of service", "transports": [ "http" ], "remoteUrl": "https://api.zo.computer/mcp", "packages": [], "auth": "api-key", "authNotes": "A bearer access token with the prefix `zo_sk_`, created by the owner under Settings \u003e Advanced and shown once. The same token is used for the HTTP API and the MCP endpoint, and both guides say it grants full access to the workspace. No scoped, read-only or expiring token and no OAuth flow for outside clients were found in the docs. Whether a token can be revoked individually is not stated on the pages read. `GET /models/catalog` needs no authentication. Sign-up is in a browser behind Cloudflare Turnstile.", "pricing": "freemium", "pricingNotes": "Free Trial is $0 for 14 days with no card, then ordinary computer access ends. Basic is $18 a month with $10 of AI credit, Pro $64 with $40 and Ultra $200 with $100. API and MCP access are included on all plans. Chat is billed at per-token rates on the models pages, which we did not read, and media at fixed per-request prices from $0.035. A user's own model API key can replace Zo-billed usage (checked 2026-10-12).", "priceSummary": "$18 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API guide, the OpenAPI file, the billing guide or the pricing page, checked 12 October 2026. Billing is a Stripe subscription with prepaid credits.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://www.zo.computer/guide", "llmsTxt": "https://www.zo.computer/llms.txt", "openapi": "https://www.zo.computer/docs-assets/openapi.json", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "agent.mcp-client" ], "tags": [ "official", "hosted", "closed-source", "assistant", "mcp", "openapi", "llms-txt", "free-trial" ], "lastRelease": "2026-09-14", "graded": true, "anchor": { "graded": true, "score": 43.1, "grade": "E", "agentReady": false, "rank": 911, "ranked": true, "rankOf": 986, "categoryRank": 13, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 34, "maintenance": 68, "payments": 40, "reliability": 15, "schema": 73, "security": 37, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": 0, "verdict": "Zo publishes an OpenAPI file, Markdown docs, plan prices and a named list of the providers that receive user content. One access token grants full access to the workspace, no approval step before sending or buying was found in the reviewed docs, and no status page, rate limit or SLA is published.", "bestFor": "One person who wants a hosted assistant with its own Linux machine, reachable by text message and chat apps, and who accepts that the assistant acts on connected accounts without a documented approval step.", "strengths": [ "OpenAPI 3.1 file, llms.txt and a Markdown copy of every guide and reference page are public", "Persona permissions remove tools from a conversation, with 19 named scopes and a Read only preset", "The security page names each infrastructure, inference and tool provider and states which can see user content", "Plan prices, included AI credit and per-request media prices are public, with a 14-day trial that needs no card", "Dated weekly changelog, with nine weekly entries between 20 July and 14 September 2026" ], "weaknesses": [ "The access token for the API and MCP endpoint grants full access to the workspace, with no scoped or read-only token documented", "No approval step before sending mail, posting or buying was found. The browser guide says Zo can buy and send on signed-in sites", "No status page, incident history, rate limit figures or SLA were found on the pages read", "The privacy policy lists only email address, trackers, usage data and SMS data, and does not describe workspace files, memory or connected accounts", "Memory storage and deletion are not documented beyond a design aim and whole-account deletion or factory reset" ], "agentNotes": [ "Send `POST https://api.zo.computer/zo/ask` with `Authorization: Bearer zo_sk_...` and an `input` string. The owner creates the token under Settings \u003e Advanced", "Pass `persona_id` for a persona with a narrow tool set. The token itself carries every permission the owner has", "Set `memory_mode` to `off` to keep workspace memory out of a request. The field is in the OpenAPI file and absent from the API guide", "Do not retry `/zo/ask` blindly after a timeout. No idempotency key is documented and the request may already have sent a message", "Append `.md` to any guide or reference URL for Markdown" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.1 } ], "editorialScores": { "ergonomics": 34, "maintenance": 68, "payments": 40, "reliability": 15, "schema": 73, "security": 37, "transparency": 46 }, "provenanceScore": 73 }, "connect": { "http": "curl -X POST https://api.zo.computer/zo/ask \\\n -H \"Authorization: Bearer zo_sk_your_key_here\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"input\": \"Hello, Zo!\"}'", "claudeCode": "claude mcp add --transport http zo https://api.zo.computer/mcp --header \"Authorization: Bearer zo_sk_your_key_here\"", "config": { "mcpServers": { "zo": { "headers": { "Authorization": "Bearer zo_sk_your_key_here" }, "type": "http", "url": "https://api.zo.computer/mcp" } } } }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/zo-computer" }, "area": "frameworks", "unitPrices": [ { "item": "Basic plan", "unit": "month", "usd": 18, "note": "Includes $10 of AI credit a month." }, { "item": "Pro plan", "unit": "month", "usd": 64, "note": "Includes $40 of AI credit a month." }, { "item": "Ultra plan", "unit": "month", "usd": 200, "note": "Includes $100 of AI credit a month." } ], "provenance": { "legalEntity": "Zo Computer Company", "domain": "zo.computer", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.zo.computer/reference/information/terms", "privacy": "https://www.zo.computer/reference/information/privacy-policy", "statusPage": "", "changelog": "https://www.zo.computer/updates", "securityTxt": "valid", "checked": "2026-10-12", "notes": [ "The terms of service name Zo Computer Company at 13 Grattan St Unit 102, Brooklyn, NY 11206, under New York law. They were last updated on 8 August 2025.", "The terms refer to an Acceptable Use Policy that we did not find linked from the pages read.", "security.txt at www.zo.computer/.well-known/security.txt gives a contact, a policy link and an expiry of 8 April 2027.", "No status page is linked from the home page, the docs index, the security page or the help centre home page.", "The API and MCP endpoint are on api.zo.computer. The domain's registration date was not looked up.", "The X handle is the one the home page footer links." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zo-computer.json", "live": { "slug": "zo-computer", "probe": { "target": "https://api.zo.computer/mcp", "method": "get", "lastAt": "2026-10-12T19:01:35.563750129Z", "lastOk": true, "lastStatus": 405, "lastMs": 472, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 320, "p95ms24h": 1228, "samples24h": 18, "samples30d": 18, "days": [ { "date": "2026-10-12", "probes": 18, "ok": 18 } ] }, "updatedAt": "2026-10-12T19:01:35.563750129Z" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "SpaceXAI and Cursor (Anysphere, Inc.)", "b": "Zo Computer Company", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.zo.computer/mcp", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary", "b": "Proprietary service under Zo Computer Company's terms of service", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-09-14", "name": "Last release" }, { "a": "2026-09-03", "b": "2025-08-08", "name": "Terms last updated" }, { "a": "2026-09-29", "b": "2026-05-20", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Grok Bot scores 45.2 (E) on agent readiness against Zo Computer's 43.1 (E), and leads in 4 of 7 scored categories. Zo Computer leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Grok Bot or Zo Computer?" }, { "answer": "No hosted endpoint is listed for Grok Bot. Zo Computer has a hosted endpoint at https://api.zo.computer/mcp.", "question": "Can an agent call Grok Bot and Zo Computer without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 40 against 15", "Agent ergonomics, 50 against 34", "Security \u0026 auth, 68 against 37", "Transparency \u0026 trust, 66 against 60" ], "also": null, "goodFor": "A person or team already paying for Cursor or SuperGrok who wants named assistants that keep working on a cloud computer, with routines and Slack or X entry points, and who will write approval rules.", "slug": "grok-bot", "watchFor": "All of one user's Bots share one cloud computer, with its files, browser sessions and command-line credentials. The docs say separate Bots are not a security boundary" }, { "aheadOn": [ "Schema \u0026 documentation, 73 against 40", "Payments \u0026 pricing, 40 against 25", "Maintenance \u0026 community, 68 against 20" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "One person who wants a hosted assistant with its own Linux machine, reachable by text message and chat apps, and who accepts that the assistant acts on connected accounts without a documented approval step.", "slug": "zo-computer", "watchFor": "The access token for the API and MCP endpoint grants full access to the workspace, with no scoped or read-only token documented" } ], "job": { "capability": "assistant.proactive", "name": "Assistant proactive" }, "others": [ { "json": "https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.json", "title": "AstrBot vs Grok Bot", "url": "https://www.anchorterminal.com/compare/astrbot-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/astrbot-vs-zo-computer.json", "title": "AstrBot vs Zo Computer", "url": "https://www.anchorterminal.com/compare/astrbot-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.json", "title": "CowAgent vs Grok Bot", "url": "https://www.anchorterminal.com/compare/cowagent-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/cowagent-vs-zo-computer.json", "title": "CowAgent vs Zo Computer", "url": "https://www.anchorterminal.com/compare/cowagent-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/gaia-vs-grok-bot.json", "title": "GAIA vs Grok Bot", "url": "https://www.anchorterminal.com/compare/gaia-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/gaia-vs-zo-computer.json", "title": "GAIA vs Zo Computer", "url": "https://www.anchorterminal.com/compare/gaia-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.json", "title": "Gemini Spark vs Grok Bot", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot" }, { "json": "https://www.anchorterminal.com/compare/gemini-spark-vs-zo-computer.json", "title": "Gemini Spark vs Zo Computer", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-haven.json", "title": "Grok Bot vs Haven", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-haven" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.json", "title": "Grok Bot vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-instinct.json", "title": "Grok Bot vs Instinct", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-instinct" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.json", "title": "Grok Bot vs IronClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-leon.json", "title": "Grok Bot vs Leon", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-leon" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy.json", "title": "Grok Bot vs Lindy", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-nanobot.json", "title": "Grok Bot vs nanobot", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.json", "title": "Grok Bot vs NanoClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-openai-dots.json", "title": "Grok Bot vs Dots", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-openclaw.json", "title": "Grok Bot vs OpenClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-openclaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.json", "title": "Grok Bot vs PicoClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-poke.json", "title": "Grok Bot vs Poke", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-qwenpaw.json", "title": "Grok Bot vs QwenPaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/grok-bot-vs-zeroclaw.json", "title": "Grok Bot vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-zeroclaw" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-zo-computer.json", "title": "Haven vs Zo Computer", "url": "https://www.anchorterminal.com/compare/haven-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer.json", "title": "Hermes Agent vs Zo Computer", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/instinct-vs-zo-computer.json", "title": "Instinct vs Zo Computer", "url": "https://www.anchorterminal.com/compare/instinct-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-zo-computer.json", "title": "IronClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/leon-vs-zo-computer.json", "title": "Leon vs Zo Computer", "url": "https://www.anchorterminal.com/compare/leon-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-zo-computer.json", "title": "Lindy vs Zo Computer", "url": "https://www.anchorterminal.com/compare/lindy-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.json", "title": "nanobot vs Zo Computer", "url": "https://www.anchorterminal.com/compare/nanobot-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/nanoclaw-vs-zo-computer.json", "title": "NanoClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/nanoclaw-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/openai-dots-vs-zo-computer.json", "title": "Dots vs Zo Computer", "url": "https://www.anchorterminal.com/compare/openai-dots-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/openclaw-vs-zo-computer.json", "title": "OpenClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/openclaw-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer.json", "title": "PicoClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/poke-vs-zo-computer.json", "title": "Poke vs Zo Computer", "url": "https://www.anchorterminal.com/compare/poke-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/qwenpaw-vs-zo-computer.json", "title": "QwenPaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/qwenpaw-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/zeroclaw-vs-zo-computer.json", "title": "ZeroClaw vs Zo Computer", "url": "https://www.anchorterminal.com/compare/zeroclaw-vs-zo-computer" } ], "scores": [ { "by": 25, "edge": "grok-bot", "grok-bot": 40, "key": "reliability", "name": "Reliability", "weight": 16, "zo-computer": 15 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 33, "edge": "zo-computer", "grok-bot": 40, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "zo-computer": 73 }, { "by": 16, "edge": "grok-bot", "grok-bot": 50, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "zo-computer": 34 }, { "by": 31, "edge": "grok-bot", "grok-bot": 68, "key": "security", "name": "Security \u0026 auth", "weight": 14, "zo-computer": 37 }, { "by": 15, "edge": "zo-computer", "grok-bot": 25, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "zo-computer": 40 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 48, "edge": "zo-computer", "grok-bot": 20, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "zo-computer": 68 }, { "by": 6, "edge": "grok-bot", "grok-bot": 66, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "zo-computer": 60 } ], "summary": "Grok Bot scores 45.2 (E) on agent readiness against Zo Computer's 43.1 (E), and leads in 4 of 7 scored categories. Zo Computer leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do assistant proactive.", "verdicts": { "grok-bot": "Connector tokens stay on Cursor's backend and each user gets a separate microVM, with approvals, drafts and a review model before risky actions. All of a user's Bots share one computer and its sign-ins, the review model skips memory writes, and the status page shows seven major Grok Bot incidents since 3 September 2026.", "zo-computer": "Zo publishes an OpenAPI file, Markdown docs, plan prices and a named list of the providers that receive user content. One access token grants full access to the workspace, no approval step before sending or buying was found in the reviewed docs, and no status page, rate limit or SLA is published." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer", "json": "https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.md", "slim": "https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.min.md" }, "markdown": "Grok Bot scores 45.2 (E) on agent readiness against Zo Computer's 43.1 (E), and leads in 4 of 7 scored categories. Zo Computer leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do assistant proactive.\n\n- Grok Bot: grade E, 45.2/100, rank #893 of 986. Markdown https://www.anchorterminal.com/tools/grok-bot.md · JSON https://www.anchorterminal.com/api/v1/tools/grok-bot.json\n- Zo Computer: grade E, 43.1/100, rank #911 of 986. Markdown https://www.anchorterminal.com/tools/zo-computer.md · JSON https://www.anchorterminal.com/api/v1/tools/zo-computer.json\n- Best AI personal assistants that act for one person: https://www.anchorterminal.com/best/personal-assistants/index.md\n- All 190 assistants comparisons: https://www.anchorterminal.com/compare/personal-assistants/index.md\n\n## Which one, for what\n\n### Grok Bot (E)\n\nGood for: A person or team already paying for Cursor or SuperGrok who wants named assistants that keep working on a cloud computer, with routines and Slack or X entry points, and who will write approval rules.\n\nAhead on:\n- Reliability, 40 against 15\n- Agent ergonomics, 50 against 34\n- Security \u0026 auth, 68 against 37\n- Transparency \u0026 trust, 66 against 60\n\nWatch for: All of one user's Bots share one cloud computer, with its files, browser sessions and command-line credentials. The docs say separate Bots are not a security boundary\n\n### Zo Computer (E)\n\nGood for: One person who wants a hosted assistant with its own Linux machine, reachable by text message and chat apps, and who accepts that the assistant acts on connected accounts without a documented approval step.\n\nAhead on:\n- Schema \u0026 documentation, 73 against 40\n- Payments \u0026 pricing, 40 against 25\n- Maintenance \u0026 community, 68 against 20\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: The access token for the API and MCP endpoint grants full access to the workspace, with no scoped or read-only token documented\n\n\n## Score by category\n\n| Category | Weight | Grok Bot | Zo Computer | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 15 | Grok Bot +25 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 73 | Zo Computer +33 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 34 | Grok Bot +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 37 | Grok Bot +31 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 40 | Zo Computer +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 68 | Zo Computer +48 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 60 | Grok Bot +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.2 · E** | **43.1 · E** | |\n\n## Facts side by side\n\n| Fact | Grok Bot | Zo Computer |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | SpaceXAI and Cursor (Anysphere, Inc.) | Zo Computer Company |\n| Hosted endpoint | no (local only) | `https://api.zo.computer/mcp` |\n| Transports | | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary | Proprietary service under Zo Computer Company's terms of service |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-09-14 |\n| Terms last updated | 2026-09-03 | 2025-08-08 |\n| Privacy policy last updated | 2026-09-29 | 2026-05-20 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## Verdicts\n\n**Grok Bot.** Connector tokens stay on Cursor's backend and each user gets a separate microVM, with approvals, drafts and a review model before risky actions. All of a user's Bots share one computer and its sign-ins, the review model skips memory writes, and the status page shows seven major Grok Bot incidents since 3 September 2026.\n\n**Zo Computer.** Zo publishes an OpenAPI file, Markdown docs, plan prices and a named list of the providers that receive user content. One access token grants full access to the workspace, no approval step before sending or buying was found in the reviewed docs, and no status page, rate limit or SLA is published.\n\n## Before you call either\n\n### Grok Bot\n\n1. State in each request what the Bot may change and where it must stop. Which actions pause for approval depends on the tool, the risk and the owner's Auto-review rules\n2. Add narrow Ask first rules for sending, publishing, purchasing and deleting. Ask first wins over Allow automatically when both match\n3. Treat any sign-in or file on the cloud computer as available to every Bot on the account. Give a workload its own Cursor user when it needs separate credentials\n4. Run Test run with safe inputs. A test run performs real work and can call connected tools\n5. To remove access, pause routines, sign out of sites on the computer, uninstall connectors and revoke them at the source service. Deleting the Bot is not enough\n\n### Zo Computer\n\n1. Send `POST https://api.zo.computer/zo/ask` with `Authorization: Bearer zo_sk_...` and an `input` string. The owner creates the token under Settings \u003e Advanced\n2. Pass `persona_id` for a persona with a narrow tool set. The token itself carries every permission the owner has\n3. Set `memory_mode` to `off` to keep workspace memory out of a request. The field is in the OpenAPI file and absent from the API guide\n4. Do not retry `/zo/ask` blindly after a timeout. No idempotency key is documented and the request may already have sent a message\n5. Append `.md` to any guide or reference URL for Markdown\n\n## Questions\n\n### Which is better for AI agents, Grok Bot or Zo Computer?\n\nGrok Bot scores 45.2 (E) on agent readiness against Zo Computer's 43.1 (E), and leads in 4 of 7 scored categories. Zo Computer leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.\n\n### Can an agent call Grok Bot and Zo Computer without installing anything?\n\nNo hosted endpoint is listed for Grok Bot. Zo Computer has a hosted endpoint at https://api.zo.computer/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grok-bot\", \"b\": \"zo-computer\"}`. From a terminal: `anchor compare grok-bot zo-computer`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grok-bot.json and https://www.anchorterminal.com/api/v1/tools/zo-computer.json\n\n## Other comparisons with Grok Bot or Zo Computer\n\n- [AstrBot vs Grok Bot](https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.md)\n- [AstrBot vs Zo Computer](https://www.anchorterminal.com/compare/astrbot-vs-zo-computer.md)\n- [CowAgent vs Grok Bot](https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.md)\n- [CowAgent vs Zo Computer](https://www.anchorterminal.com/compare/cowagent-vs-zo-computer.md)\n- [GAIA vs Grok Bot](https://www.anchorterminal.com/compare/gaia-vs-grok-bot.md)\n- [GAIA vs Zo Computer](https://www.anchorterminal.com/compare/gaia-vs-zo-computer.md)\n- [Gemini Spark vs Grok Bot](https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.md)\n- [Gemini Spark vs Zo Computer](https://www.anchorterminal.com/compare/gemini-spark-vs-zo-computer.md)\n- [Grok Bot vs Haven](https://www.anchorterminal.com/compare/grok-bot-vs-haven.md)\n- [Grok Bot vs Hermes Agent](https://www.anchorterminal.com/compare/grok-bot-vs-hermes-agent.md)\n- [Grok Bot vs Instinct](https://www.anchorterminal.com/compare/grok-bot-vs-instinct.md)\n- [Grok Bot vs IronClaw](https://www.anchorterminal.com/compare/grok-bot-vs-ironclaw.md)\n- [Grok Bot vs Leon](https://www.anchorterminal.com/compare/grok-bot-vs-leon.md)\n- [Grok Bot vs Lindy](https://www.anchorterminal.com/compare/grok-bot-vs-lindy.md)\n- [Grok Bot vs nanobot](https://www.anchorterminal.com/compare/grok-bot-vs-nanobot.md)\n- [Grok Bot vs NanoClaw](https://www.anchorterminal.com/compare/grok-bot-vs-nanoclaw.md)\n- [Grok Bot vs Dots](https://www.anchorterminal.com/compare/grok-bot-vs-openai-dots.md)\n- [Grok Bot vs OpenClaw](https://www.anchorterminal.com/compare/grok-bot-vs-openclaw.md)\n- [Grok Bot vs PicoClaw](https://www.anchorterminal.com/compare/grok-bot-vs-picoclaw.md)\n- [Grok Bot vs Poke](https://www.anchorterminal.com/compare/grok-bot-vs-poke.md)\n- [Grok Bot vs QwenPaw](https://www.anchorterminal.com/compare/grok-bot-vs-qwenpaw.md)\n- [Grok Bot vs ZeroClaw](https://www.anchorterminal.com/compare/grok-bot-vs-zeroclaw.md)\n- [Haven vs Zo Computer](https://www.anchorterminal.com/compare/haven-vs-zo-computer.md)\n- [Hermes Agent vs Zo Computer](https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer.md)\n- [Instinct vs Zo Computer](https://www.anchorterminal.com/compare/instinct-vs-zo-computer.md)\n- [IronClaw vs Zo Computer](https://www.anchorterminal.com/compare/ironclaw-vs-zo-computer.md)\n- [Leon vs Zo Computer](https://www.anchorterminal.com/compare/leon-vs-zo-computer.md)\n- [Lindy vs Zo Computer](https://www.anchorterminal.com/compare/lindy-vs-zo-computer.md)\n- [nanobot vs Zo Computer](https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.md)\n- [NanoClaw vs Zo Computer](https://www.anchorterminal.com/compare/nanoclaw-vs-zo-computer.md)\n- [Dots vs Zo Computer](https://www.anchorterminal.com/compare/openai-dots-vs-zo-computer.md)\n- [OpenClaw vs Zo Computer](https://www.anchorterminal.com/compare/openclaw-vs-zo-computer.md)\n- [PicoClaw vs Zo Computer](https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer.md)\n- [Poke vs Zo Computer](https://www.anchorterminal.com/compare/poke-vs-zo-computer.md)\n- [QwenPaw vs Zo Computer](https://www.anchorterminal.com/compare/qwenpaw-vs-zo-computer.md)\n- [ZeroClaw vs Zo Computer](https://www.anchorterminal.com/compare/zeroclaw-vs-zo-computer.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-12", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Grok Bot vs Zo Computer", "url": "" } ], "description": "Grok Bot scores 45.2 (E) to Zo Computer's 43.1 (E) for assistant proactive. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grok Bot E 45.2", "Zo Computer E 43.1", "scores" ], "h1": "Grok Bot vs Zo Computer", "image": "https://www.anchorterminal.com/assets/og/compare-grok-bot-vs-zo-computer.png", "path": "/compare/grok-bot-vs-zo-computer", "published": "2026-10-01", "section": "tools", "title": "Grok Bot vs Zo Computer for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer" }, "tokens": { "markdown": 2750, "slim": 630 }, "version": 1 }