{ "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 Lindy's 32.3 (F), and leads in 6 of 7 scored categories. Lindy leads on payments \u0026 pricing.", "b": { "slug": "lindy", "name": "Lindy", "vendor": "Crivello Corp (doing business as Lindy)", "vendorUrl": "https://www.lindy.ai", "kind": "platform", "category": "personal-assistants", "summary": "Lindy is a hosted AI assistant from Crivello Corp. Each user has a private assistant for mail, calendar and meetings, reached by Slack, iMessage, SMS, email or the web app, and a team shares a second one in Slack channels.", "url": "https://www.anchorterminal.com/tools/lindy", "markdownUrl": "https://www.anchorterminal.com/tools/lindy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/lindy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/lindy.json", "license": "Proprietary service under Lindy's Terms of Service. No source is published", "transports": [], "packages": [], "auth": "oauth", "authNotes": "A person signs in with Google or Microsoft and connects mail and calendar from either, a phone number verified by code, and Slack through an app an owner or admin installs. Other tools connect by OAuth or an API key, and every action for a tool turns on at once with no scope choice in Lindy. A connection is personal until an owner or admin shares it with the workspace, after which everyone's Lindy works as that account. Saved API keys are write-only and can be rotated or revoked. No public API or key for outside callers was found in the docs.", "pricing": "paid", "pricingNotes": "$29.99 per active user a month with 3,000 credits, pooled across the workspace, and larger monthly credit amounts up to 1,750,000 for $9,999.50. Top-ups are $10 per 1,000 credits and do not expire, while monthly credits do not roll over. New accounts get $50 of credit for seven days with no card. The pricing page gives 2 to 250 credits for an everyday request and 1,000 to 2,500 for a large build. The docs name Plus, Pro and Max plans priced only inside the app, which the pricing page does not list (checked 2026-10-12).", "priceSummary": "$29.99 / seat-mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the terms or the docs (checked 2026-10-12).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-12" }, "docsUrl": "https://docs.lindy.ai", "llmsTxt": "https://docs.lindy.ai/llms.txt", "capabilities": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "agent.mcp-client" ], "tags": [ "hosted", "closed-source", "paid", "free-trial", "no-card", "slack", "imessage", "sms", "email", "chrome-extension", "mcp-client", "approvals", "llms-txt", "soc2", "team" ], "lastRelease": "2025-10-21", "graded": true, "anchor": { "graded": true, "score": 32.3, "grade": "F", "agentReady": false, "rank": 968, "ranked": true, "rankOf": 986, "categoryRank": 16, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 43, "maintenance": 9, "payments": 35, "reliability": 24, "schema": 32, "security": 49, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-12" }, "negative": -3, "negativeNotes": [ "2026-10-12. The pricing page and the docs pricing page answer the question of whether Lindy does anything without approval with No, and say anything with outside impact waits for approval. The integrations page says approval settings apply in shared Slack threads only, that web chat, Slack direct messages, iMessage and SMS are not guarded, and that an integration can be set to always allow writes (https://www.lindy.ai/pricing, https://docs.lindy.ai/pricing.md, https://docs.lindy.ai/integrations/overview.md). 3 points for a misleading claim." ], "verdict": "Lindy keeps what it remembers in files the owner can read and edit, and publishes credit prices. Its approval setting applies in shared Slack threads only, so writes asked for by direct message, text or web chat run unasked, which its pricing page does not say. It has no status page, and its changelog stops in October 2025.", "bestFor": "Lindy suits a person or small team that lives in Slack and Google or Microsoft mail and wants briefs, drafts, scheduling and meeting notes done on a schedule.", "strengths": [ "Memory is a set of plain files in the web app, split into Personal, Team and System scopes, which the owner can read, edit and restore by version.", "Each integration has a setting that makes Lindy ask in Slack before writing, or stops it writing with that tool at all.", "Saved API keys are write-only. The docs say a value cannot be read back in the app, through the API or by asking Lindy, and keys can be rotated or revoked.", "The privacy policy of 28 September 2026 names its processors by category, among them Anthropic, OpenAI, Perplexity AI, Pipedream, WorkOS, Twilio and Recall.ai.", "Credit prices are public. A seat is $29.99 a month with 3,000 credits, top-ups are $10 per 1,000, and new accounts get $50 of credit with no card." ], "weaknesses": [ "The integrations page says approval settings apply in shared Slack threads only. Web chat, Slack direct messages, iMessage and SMS are not covered, and reads are never covered.", "The pricing page and the docs pricing page both answer that Lindy does nothing with outside impact without approval, which the integrations page contradicts.", "No status page, uptime record or SLA was found on the site or in the docs.", "The public changelog's newest entry is dated 21 October 2025, and it describes an agent builder the current docs no longer cover.", "Deleting a memory file keeps its earlier versions, and no way to purge them or a retention period was found. The privacy policy gives no period either.", "The terms of 24 September 2026 forbid automated use of the system and use for any commercial enterprise, in a product sold to companies. This matters before any probe is run." ], "agentNotes": [ "Treat a request sent by direct message, text or web chat as unguarded. Approval prompts appear in shared Slack threads only.", "Run a routine as a dry run before turning it on. A dry run reads real data and sends, posts and writes nothing.", "Turn off unused tools after adding an MCP server. Every supported tool arrives switched on, and a large server adds more than a hundred.", "Expect a billed seat for anyone who mentions Lindy in Slack. A teammate who joins that way has seven free days first.", "Connect only hosted MCP servers on public HTTPS with streamable HTTP, the one kind the docs describe." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 32.3 } ], "editorialScores": { "ergonomics": 43, "maintenance": 9, "payments": 35, "reliability": 24, "schema": 32, "security": 49, "transparency": 36 }, "provenanceScore": 68 }, "letme": { "capability": "https://letme.dev/assistant.proactive", "tool": "https://letme.dev/lindy" }, "area": "frameworks", "unitPrices": [ { "item": "Team seat", "unit": "seat-month", "usd": 29.99, "note": "3,000 credits a month, pooled across the workspace. Every active user is billed" }, { "item": "Top-up credit", "unit": "credit", "usd": 0.01, "note": "$10 per 1,000 credits. Top-up credits do not expire, monthly credits do not roll over" } ], "provenance": { "legalEntity": "Crivello Corp (doing business as Lindy)", "domain": "lindy.ai", "domainRegistered": "2019-05-16", "endpointOnVendorDomain": true, "terms": "https://www.lindy.ai/terms-of-service", "privacy": "https://www.lindy.ai/privacy", "statusPage": "", "changelog": "https://www.lindy.ai/changelog", "securityTxt": "none", "checked": "2026-10-12", "notes": [ "The Terms of Service, last updated 24 September 2026, name Crivello Corp, doing business as Lindy, registered in Oregon at 9450 SW Gemini Dr, Beaverton, OR 97008, and are governed by California law with binding arbitration.", "The terms cover the site and all related products and services. No separate service agreement or DPA was linked from the pages read.", "The privacy policy was last updated 28 September 2026.", "The web app and sign-in are at chat.lindy.ai.", "www.lindy.ai/.well-known/security.txt returns 404. No disclosure policy or bug bounty was found.", "No status page is linked from the site, the docs or the security page.", "RDAP gives a registration date of 2019-05-16 for lindy.ai, with NameCheap as registrar." ], "score": 68 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/lindy.json" }, "facts": [ { "a": "Platform", "b": "Platform", "name": "Kind" }, { "a": "SpaceXAI and Cursor (Anysphere, Inc.)", "b": "Crivello Corp (doing business as Lindy)", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary", "b": "Proprietary service under Lindy's Terms of Service. No source is published", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2025-10-21", "name": "Last release" }, { "a": "2026-09-03", "b": "2026-09-24", "name": "Terms last updated" }, { "a": "2026-09-29", "b": "2026-09-28", "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": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Grok Bot scores 45.2 (E) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories. Lindy leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Grok Bot or Lindy?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 40 against 24", "Schema \u0026 documentation, 40 against 32", "Agent ergonomics, 50 against 43", "Security \u0026 auth, 68 against 49", "Maintenance \u0026 community, 20 against 9", "Transparency \u0026 trust, 66 against 52" ], "also": [ "No incidents deducted, where Lindy loses 3 points for them" ], "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, 35 against 25" ], "also": [ "Free to start without a card" ], "goodFor": "Lindy suits a person or small team that lives in Slack and Google or Microsoft mail and wants briefs, drafts, scheduling and meeting notes done on a schedule.", "slug": "lindy", "watchFor": "The integrations page says approval settings apply in shared Slack threads only. Web chat, Slack direct messages, iMessage and SMS are not covered, and reads are never covered." } ], "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-lindy.json", "title": "AstrBot vs Lindy", "url": "https://www.anchorterminal.com/compare/astrbot-vs-lindy" }, { "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-lindy.json", "title": "CowAgent vs Lindy", "url": "https://www.anchorterminal.com/compare/cowagent-vs-lindy" }, { "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-lindy.json", "title": "GAIA vs Lindy", "url": "https://www.anchorterminal.com/compare/gaia-vs-lindy" }, { "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-lindy.json", "title": "Gemini Spark vs Lindy", "url": "https://www.anchorterminal.com/compare/gemini-spark-vs-lindy" }, { "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-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-lindy.json", "title": "Haven vs Lindy", "url": "https://www.anchorterminal.com/compare/haven-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/hermes-agent-vs-lindy.json", "title": "Hermes Agent vs Lindy", "url": "https://www.anchorterminal.com/compare/hermes-agent-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/instinct-vs-lindy.json", "title": "Instinct vs Lindy", "url": "https://www.anchorterminal.com/compare/instinct-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/ironclaw-vs-lindy.json", "title": "IronClaw vs Lindy", "url": "https://www.anchorterminal.com/compare/ironclaw-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/leon-vs-lindy.json", "title": "Leon vs Lindy", "url": "https://www.anchorterminal.com/compare/leon-vs-lindy" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-nanobot.json", "title": "Lindy vs nanobot", "url": "https://www.anchorterminal.com/compare/lindy-vs-nanobot" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-nanoclaw.json", "title": "Lindy vs NanoClaw", "url": "https://www.anchorterminal.com/compare/lindy-vs-nanoclaw" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-openai-dots.json", "title": "Lindy vs Dots", "url": "https://www.anchorterminal.com/compare/lindy-vs-openai-dots" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-openclaw.json", "title": "Lindy vs OpenClaw", "url": "https://www.anchorterminal.com/compare/lindy-vs-openclaw" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-picoclaw.json", "title": "Lindy vs PicoClaw", "url": "https://www.anchorterminal.com/compare/lindy-vs-picoclaw" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-poke.json", "title": "Lindy vs Poke", "url": "https://www.anchorterminal.com/compare/lindy-vs-poke" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-qwenpaw.json", "title": "Lindy vs QwenPaw", "url": "https://www.anchorterminal.com/compare/lindy-vs-qwenpaw" }, { "json": "https://www.anchorterminal.com/compare/lindy-vs-zeroclaw.json", "title": "Lindy vs ZeroClaw", "url": "https://www.anchorterminal.com/compare/lindy-vs-zeroclaw" }, { "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" } ], "scores": [ { "by": 16, "edge": "grok-bot", "grok-bot": 40, "key": "reliability", "lindy": 24, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "grok-bot", "grok-bot": 40, "key": "schema", "lindy": 32, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 7, "edge": "grok-bot", "grok-bot": 50, "key": "ergonomics", "lindy": 43, "name": "Agent ergonomics", "weight": 13 }, { "by": 19, "edge": "grok-bot", "grok-bot": 68, "key": "security", "lindy": 49, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "edge": "lindy", "grok-bot": 25, "key": "payments", "lindy": 35, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 11, "edge": "grok-bot", "grok-bot": 20, "key": "maintenance", "lindy": 9, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 14, "edge": "grok-bot", "grok-bot": 66, "key": "transparency", "lindy": 52, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Grok Bot scores 45.2 (E) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories. Lindy leads on payments \u0026 pricing. 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.", "lindy": "Lindy keeps what it remembers in files the owner can read and edit, and publishes credit prices. Its approval setting applies in shared Slack threads only, so writes asked for by direct message, text or web chat run unasked, which its pricing page does not say. It has no status page, and its changelog stops in October 2025." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy", "json": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy.md", "slim": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy.min.md" }, "markdown": "Grok Bot scores 45.2 (E) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories. Lindy leads on payments \u0026 pricing. 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- Lindy: grade F, 32.3/100, rank #968 of 986. Markdown https://www.anchorterminal.com/tools/lindy.md · JSON https://www.anchorterminal.com/api/v1/tools/lindy.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 24\n- Schema \u0026 documentation, 40 against 32\n- Agent ergonomics, 50 against 43\n- Security \u0026 auth, 68 against 49\n- Maintenance \u0026 community, 20 against 9\n- Transparency \u0026 trust, 66 against 52\n\nAlso in its favour:\n- No incidents deducted, where Lindy loses 3 points for them\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### Lindy (F)\n\nGood for: Lindy suits a person or small team that lives in Slack and Google or Microsoft mail and wants briefs, drafts, scheduling and meeting notes done on a schedule.\n\nAhead on:\n- Payments \u0026 pricing, 35 against 25\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: The integrations page says approval settings apply in shared Slack threads only. Web chat, Slack direct messages, iMessage and SMS are not covered, and reads are never covered.\n\n\n## Score by category\n\n| Category | Weight | Grok Bot | Lindy | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 24 | Grok Bot +16 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 40 | 32 | Grok Bot +8 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 43 | Grok Bot +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 68 | 49 | Grok Bot +19 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 35 | Lindy +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 20 | 9 | Grok Bot +11 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 66 | 52 | Grok Bot +14 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **45.2 · E** | **32.3 · F** | |\n\n## Facts side by side\n\n| Fact | Grok Bot | Lindy |\n| --- | --- | --- |\n| Kind | Platform | Platform |\n| Vendor | SpaceXAI and Cursor (Anysphere, Inc.) | Crivello Corp (doing business as Lindy) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | OAuth or key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary | Proprietary service under Lindy's Terms of Service. No source is published |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2025-10-21 |\n| Terms last updated | 2026-09-03 | 2026-09-24 |\n| Privacy policy last updated | 2026-09-29 | 2026-09-28 |\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 | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\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**Lindy.** Lindy keeps what it remembers in files the owner can read and edit, and publishes credit prices. Its approval setting applies in shared Slack threads only, so writes asked for by direct message, text or web chat run unasked, which its pricing page does not say. It has no status page, and its changelog stops in October 2025.\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### Lindy\n\n1. Treat a request sent by direct message, text or web chat as unguarded. Approval prompts appear in shared Slack threads only.\n2. Run a routine as a dry run before turning it on. A dry run reads real data and sends, posts and writes nothing.\n3. Turn off unused tools after adding an MCP server. Every supported tool arrives switched on, and a large server adds more than a hundred.\n4. Expect a billed seat for anyone who mentions Lindy in Slack. A teammate who joins that way has seven free days first.\n5. Connect only hosted MCP servers on public HTTPS with streamable HTTP, the one kind the docs describe.\n\n## Questions\n\n### Which is better for AI agents, Grok Bot or Lindy?\n\nGrok Bot scores 45.2 (E) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories. Lindy leads on payments \u0026 pricing.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/grok-bot-vs-lindy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/grok-bot-vs-lindy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"grok-bot\", \"b\": \"lindy\"}`. From a terminal: `anchor compare grok-bot lindy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/grok-bot.json and https://www.anchorterminal.com/api/v1/tools/lindy.json\n\n## Other comparisons with Grok Bot or Lindy\n\n- [AstrBot vs Grok Bot](https://www.anchorterminal.com/compare/astrbot-vs-grok-bot.md)\n- [AstrBot vs Lindy](https://www.anchorterminal.com/compare/astrbot-vs-lindy.md)\n- [CowAgent vs Grok Bot](https://www.anchorterminal.com/compare/cowagent-vs-grok-bot.md)\n- [CowAgent vs Lindy](https://www.anchorterminal.com/compare/cowagent-vs-lindy.md)\n- [GAIA vs Grok Bot](https://www.anchorterminal.com/compare/gaia-vs-grok-bot.md)\n- [GAIA vs Lindy](https://www.anchorterminal.com/compare/gaia-vs-lindy.md)\n- [Gemini Spark vs Grok Bot](https://www.anchorterminal.com/compare/gemini-spark-vs-grok-bot.md)\n- [Gemini Spark vs Lindy](https://www.anchorterminal.com/compare/gemini-spark-vs-lindy.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 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 Lindy](https://www.anchorterminal.com/compare/haven-vs-lindy.md)\n- [Hermes Agent vs Lindy](https://www.anchorterminal.com/compare/hermes-agent-vs-lindy.md)\n- [Instinct vs Lindy](https://www.anchorterminal.com/compare/instinct-vs-lindy.md)\n- [IronClaw vs Lindy](https://www.anchorterminal.com/compare/ironclaw-vs-lindy.md)\n- [Leon vs Lindy](https://www.anchorterminal.com/compare/leon-vs-lindy.md)\n- [Lindy vs nanobot](https://www.anchorterminal.com/compare/lindy-vs-nanobot.md)\n- [Lindy vs NanoClaw](https://www.anchorterminal.com/compare/lindy-vs-nanoclaw.md)\n- [Lindy vs Dots](https://www.anchorterminal.com/compare/lindy-vs-openai-dots.md)\n- [Lindy vs OpenClaw](https://www.anchorterminal.com/compare/lindy-vs-openclaw.md)\n- [Lindy vs PicoClaw](https://www.anchorterminal.com/compare/lindy-vs-picoclaw.md)\n- [Lindy vs Poke](https://www.anchorterminal.com/compare/lindy-vs-poke.md)\n- [Lindy vs QwenPaw](https://www.anchorterminal.com/compare/lindy-vs-qwenpaw.md)\n- [Lindy vs ZeroClaw](https://www.anchorterminal.com/compare/lindy-vs-zeroclaw.md)\n- [Lindy vs Zo Computer](https://www.anchorterminal.com/compare/lindy-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 Lindy", "url": "" } ], "description": "Grok Bot scores 45.2 (E) to Lindy's 32.3 (F) for assistant proactive. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Grok Bot E 45.2", "Lindy F 32.3", "scores" ], "h1": "Grok Bot vs Lindy", "image": "https://www.anchorterminal.com/assets/og/compare-grok-bot-vs-lindy.png", "path": "/compare/grok-bot-vs-lindy", "published": "2026-10-01", "section": "tools", "title": "Grok Bot vs Lindy for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/compare/grok-bot-vs-lindy" }, "tokens": { "markdown": 2600, "slim": 680 }, "version": 1 }