{ "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 Haven's 22.2 (F), and leads in 5 of 7 scored categories. Haven leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "haven", "name": "Haven", "vendor": "Hello Haven, Inc.", "vendorUrl": "https://my.hellohaven.ai", "kind": "platform", "category": "personal-assistants", "summary": "Hosted personal AI assistant from Hello Haven, Inc. that a person reaches by phone call, text message, email, web or mobile app. It keeps a memory of the user and carries out tasks for them. In beta.", "url": "https://www.anchorterminal.com/tools/haven", "markdownUrl": "https://www.anchorterminal.com/tools/haven.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/haven.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/haven.json", "license": "Proprietary service under Hello Haven's Terms of Service", "transports": [ "http" ], "packages": [], "auth": "mixed", "authNotes": "A person signs up at my.hellohaven.ai/gethaven with an invite code and signs in at app.hellohaven.ai, or reaches Haven from their own phone number or email address. The sign-in method was not read, because the app is behind a sign-in. No API key, OAuth app or other developer credential was found. The terms say Haven connects with the user's email, calendar, cloud storage, messaging and other services, and the privacy policy says authentication credentials for connected services are shared with those providers. Provider names, scopes and where tokens are stored were not found (https://my.hellohaven.ai/terms; https://my.hellohaven.ai/privacy).", "pricing": "free", "pricingNotes": "Free during beta with full access and no card, per the plans page. The FAQ says there are no usage limits, that prices are not set, and that users will get notice before charges begin. The terms mention subscription billing through a payment processor but no price is published (https://my.hellohaven.ai/plans; https://my.hellohaven.ai/faq, checked 2026-10-12).", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the site, the plans page or the terms, and no API to carry one (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://my.hellohaven.ai/faq", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory" ], "tags": [ "hosted", "closed-source", "beta", "free", "phone", "sms", "email", "voice", "ios", "android", "status-page" ], "lastRelease": "2026-09-17", "graded": true, "anchor": { "graded": true, "score": 22.2, "grade": "F", "agentReady": false, "rank": 977, "ranked": true, "rankOf": 986, "categoryRank": 19, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 6, "maintenance": 35, "payments": 30, "reliability": 35, "schema": 4, "security": 13, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-10-12" }, "negative": 0, "verdict": "Haven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor.", "bestFor": "A consumer assistant for one person who wants to phone, text or email it and have it remember them.", "strengths": [ "Free during beta with no card and no usage limits, per the plans page and FAQ (checked 12 October 2026).", "One assistant on phone call, SMS, email, voice, web and mobile app, with a published phone number and email address.", "Statuspage site with eight components, including Phone Calls, SMS Chat and Scheduled Tasks \u0026 Reminders, and four dated incidents since May 2026.", "The data page says memory can be viewed, edited, exported and wiped in the app, with deleted data leaving backups within 30 days.", "The privacy policy names Hello Haven, Inc. with a street address in Park City, Utah, and was last updated on 24 July 2026." ], "weaknesses": [ "No approval setting or list of actions that need confirmation was found on the public pages. The terms say it sends emails, SMS and calls following the user's instructions.", "Connected accounts are described only by type (email, calendar, cloud storage, messaging). No provider names, scopes or token storage statement were found.", "Model providers and sub-processors are listed by category only. The policy says the list is available on request by email.", "No API, MCP server, developer docs, changelog, security.txt or disclosure policy was found. The press release says a developer platform is planned.", "Two voice outages (23 May and 15 August 2026) were caused by billing errors with a provider, per the status page.", "The terms allow the vendor to suspend, modify or terminate the service at any time, and say continued use accepts updated terms." ], "agentNotes": [ "Haven has no documented API or MCP server. An outside agent can reach it only through the owner's channels (call, SMS, email, app).", "Do not assume an approval step before Haven sends mail, texts or calls. None is documented on the public pages.", "Email Haven sends to other people names Hello Haven as sender and says it was sent on the user's behalf, per the terms.", "Chat messages, history, profile context and uploaded files go to third-party AI model providers that the vendor does not name.", "Check status.hellohaven.ai before relying on phone or voice. All four published incidents affected those channels." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 22.2 } ], "editorialScores": { "ergonomics": 6, "maintenance": 35, "payments": 30, "reliability": 35, "schema": 4, "security": 13, "transparency": 37 }, "provenanceScore": 64 }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/haven" }, "area": "frameworks", "provenance": { "legalEntity": "Hello Haven, Inc.", "domain": "hellohaven.ai", "domainRegistered": "2024-11-21", "endpointOnVendorDomain": true, "terms": "https://my.hellohaven.ai/terms", "privacy": "https://my.hellohaven.ai/privacy", "statusPage": "https://status.hellohaven.ai/", "changelog": "", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The privacy policy names Hello Haven, Inc. with a street address in Park City, Utah 84098. The terms are governed by Utah law with disputes heard in Salt Lake City.", "my.hellohaven.ai/.well-known/security.txt answered 404 on 12 October 2026. No disclosure policy was found.", "RDAP gives a registration date of 2024-11-21 for hellohaven.ai, registrar GoDaddy.com, LLC, registrant private.", "The app is at app.hellohaven.ai, linked from every page. We did not open it.", "The terms and privacy pages are drawn by script. Our reader received their text and a plain request received an empty page." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/haven.json", "live": { "slug": "haven", "vendorStatus": { "page": "https://status.hellohaven.ai", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-12T18:56:37.37398695Z" }, "updatedAt": "2026-10-12T18:56:37.37398695Z" } }, "facts": [ { "a": "Platform", "b": "Platform", "name": "Kind" }, { "a": "SpaceXAI and Cursor (Anysphere, Inc.)", "b": "Hello Haven, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary", "b": "Proprietary service under Hello Haven's Terms of Service", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "none", "b": "2026-09-17", "name": "Last release" }, { "a": "2026-09-03", "b": "2026-07-24", "name": "Terms last updated" }, { "a": "2026-09-29", "b": "2026-07-24", "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 Haven's 22.2 (F), and leads in 5 of 7 scored categories. Haven leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Grok Bot or Haven?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 40 against 35", "Schema \u0026 documentation, 40 against 4", "Agent ergonomics, 50 against 6", "Security \u0026 auth, 68 against 13", "Transparency \u0026 trust, 66 against 51" ], "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": [ "Payments \u0026 pricing, 30 against 25", "Maintenance \u0026 community, 35 against 20" ], "also": null, "goodFor": "A consumer assistant for one person who wants to phone, text or email it and have it remember them.", "slug": "haven", "watchFor": "No approval setting or list of actions that need confirmation was found on the public pages. The terms say it sends emails, SMS and calls following the user's instructions." } ], "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-haven.json", "title": "AstrBot vs Haven", "url": "https://www.anchorterminal.com/compare/astrbot-vs-haven" }, { "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-haven.json", "title": "CowAgent vs Haven", "url": "https://www.anchorterminal.com/compare/cowagent-vs-haven" }, { "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-haven.json", "title": "GAIA vs Haven", "url": "https://www.anchorterminal.com/compare/gaia-vs-haven" }, { "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-haven.json", "title": "Gemini Spark vs Haven", "url": "https://www.anchorterminal.com/compare/gemini-spark-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/grok-bot-vs-zo-computer.json", "title": "Grok Bot vs Zo Computer", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-hermes-agent.json", "title": "Haven vs Hermes Agent", "url": "https://www.anchorterminal.com/compare/haven-vs-hermes-agent" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-instinct.json", "title": "Haven vs Instinct", "url": "https://www.anchorterminal.com/compare/haven-vs-instinct" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-ironclaw.json", "title": "Haven vs IronClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-ironclaw" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-leon.json", "title": "Haven vs Leon", "url": "https://www.anchorterminal.com/compare/haven-vs-leon" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-lindy.json", "title": "Haven vs Lindy", "url": "https://www.anchorterminal.com/compare/haven-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-nanobot.json", "title": "Haven vs nanobot", "url": "https://www.anchorterminal.com/compare/haven-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-nanoclaw.json", "title": "Haven vs NanoClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-openai-dots.json", "title": "Haven vs Dots", "url": "https://www.anchorterminal.com/compare/haven-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-openclaw.json", "title": "Haven vs OpenClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-openclaw" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-picoclaw.json", "title": "Haven vs PicoClaw", "url": "https://www.anchorterminal.com/compare/haven-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-poke.json", "title": "Haven vs Poke", "url": "https://www.anchorterminal.com/compare/haven-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-qwenpaw.json", "title": "Haven vs QwenPaw", "url": "https://www.anchorterminal.com/compare/haven-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/haven-vs-zeroclaw.json", "title": "Haven vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/haven-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" } ], "scores": [ { "by": 5, "edge": "grok-bot", "grok-bot": 40, "haven": 35, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 36, "edge": "grok-bot", "grok-bot": 40, "haven": 4, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 44, "edge": "grok-bot", "grok-bot": 50, "haven": 6, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 55, "edge": "grok-bot", "grok-bot": 68, "haven": 13, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "edge": "haven", "grok-bot": 25, "haven": 30, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 15, "edge": "haven", "grok-bot": 20, "haven": 35, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 15, "edge": "grok-bot", "grok-bot": 66, "haven": 51, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Grok Bot scores 45.2 (E) on agent readiness against Haven's 22.2 (F), and leads in 5 of 7 scored categories. Haven leads on 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.", "haven": "Haven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/grok-bot-vs-haven", "json": "https://www.anchorterminal.com/compare/grok-bot-vs-haven.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grok-bot-vs-haven.md", "slim": "https://www.anchorterminal.com/compare/grok-bot-vs-haven.min.md" }, "markdown": "Grok Bot scores 45.2 (E) on agent readiness against Haven's 22.2 (F), and leads in 5 of 7 scored categories. Haven leads on 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- Haven: grade F, 22.2/100, rank #977 of 986. Markdown https://www.anchorterminal.com/tools/haven.md · JSON https://www.anchorterminal.com/api/v1/tools/haven.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 35\n- Schema \u0026 documentation, 40 against 4\n- Agent ergonomics, 50 against 6\n- Security \u0026 auth, 68 against 13\n- Transparency \u0026 trust, 66 against 51\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### Haven (F)\n\nGood for: A consumer assistant for one person who wants to phone, text or email it and have it remember them.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 25\n- Maintenance \u0026 community, 35 against 20\n\nWatch for: No approval setting or list of actions that need confirmation was found on the public pages. The terms say it sends emails, SMS and calls following the user's instructions.\n\n\n## Score by category\n\n| Category | Weight | Grok Bot | Haven | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 35 | Grok Bot +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 4 | Grok Bot +36 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 6 | Grok Bot +44 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 13 | Grok Bot +55 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 30 | Haven +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 35 | Haven +15 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 51 | Grok Bot +15 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.2 · E** | **22.2 · F** | |\n\n## Facts side by side\n\n| Fact | Grok Bot | Haven |\n| --- | --- | --- |\n| Kind | Platform | Platform |\n| Vendor | SpaceXAI and Cursor (Anysphere, Inc.) | Hello Haven, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Free |\n| x402 | no | no |\n| Licence | Proprietary | Proprietary service under Hello Haven's Terms of Service |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | none | 2026-09-17 |\n| Terms last updated | 2026-09-03 | 2026-07-24 |\n| Privacy policy last updated | 2026-09-29 | 2026-07-24 |\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**Haven.** Haven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor.\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### Haven\n\n1. Haven has no documented API or MCP server. An outside agent can reach it only through the owner's channels (call, SMS, email, app).\n2. Do not assume an approval step before Haven sends mail, texts or calls. None is documented on the public pages.\n3. Email Haven sends to other people names Hello Haven as sender and says it was sent on the user's behalf, per the terms.\n4. Chat messages, history, profile context and uploaded files go to third-party AI model providers that the vendor does not name.\n5. Check status.hellohaven.ai before relying on phone or voice. All four published incidents affected those channels.\n\n## Questions\n\n### Which is better for AI agents, Grok Bot or Haven?\n\nGrok Bot scores 45.2 (E) on agent readiness against Haven's 22.2 (F), and leads in 5 of 7 scored categories. Haven leads on payments \u0026 pricing and maintenance \u0026 community.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grok-bot-vs-haven.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grok-bot-vs-haven.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grok-bot\", \"b\": \"haven\"}`. From a terminal: `anchor compare grok-bot haven`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grok-bot.json and https://www.anchorterminal.com/api/v1/tools/haven.json\n\n## Other comparisons with Grok Bot or Haven\n\n- [AstrBot vs Grok Bot](https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.md)\n- [AstrBot vs Haven](https://www.anchorterminal.com/compare/astrbot-vs-haven.md)\n- [CowAgent vs Grok Bot](https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.md)\n- [CowAgent vs Haven](https://www.anchorterminal.com/compare/cowagent-vs-haven.md)\n- [GAIA vs Grok Bot](https://www.anchorterminal.com/compare/gaia-vs-grok-bot.md)\n- [GAIA vs Haven](https://www.anchorterminal.com/compare/gaia-vs-haven.md)\n- [Gemini Spark vs Grok Bot](https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.md)\n- [Gemini Spark vs Haven](https://www.anchorterminal.com/compare/gemini-spark-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- [Grok Bot vs Zo Computer](https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.md)\n- [Haven vs Hermes Agent](https://www.anchorterminal.com/compare/haven-vs-hermes-agent.md)\n- [Haven vs Instinct](https://www.anchorterminal.com/compare/haven-vs-instinct.md)\n- [Haven vs IronClaw](https://www.anchorterminal.com/compare/haven-vs-ironclaw.md)\n- [Haven vs Leon](https://www.anchorterminal.com/compare/haven-vs-leon.md)\n- [Haven vs Lindy](https://www.anchorterminal.com/compare/haven-vs-lindy.md)\n- [Haven vs nanobot](https://www.anchorterminal.com/compare/haven-vs-nanobot.md)\n- [Haven vs NanoClaw](https://www.anchorterminal.com/compare/haven-vs-nanoclaw.md)\n- [Haven vs Dots](https://www.anchorterminal.com/compare/haven-vs-openai-dots.md)\n- [Haven vs OpenClaw](https://www.anchorterminal.com/compare/haven-vs-openclaw.md)\n- [Haven vs PicoClaw](https://www.anchorterminal.com/compare/haven-vs-picoclaw.md)\n- [Haven vs Poke](https://www.anchorterminal.com/compare/haven-vs-poke.md)\n- [Haven vs QwenPaw](https://www.anchorterminal.com/compare/haven-vs-qwenpaw.md)\n- [Haven vs ZeroClaw](https://www.anchorterminal.com/compare/haven-vs-zeroclaw.md)\n- [Haven vs Zo Computer](https://www.anchorterminal.com/compare/haven-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 Haven", "url": "" } ], "description": "Grok Bot scores 45.2 (E) to Haven's 22.2 (F) for assistant proactive. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grok Bot E 45.2", "Haven F 22.2", "scores" ], "h1": "Grok Bot vs Haven", "image": "https://www.anchorterminal.com/assets/og/compare-grok-bot-vs-haven.png", "path": "/compare/grok-bot-vs-haven", "published": "2026-10-01", "section": "tools", "title": "Grok Bot vs Haven for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-haven" }, "tokens": { "markdown": 2550, "slim": 580 }, "version": 1 }