{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/zeroclaw.json", "name": "ZeroClaw", "score": 70.2, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.accounts", "agent.mcp-client" ], "slug": "zeroclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/nanoclaw.json", "name": "NanoClaw", "score": 68.3, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "agent.mcp-client", "assistant.accounts" ], "slug": "nanoclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/hermes-agent.json", "name": "Hermes Agent", "score": 67.9, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "agent.mcp-client" ], "slug": "hermes-agent" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/openclaw.json", "name": "OpenClaw", "score": 67.1, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "agent.mcp-client" ], "slug": "openclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/ironclaw.json", "name": "IronClaw", "score": 66.7, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.accounts", "assistant.memory", "agent.mcp-client" ], "slug": "ironclaw" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/nanobot.json", "name": "nanobot", "score": 62.4, "shared": [ "assistant.proactive", "assistant.messaging", "assistant.memory", "assistant.accounts", "agent.mcp-client" ], "slug": "nanobot" } ], "tool": { "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 15, "points": 3, "reason": "Read with the hosted lines. No status page is linked from the home page, docs index, security page or help centre home (0). With no incident history to read, 5. No rate limit is published with numbers. The changelog of 7 September 2026 says the owner can set a concurrency limit for `/zo/ask` in Advanced settings, with no default figure given (0). No 429, Retry-After, backoff or idempotency guidance for the API was found (0). No SLA, and the terms supply the service as is (0). The API is at version 1.0.0 in its OpenAPI file and is not labelled beta (10). Total 15." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 73, "points": 11.86, "reason": "Graded on the HTTP API, with the MCP endpoint's tool definitions unread because listing them needs a token. A public OpenAPI 3.1 file covers all four operations (25). llms.txt and a Markdown copy of every guide and reference page (10). Field and tool descriptions state purpose in one line and seldom say when not to use something (10 of 20). The ask request is typed with one required field and an enum for `memory_mode`, while the work itself is a free-text prompt (10 of 15). The guide has curl and Python examples for continuing a conversation, structured output and streaming. Documented errors are a 422 validation schema, an error response schema and an SSE `Error` event, with no list of codes (8 of 15). A dated weekly changelog is public and the spec has a version, but the paths carry none and the guide omits `memory_mode`, which the spec defines (10 of 15). Total 73." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 34, "points": 5.53, "reason": "The HTTP API is four operations, and `output_format` takes a JSON Schema so a caller can size the answer. The MCP guide says all Zo tools are exposed, and llms.txt lists 110 tool reference pages, which is well over 30. Persona permissions can remove tools, though whether the MCP endpoint honours a persona was not established (10 of 25). Structured output and streaming control output, with no pagination or filtering on the list operations (8 of 20). Errors are a validation schema and a message string with no documented codes or recovery advice (6 of 20). No idempotency key or retry guidance for `/zo/ask`, MCP annotations were not read, and the changelog for the week of 17 August 2026 records a fix for a tool call that could run twice (2 of 20). Only `input` is required and defaults are sensible. An agent-sdk repository exists under the vendor's GitHub organisation but is not mentioned in the docs we read (8 of 15). Total 34." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 37, "points": 6.48, "reason": "One bearer token created in Settings, which both guides say grants full access to the workspace, and with it the shell, every connected account and every browser session. No scopes, expiry or rotation are documented (10 of 30). Persona permissions have four presets and 19 scopes and remove tools from a conversation, and a caller can pass `persona_id`, but the token is not bound to a persona. No approval step before sending, buying or deleting was found, and the browser guide says Zo can buy and send on signed-in sites (8 of 20). The assistant reads mail, web pages and channel messages. The security page says the design is not without risks and asks researchers to report prompt injection findings, with no mitigation or guidance documented (4 of 15). Each automation run and conversation is saved with the tools it used, with no audit log of API token use documented (7 of 15). A valid security.txt and a disclosure policy with a safe harbour and a 30-day window. No bounty terms, SOC 2 or ISO 27001 report, or advisory list was found (8 of 20). Total 37." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 40, "points": 5, "reason": "No x402, MPP or L402 (0). Plan prices, included credit and per-request media prices are public without a login, and the billing guide says chat follows listed token rates (20). The Free Trial runs 14 days and the home page says no credit card is required (20). A person signs up in a browser behind a Turnstile check and creates the token in Settings, so an agent cannot get access by itself (0). Total 40." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 68, "points": 5.95, "reason": "The newest dated changelog entry is the week of 14 September 2026, 28 days before this check, followed by a September summary. No entry for the three weeks since was on the page (30). Nine weekly entries fall in the last 90 days (20). A public changelog, a Discord community and a help centre with a route to a person. We did not test whether they answer (9 of 15). No official SDK is documented for the API and the official MCP registry returned no server for zocomputer. The desktop app's last GitHub release is v1.5.13 of 13 August 2026 (4 of 15). Package health does not apply to a closed service, and half marks rest on the changelog's steady run of fixes (5 of 10). Total 68." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 60, "points": 5.25, "note": "editorial 46, provenance 73", "reason": "Closed source with public terms. The terms are 18 short clauses last updated on 8 August 2025, cite an Acceptable Use Policy we did not find, name \"Substrate Lab's trademarks\" in clause 3, and say credits are bought in advance while the product is sold by subscription (12 of 30). The privacy policy of 20 May 2026 lists only email address, trackers, usage data and SMS data, gives no retention period, and does not describe workspace files, memory or connected-account data. The security page fills part of that gap, with stated retention for Postmark (45 days) and Telnyx (10 days), and the help centre says deleting the account erases the computer. No DPA was found (14 of 30). The changelog announces retired and deprecated models and says retired models forward to a successor, with no deprecation policy or notice period for the API (6 of 20). The security page names each provider and marks which can see user content. Data locations are given only for Fireworks, as US-based (14 of 20). Total 46." } ], "assessment": { "date": "2026-10-12", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "The HTTP API is four operations, and `output_format` takes a JSON Schema so a caller can size the answer. The MCP guide says all Zo tools are exposed, and llms.txt lists 110 tool reference pages, which is well over 30. Persona permissions can remove tools, though whether the MCP endpoint honours a persona was not established (10 of 25). Structured output and streaming control output, with no pagination or filtering on the list operations (8 of 20). Errors are a validation schema and a message string with no documented codes or recovery advice (6 of 20). No idempotency key or retry guidance for `/zo/ask`, MCP annotations were not read, and the changelog for the week of 17 August 2026 records a fix for a tool call that could run twice (2 of 20). Only `input` is required and defaults are sensible. An agent-sdk repository exists under the vendor's GitHub organisation but is not mentioned in the docs we read (8 of 15). Total 34.", "maintenance": "The newest dated changelog entry is the week of 14 September 2026, 28 days before this check, followed by a September summary. No entry for the three weeks since was on the page (30). Nine weekly entries fall in the last 90 days (20). A public changelog, a Discord community and a help centre with a route to a person. We did not test whether they answer (9 of 15). No official SDK is documented for the API and the official MCP registry returned no server for zocomputer. The desktop app's last GitHub release is v1.5.13 of 13 August 2026 (4 of 15). Package health does not apply to a closed service, and half marks rest on the changelog's steady run of fixes (5 of 10). Total 68.", "payments": "No x402, MPP or L402 (0). Plan prices, included credit and per-request media prices are public without a login, and the billing guide says chat follows listed token rates (20). The Free Trial runs 14 days and the home page says no credit card is required (20). A person signs up in a browser behind a Turnstile check and creates the token in Settings, so an agent cannot get access by itself (0). Total 40.", "reliability": "Read with the hosted lines. No status page is linked from the home page, docs index, security page or help centre home (0). With no incident history to read, 5. No rate limit is published with numbers. The changelog of 7 September 2026 says the owner can set a concurrency limit for `/zo/ask` in Advanced settings, with no default figure given (0). No 429, Retry-After, backoff or idempotency guidance for the API was found (0). No SLA, and the terms supply the service as is (0). The API is at version 1.0.0 in its OpenAPI file and is not labelled beta (10). Total 15.", "schema": "Graded on the HTTP API, with the MCP endpoint's tool definitions unread because listing them needs a token. A public OpenAPI 3.1 file covers all four operations (25). llms.txt and a Markdown copy of every guide and reference page (10). Field and tool descriptions state purpose in one line and seldom say when not to use something (10 of 20). The ask request is typed with one required field and an enum for `memory_mode`, while the work itself is a free-text prompt (10 of 15). The guide has curl and Python examples for continuing a conversation, structured output and streaming. Documented errors are a 422 validation schema, an error response schema and an SSE `Error` event, with no list of codes (8 of 15). A dated weekly changelog is public and the spec has a version, but the paths carry none and the guide omits `memory_mode`, which the spec defines (10 of 15). Total 73.", "security": "One bearer token created in Settings, which both guides say grants full access to the workspace, and with it the shell, every connected account and every browser session. No scopes, expiry or rotation are documented (10 of 30). Persona permissions have four presets and 19 scopes and remove tools from a conversation, and a caller can pass `persona_id`, but the token is not bound to a persona. No approval step before sending, buying or deleting was found, and the browser guide says Zo can buy and send on signed-in sites (8 of 20). The assistant reads mail, web pages and channel messages. The security page says the design is not without risks and asks researchers to report prompt injection findings, with no mitigation or guidance documented (4 of 15). Each automation run and conversation is saved with the tools it used, with no audit log of API token use documented (7 of 15). A valid security.txt and a disclosure policy with a safe harbour and a 30-day window. No bounty terms, SOC 2 or ISO 27001 report, or advisory list was found (8 of 20). Total 37.", "transparency": "Closed source with public terms. The terms are 18 short clauses last updated on 8 August 2025, cite an Acceptable Use Policy we did not find, name \"Substrate Lab's trademarks\" in clause 3, and say credits are bought in advance while the product is sold by subscription (12 of 30). The privacy policy of 20 May 2026 lists only email address, trackers, usage data and SMS data, gives no retention period, and does not describe workspace files, memory or connected-account data. The security page fills part of that gap, with stated retention for Postmark (45 days) and Telnyx (10 days), and the help centre says deleting the account erases the computer. No DPA was found (14 of 30). The changelog announces retired and deprecated models and says retired models forward to a successor, with no deprecation policy or notice period for the API (6 of 20). The security page names each provider and marks which can see user content. Data locations are given only for Fireworks, as US-based (14 of 20). Total 46." }, "sources": [ { "what": "home page", "url": "https://www.zo.computer/", "seen": "2026-10-12" }, { "what": "robots.txt", "url": "https://www.zo.computer/robots.txt", "seen": "2026-10-12" }, { "what": "llms.txt", "url": "https://www.zo.computer/llms.txt", "seen": "2026-10-12" }, { "what": "security.txt", "url": "https://www.zo.computer/.well-known/security.txt", "seen": "2026-10-12" }, { "what": "pricing", "url": "https://www.zo.computer/pricing", "seen": "2026-10-12" }, { "what": "subscription guide", "url": "https://www.zo.computer/guide/billing.md", "seen": "2026-10-12" }, { "what": "API guide", "url": "https://www.zo.computer/guide/api.md", "seen": "2026-10-12" }, { "what": "API reference", "url": "https://www.zo.computer/reference/api-reference.md", "seen": "2026-10-12" }, { "what": "OpenAPI file", "url": "https://www.zo.computer/docs-assets/openapi.json", "seen": "2026-10-12" }, { "what": "MCP server guide", "url": "https://www.zo.computer/guide/mcp-server.md", "seen": "2026-10-12" }, { "what": "messaging channels guide", "url": "https://www.zo.computer/guide/messaging-channels.md", "seen": "2026-10-12" }, { "what": "automations guide", "url": "https://www.zo.computer/guide/automations.md", "seen": "2026-10-12" }, { "what": "personas and permissions guide", "url": "https://www.zo.computer/guide/personas.md", "seen": "2026-10-12" }, { "what": "browser use guide", "url": "https://www.zo.computer/guide/browser.md", "seen": "2026-10-12" }, { "what": "Use Gmail tool reference", "url": "https://www.zo.computer/reference/tools/use-app-gmail.md", "seen": "2026-10-12" }, { "what": "security page", "url": "https://www.zo.computer/reference/information/security.md", "seen": "2026-10-12" }, { "what": "terms of service", "url": "https://www.zo.computer/reference/information/terms.md", "seen": "2026-10-12" }, { "what": "privacy policy", "url": "https://www.zo.computer/reference/information/privacy-policy.md", "seen": "2026-10-12" }, { "what": "product updates", "url": "https://www.zo.computer/updates", "seen": "2026-10-12" }, { "what": "help centre, deleting an account", "url": "https://support.zocomputer.com/article/how-do-i-delete-my-account", "seen": "2026-10-12" }, { "what": "help centre, who can access data", "url": "https://support.zocomputer.com/article/understanding-data-access-and-privacy-in-our-services-1uvvgwhcoohzycggeo87z0us", "seen": "2026-10-12" }, { "what": "GitHub organisation repositories", "url": "https://api.github.com/orgs/zocomputer/repos?per_page=100\u0026sort=pushed", "seen": "2026-10-12" }, { "what": "desktop app releases", "url": "https://api.github.com/repos/zocomputer/Zo/releases?per_page=10", "seen": "2026-10-12" }, { "what": "MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=zocomputer\u0026limit=20", "seen": "2026-10-12" } ], "openQuestions": [ "Kind chosen: `http-api`. Zo is a hosted assistant, which the brief would call a platform, but it has a documented public HTTP API with an OpenAPI file and an MCP endpoint, so it was graded as a hosted service with an API. The MCP endpoint is not the main surface for a person, who uses chat and messaging", "`assistant.self-hosted` was not claimed. The vendor describes a personal server and self-hosting, but the server runs on Modal or Daytona under the vendor's account", "Whether the assistant asks before sending mail, posting or buying. No approval step was found in the docs read, and the product was not run", "Which OAuth scopes each connected app requests and where the tokens are stored. The security page says Pipedream has no data access while the tool reference says OneDrive and Dropbox work via Pipedream", "What memory stores, where, and whether one memory can be deleted without a factory reset", "Whether an access token can be revoked individually, and whether the MCP endpoint honours persona permissions", "The terms cite an Acceptable Use Policy that was not found, and clause 3 names Substrate Lab", "unchecked: the MCP tool definitions, count and annotations. Listing them needs a token and nothing was sent to api.zo.computer", "unchecked: per-token chat prices on the models pages, and the default `/zo/ask` concurrency limit", "unchecked: the remaining guide pages (tools, skills, bring your own key, devices, payments, hosting) and the 110 tool reference pages other than Use Gmail and List available scopes, which were left unread to limit requests. We made 21 requests to www.zo.computer, above the brief's guide of about fifteen", "unchecked: the zocomputer/agent-sdk and zocomputer/skills repositories, GitHub security advisories for the organisation, and the domain's registration date", "unchecked: whether support, Discord or the help centre answer, and whether a status page exists at an address no page links", "The changelog page shows no entry after the week of 14 September 2026. `lastRelease` is that week's Monday" ] }, "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" }, "notable": [ "The API has four operations, `POST /zo/ask`, `GET /models/available`, `GET /models/catalog` (no authentication) and `GET /personas/available`, described in an OpenAPI 3.1 file with version 1.0.0 (https://www.zo.computer/docs-assets/openapi.json)", "The MCP endpoint at `https://api.zo.computer/mcp` uses HTTP transport and the same bearer token. The guide says all Zo tools are exposed with identical capabilities, and both guides warn that the key grants full access to the workspace (https://www.zo.computer/guide/mcp-server)", "Messaging channels are Discord, Slack, Telegram, SMS and email at yourhandle@zo.computer. In group channels Zo answers only when mentioned and runs on the workspace of the person who mentioned it (https://www.zo.computer/guide/messaging-channels)", "Automations run a prompt on a schedule with the same access as chat, including every connected integration. The guide says Zo confirms before saving an automation, and each run is saved as a conversation showing the tools used (https://www.zo.computer/guide/automations)", "Persona permissions have four presets (All access, Workspace, Read only, Chat only) and 19 custom scopes such as `comms:email`, `shell:execute` and `commerce:manage`, plus one scope for each connected app (https://www.zo.computer/guide/personas)", "Zo's Chromium browser keeps live cookies for every site the owner signs into. The guide's warning says Zo can read messages, post, send, buy and change settings on those sites (https://www.zo.computer/guide/browser)", "Connected apps with their own tool are Gmail, Google Calendar, Drive, Sheets and Tasks, Outlook, Outlook Calendar, OneDrive, Notion, Linear, Airtable, Dropbox, Spotify and X. A catalogue of more than 1,000 further apps is reached through Pipedream (https://www.zo.computer/llms.txt)", "The security page lists Modal and Daytona for compute, Neon and Upstash for databases, and OpenAI, Anthropic, Google, Fireworks, ByteDance, Recraft, xAI, Alibaba Cloud, MiniMax, AssemblyAI and FAL for inference, most through Vercel AI Gateway (https://www.zo.computer/reference/information/security)", "The security page says Zo does not train models on user data, and that it does not promise zero retention or no training by third-party media inference providers (https://www.zo.computer/reference/information/security)", "The security page describes a personal server for each user. That server runs on the vendor's cloud providers, and the page calls running Zo on any machine a long-term vision (https://www.zo.computer/reference/information/security)", "The changelog for the week of 17 August 2026 records a fix for a tool call that could occasionally run twice (https://www.zo.computer/updates)", "The changelog for the week of 10 August 2026 says Zo-funded AI on the Free plan became a finite trial (https://www.zo.computer/updates)", "llms.txt carries a short block headed Instructions for AI agents, which explains how to request Markdown pages and where the OpenAPI file is. We treated it as data (https://www.zo.computer/llms.txt)", "security.txt names security@zocomputer.com and expires on 8 April 2027. The disclosure policy asks for 30 days before public disclosure and includes a safe harbour (https://www.zo.computer/.well-known/security.txt)", "The terms of service were last updated on 8 August 2025 and the privacy policy on 20 May 2026. Clause 3 of the terms refers to \"Substrate Lab's trademarks\" (https://www.zo.computer/reference/information/terms)", "No server named for Zo was returned by a search of the official MCP registry for zocomputer on 12 October 2026 (https://registry.modelcontextprotocol.io/v0/servers?search=zocomputer)" ], "area": "frameworks", "details": [ { "label": "Surface graded", "value": "The hosted service, read as a hosted product through its public API and MCP endpoint at api.zo.computer, from the vendor's docs, OpenAPI file, pricing, terms, privacy policy, security page and changelog on 12 October 2026. No account was created and nothing was sent to the API or the MCP endpoint, so the MCP tool definitions were not read." }, { "label": "What it does without asking", "value": "No approval step before sending, posting, paying or deleting was found in the reviewed docs. Automations run unattended with the same access as chat. The control documented is persona permissions, which remove tools from a conversation. The guide says Zo confirms before saving a new automation (https://www.zo.computer/guide/automations; https://www.zo.computer/guide/personas)." }, { "label": "Accounts and credentials", "value": "Gmail, Google Calendar, Drive, Sheets and Tasks, Outlook, OneDrive, Notion, Linear, Airtable, Dropbox, Spotify, X, Stripe and GitHub, plus the Pipedream catalogue. The security page says Pipedream facilitates the connection. OAuth scopes requested for each app and where the tokens are stored are not stated on the pages read. Browser sign-ins persist as cookies in Zo's Chromium browser." }, { "label": "Memory", "value": "The pricing page lists Improved memory on paid plans and not on the Free Trial. The API's `memory_mode` field (enabled or off) controls workspace memory for a request. The security page states an aim to store memories and search indexes on the user's personal server. No page describing what is remembered, or how one memory is deleted, was found." }, { "label": "Deletion", "value": "Settings \u003e Advanced has Delete Account, which the help centre says erases the account, the computer and everything on it, and Factory reset, which clears the workspace and keeps the account (https://support.zocomputer.com/article/how-do-i-delete-my-account). The privacy policy gives no retention period." }, { "label": "Where it runs", "value": "On the vendor's cloud. The Zo application runs on a per-user server hosted with Modal or Daytona, and the Zo agent and internal services run on Modal and Cloudflare. Prompts, file snippets and conversation history go to the selected model provider. A user's own API key or a Codex or Claude Code subscription can be used instead of Zo-billed models." }, { "label": "Channels", "value": "Web app, desktop app, SMS and MMS, email, Slack, Discord and Telegram. SMS is carried by Telnyx with a stated 10-day message retention and email by Postmark with a stated 45-day retention of addresses and headers." }, { "label": "Monthly cost", "value": "Basic $18 with $10 of AI credit, Pro $64 with $40, Ultra $200 with $100. Free Trial lasts 14 days, after which ordinary computer access ends and files stay retrievable. Automations spend AI credit the same way chat does." }, { "label": "Access by vendor staff", "value": "The help centre says staff do not look at personal data day to day and may access a workspace when that is needed to fix a problem (https://support.zocomputer.com/article/understanding-data-access-and-privacy-in-our-services-1uvvgwhcoohzycggeo87z0us)." }, { "label": "Advisories and incidents", "value": "None found. The vendor publishes no advisory list, incident history or status page on the pages read, and the zocomputer GitHub organisation's repositories were not searched for advisories." } ], "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, "checks": [ { "check": "Legal entity named", "value": "Zo Computer Company", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "zo.computer, no registry record we could read", "points": 0, "max": 15, "state": "no" }, { "check": "Endpoint on the vendor's domain", "value": "api.zo.computer", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 5 of the 7 things a reader expects", "points": 8.3, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 7 of the 8 things a reader expects", "points": 9.3, "max": 10, "state": "part" }, { "check": "Status page", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "valid", "points": 10, "max": 10, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.zo.computer/reference/information/terms", "state": "read", "readAt": "2026-10-12", "statedDate": "2025-08-08", "words": 1343, "points": 8.3, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "Terms of Service last updated: August 8th, 2025", "says": "Last updated 2025-08-08" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "The Agreement will be interpreted according to the laws of the state of New York.", "says": "The law of the State of New York" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "NEITHER PARTY’S TOTAL LIABILITY TO THE OTHER (AGGREGATED ACROSS ALL CLAIMS ARISING IN CONNECTION WITH THIS ZO COMPUTER LICENSE) WILL EXCEED $100.", "says": "Capped at $100" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "Upon termination of the Agreement, any provision which, by its nature or express terms should survive, shall survive such termination or expiration." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "You agree to use the Services in accordance with our Acceptable Use Policy." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "notes": [ { "date": "2026-10-08", "text": "Each party's total liability across all claims is capped at 100 US dollars, outside gross negligence, wilful misconduct and excluded categories.", "quote": "TOTAL LIABILITY TO THE OTHER (AGGREGATED ACROSS ALL CLAIMS ARISING IN CONNECTION WITH THIS ZO COMPUTER LICENSE) WILL EXCEED $100." }, { "date": "2026-10-08", "text": "A claim related to the services must be started within eighteen months of arising or it is barred.", "quote": "the Parties agree that any cause of action you may have arising out of or related to the Services must commence within eighteen (18) months after the cause of action accrues." }, { "date": "2026-10-08", "text": "Zo may anonymise usage data and aggregate it with other data to share publicly.", "quote": "Usage Data is subject to the confidentiality protections under these Terms, provided however that Zo Computer Company may anonymize and aggregate it with other data to be shared publicly" } ] }, { "kind": "privacy", "url": "https://www.zo.computer/reference/information/privacy-policy", "state": "read", "readAt": "2026-10-12", "statedDate": "2026-05-20", "words": 1494, "points": 9.3, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Privacy Policy last updated: May 20th, 2026", "says": "Last updated 2026-05-20" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "This Privacy Policy explains what data we collect, how we use it, and the choices you have." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "Retention: Unless otherwise stated, we retain data as long as necessary for the purposes collected, and longer where required by law or with your consent.", "says": "For as long as needed, with no period named" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "You are responsible for any third-party personal data you provide to us." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "Sale and targeted advertising: We do not sell personal data or process it for targeted advertising.", "says": "Says it does not sell personal data" }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "How to exercise your rights: Contact us using the details above." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": false }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "Transfers to other countries may occur as needed to operate the Service." } ] } ] }, "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" } }, "verify": { "accepts": "a page on zo.computer or one of its subdomains", "badgeUrl": "https://www.anchorterminal.com/badges/zo-computer.svg", "body": { "slug": "zo-computer", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/zo-computer", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/zo-computer\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/zo-computer.svg\" alt=\"Zo Computer on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Zo Computer on Anchor Terminal](https://www.anchorterminal.com/badges/zo-computer.svg)](https://www.anchorterminal.com/tools/zo-computer)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/zo-computer\"\u003eZo Computer on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/zo-computer", "json": "https://www.anchorterminal.com/tools/zo-computer.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/zo-computer.md", "slim": "https://www.anchorterminal.com/tools/zo-computer.min.md" }, "markdown": "## Overview\n\n**Grade E · 43.1/100 · rank #911 of 986 · #13 in Personal assistants · not agent-ready · confidence medium**\n\n\n## Assessment\n\nZo 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Zo Computer Company (https://www.zo.computer) |\n| Kind | HTTP API |\n| Category | Personal assistants (https://www.anchorterminal.com/categories/personal-assistants) |\n| Transport | HTTP |\n| Endpoint | `https://api.zo.computer/mcp` |\n| Auth | API key · 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. |\n| Pricing | Freemium ($18 / mo) · 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). |\n| x402 | No · 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. |\n| Licence | Proprietary service under Zo Computer Company's terms of service |\n| Docs | https://www.zo.computer/guide |\n| llms.txt | https://www.zo.computer/llms.txt |\n| Last release | 2026-09-14 |\n| Surface graded | The hosted service, read as a hosted product through its public API and MCP endpoint at api.zo.computer, from the vendor's docs, OpenAPI file, pricing, terms, privacy policy, security page and changelog on 12 October 2026. No account was created and nothing was sent to the API or the MCP endpoint, so the MCP tool definitions were not read. |\n| What it does without asking | No approval step before sending, posting, paying or deleting was found in the reviewed docs. Automations run unattended with the same access as chat. The control documented is persona permissions, which remove tools from a conversation. The guide says Zo confirms before saving a new automation (https://www.zo.computer/guide/automations; https://www.zo.computer/guide/personas). |\n| Accounts and credentials | Gmail, Google Calendar, Drive, Sheets and Tasks, Outlook, OneDrive, Notion, Linear, Airtable, Dropbox, Spotify, X, Stripe and GitHub, plus the Pipedream catalogue. The security page says Pipedream facilitates the connection. OAuth scopes requested for each app and where the tokens are stored are not stated on the pages read. Browser sign-ins persist as cookies in Zo's Chromium browser. |\n| Memory | The pricing page lists Improved memory on paid plans and not on the Free Trial. The API's `memory_mode` field (enabled or off) controls workspace memory for a request. The security page states an aim to store memories and search indexes on the user's personal server. No page describing what is remembered, or how one memory is deleted, was found. |\n| Deletion | Settings \u003e Advanced has Delete Account, which the help centre says erases the account, the computer and everything on it, and Factory reset, which clears the workspace and keeps the account (https://support.zocomputer.com/article/how-do-i-delete-my-account). The privacy policy gives no retention period. |\n| Where it runs | On the vendor's cloud. The Zo application runs on a per-user server hosted with Modal or Daytona, and the Zo agent and internal services run on Modal and Cloudflare. Prompts, file snippets and conversation history go to the selected model provider. A user's own API key or a Codex or Claude Code subscription can be used instead of Zo-billed models. |\n| Channels | Web app, desktop app, SMS and MMS, email, Slack, Discord and Telegram. SMS is carried by Telnyx with a stated 10-day message retention and email by Postmark with a stated 45-day retention of addresses and headers. |\n| Monthly cost | Basic $18 with $10 of AI credit, Pro $64 with $40, Ultra $200 with $100. Free Trial lasts 14 days, after which ordinary computer access ends and files stay retrievable. Automations spend AI credit the same way chat does. |\n| Access by vendor staff | The help centre says staff do not look at personal data day to day and may access a workspace when that is needed to fix a problem (https://support.zocomputer.com/article/understanding-data-access-and-privacy-in-our-services-1uvvgwhcoohzycggeo87z0us). |\n| Advisories and incidents | None found. The vendor publishes no advisory list, incident history or status page on the pages read, and the zocomputer GitHub organisation's repositories were not searched for advisories. |\n| Capabilities | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory, agent.mcp-client |\n| Tags | official, hosted, closed-source, assistant, mcp, openapi, llms-txt, free-trial |\n| JSON | https://www.anchorterminal.com/api/v1/tools/zo-computer.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-12 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 15 | 3.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 73 | 11.9 |\n| Agent ergonomics | 13% | 16.2 | 34 | 5.5 |\n| Security \u0026 auth | 14% | 17.5 | 37 | 6.5 |\n| Payments \u0026 pricing | 10% | 12.5 | 40 | 5.0 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 68 | 6.0 |\n| Transparency \u0026 trust (editorial 46, provenance 73) | 7% | 8.8 | 60 | 5.2 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **43.1 → E** |\n\n### Why each score\n\n- Reliability 15: Read with the hosted lines. No status page is linked from the home page, docs index, security page or help centre home (0). With no incident history to read, 5. No rate limit is published with numbers. The changelog of 7 September 2026 says the owner can set a concurrency limit for `/zo/ask` in Advanced settings, with no default figure given (0). No 429, Retry-After, backoff or idempotency guidance for the API was found (0). No SLA, and the terms supply the service as is (0). The API is at version 1.0.0 in its OpenAPI file and is not labelled beta (10). Total 15.\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 73: Graded on the HTTP API, with the MCP endpoint's tool definitions unread because listing them needs a token. A public OpenAPI 3.1 file covers all four operations (25). llms.txt and a Markdown copy of every guide and reference page (10). Field and tool descriptions state purpose in one line and seldom say when not to use something (10 of 20). The ask request is typed with one required field and an enum for `memory_mode`, while the work itself is a free-text prompt (10 of 15). The guide has curl and Python examples for continuing a conversation, structured output and streaming. Documented errors are a 422 validation schema, an error response schema and an SSE `Error` event, with no list of codes (8 of 15). A dated weekly changelog is public and the spec has a version, but the paths carry none and the guide omits `memory_mode`, which the spec defines (10 of 15). Total 73.\n- Agent ergonomics 34: The HTTP API is four operations, and `output_format` takes a JSON Schema so a caller can size the answer. The MCP guide says all Zo tools are exposed, and llms.txt lists 110 tool reference pages, which is well over 30. Persona permissions can remove tools, though whether the MCP endpoint honours a persona was not established (10 of 25). Structured output and streaming control output, with no pagination or filtering on the list operations (8 of 20). Errors are a validation schema and a message string with no documented codes or recovery advice (6 of 20). No idempotency key or retry guidance for `/zo/ask`, MCP annotations were not read, and the changelog for the week of 17 August 2026 records a fix for a tool call that could run twice (2 of 20). Only `input` is required and defaults are sensible. An agent-sdk repository exists under the vendor's GitHub organisation but is not mentioned in the docs we read (8 of 15). Total 34.\n- Security \u0026 auth 37: One bearer token created in Settings, which both guides say grants full access to the workspace, and with it the shell, every connected account and every browser session. No scopes, expiry or rotation are documented (10 of 30). Persona permissions have four presets and 19 scopes and remove tools from a conversation, and a caller can pass `persona_id`, but the token is not bound to a persona. No approval step before sending, buying or deleting was found, and the browser guide says Zo can buy and send on signed-in sites (8 of 20). The assistant reads mail, web pages and channel messages. The security page says the design is not without risks and asks researchers to report prompt injection findings, with no mitigation or guidance documented (4 of 15). Each automation run and conversation is saved with the tools it used, with no audit log of API token use documented (7 of 15). A valid security.txt and a disclosure policy with a safe harbour and a 30-day window. No bounty terms, SOC 2 or ISO 27001 report, or advisory list was found (8 of 20). Total 37.\n- Payments \u0026 pricing 40: No x402, MPP or L402 (0). Plan prices, included credit and per-request media prices are public without a login, and the billing guide says chat follows listed token rates (20). The Free Trial runs 14 days and the home page says no credit card is required (20). A person signs up in a browser behind a Turnstile check and creates the token in Settings, so an agent cannot get access by itself (0). Total 40.\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 68: The newest dated changelog entry is the week of 14 September 2026, 28 days before this check, followed by a September summary. No entry for the three weeks since was on the page (30). Nine weekly entries fall in the last 90 days (20). A public changelog, a Discord community and a help centre with a route to a person. We did not test whether they answer (9 of 15). No official SDK is documented for the API and the official MCP registry returned no server for zocomputer. The desktop app's last GitHub release is v1.5.13 of 13 August 2026 (4 of 15). Package health does not apply to a closed service, and half marks rest on the changelog's steady run of fixes (5 of 10). Total 68.\n- Transparency \u0026 trust 60: Closed source with public terms. The terms are 18 short clauses last updated on 8 August 2025, cite an Acceptable Use Policy we did not find, name \"Substrate Lab's trademarks\" in clause 3, and say credits are bought in advance while the product is sold by subscription (12 of 30). The privacy policy of 20 May 2026 lists only email address, trackers, usage data and SMS data, gives no retention period, and does not describe workspace files, memory or connected-account data. The security page fills part of that gap, with stated retention for Postmark (45 days) and Telnyx (10 days), and the help centre says deleting the account erases the computer. No DPA was found (14 of 30). The changelog announces retired and deprecated models and says retired models forward to a successor, with no deprecation policy or notice period for the API (6 of 20). The security page names each provider and marks which can see user content. Data locations are given only for Fireworks, as US-based (14 of 20). Total 46.\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (24 items): https://www.anchorterminal.com/fixes/zo-computer.md (JSON https://www.anchorterminal.com/fixes/zo-computer.json)\n\n### What we couldn't check\n\n- Kind chosen: `http-api`. Zo is a hosted assistant, which the brief would call a platform, but it has a documented public HTTP API with an OpenAPI file and an MCP endpoint, so it was graded as a hosted service with an API. The MCP endpoint is not the main surface for a person, who uses chat and messaging\n- `assistant.self-hosted` was not claimed. The vendor describes a personal server and self-hosting, but the server runs on Modal or Daytona under the vendor's account\n- Whether the assistant asks before sending mail, posting or buying. No approval step was found in the docs read, and the product was not run\n- Which OAuth scopes each connected app requests and where the tokens are stored. The security page says Pipedream has no data access while the tool reference says OneDrive and Dropbox work via Pipedream\n- What memory stores, where, and whether one memory can be deleted without a factory reset\n- Whether an access token can be revoked individually, and whether the MCP endpoint honours persona permissions\n- The terms cite an Acceptable Use Policy that was not found, and clause 3 names Substrate Lab\n- unchecked: the MCP tool definitions, count and annotations. Listing them needs a token and nothing was sent to api.zo.computer\n- unchecked: per-token chat prices on the models pages, and the default `/zo/ask` concurrency limit\n- unchecked: the remaining guide pages (tools, skills, bring your own key, devices, payments, hosting) and the 110 tool reference pages other than Use Gmail and List available scopes, which were left unread to limit requests. We made 21 requests to www.zo.computer, above the brief's guide of about fifteen\n- unchecked: the zocomputer/agent-sdk and zocomputer/skills repositories, GitHub security advisories for the organisation, and the domain's registration date\n- unchecked: whether support, Discord or the help centre answer, and whether a status page exists at an address no page links\n- The changelog page shows no entry after the week of 14 September 2026. `lastRelease` is that week's Monday\n\n### Sources\n\n- home page: \u003chttps://www.zo.computer/\u003e (seen 2026-10-12)\n- robots.txt: \u003chttps://www.zo.computer/robots.txt\u003e (seen 2026-10-12)\n- llms.txt: \u003chttps://www.zo.computer/llms.txt\u003e (seen 2026-10-12)\n- security.txt: \u003chttps://www.zo.computer/.well-known/security.txt\u003e (seen 2026-10-12)\n- pricing: \u003chttps://www.zo.computer/pricing\u003e (seen 2026-10-12)\n- subscription guide: \u003chttps://www.zo.computer/guide/billing.md\u003e (seen 2026-10-12)\n- API guide: \u003chttps://www.zo.computer/guide/api.md\u003e (seen 2026-10-12)\n- API reference: \u003chttps://www.zo.computer/reference/api-reference.md\u003e (seen 2026-10-12)\n- OpenAPI file: \u003chttps://www.zo.computer/docs-assets/openapi.json\u003e (seen 2026-10-12)\n- MCP server guide: \u003chttps://www.zo.computer/guide/mcp-server.md\u003e (seen 2026-10-12)\n- messaging channels guide: \u003chttps://www.zo.computer/guide/messaging-channels.md\u003e (seen 2026-10-12)\n- automations guide: \u003chttps://www.zo.computer/guide/automations.md\u003e (seen 2026-10-12)\n- personas and permissions guide: \u003chttps://www.zo.computer/guide/personas.md\u003e (seen 2026-10-12)\n- browser use guide: \u003chttps://www.zo.computer/guide/browser.md\u003e (seen 2026-10-12)\n- Use Gmail tool reference: \u003chttps://www.zo.computer/reference/tools/use-app-gmail.md\u003e (seen 2026-10-12)\n- security page: \u003chttps://www.zo.computer/reference/information/security.md\u003e (seen 2026-10-12)\n- terms of service: \u003chttps://www.zo.computer/reference/information/terms.md\u003e (seen 2026-10-12)\n- privacy policy: \u003chttps://www.zo.computer/reference/information/privacy-policy.md\u003e (seen 2026-10-12)\n- product updates: \u003chttps://www.zo.computer/updates\u003e (seen 2026-10-12)\n- help centre, deleting an account: \u003chttps://support.zocomputer.com/article/how-do-i-delete-my-account\u003e (seen 2026-10-12)\n- help centre, who can access data: \u003chttps://support.zocomputer.com/article/understanding-data-access-and-privacy-in-our-services-1uvvgwhcoohzycggeo87z0us\u003e (seen 2026-10-12)\n- GitHub organisation repositories: \u003chttps://api.github.com/orgs/zocomputer/repos?per_page=100\u0026sort=pushed\u003e (seen 2026-10-12)\n- desktop app releases: \u003chttps://api.github.com/repos/zocomputer/Zo/releases?per_page=10\u003e (seen 2026-10-12)\n- MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=zocomputer\u0026limit=20\u003e (seen 2026-10-12)\n\n## Who's behind it (provenance 73/100, checked 2026-10-12)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Zo Computer Company | 20/20 |\n| Domain age | zo.computer, no registry record we could read | 0/15 |\n| Endpoint on the vendor's domain | api.zo.computer | 15/15 |\n| Terms of service | read, states 5 of the 7 things a reader expects | 8.3/10 |\n| Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 |\n| Status page | not found | 0/10 |\n| Changelog | published | 10/10 |\n| security.txt | valid | 10/10 |\n\nThe 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.\n\nThe terms refer to an Acceptable Use Policy that we did not find linked from the pages read.\n\nsecurity.txt at www.zo.computer/.well-known/security.txt gives a contact, a policy link and an expiry of 8 April 2027.\n\nNo status page is linked from the home page, the docs index, the security page or the help centre home page.\n\nThe API and MCP endpoint are on api.zo.computer. The domain's registration date was not looked up.\n\nThe X handle is the one the home page footer links.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.zo.computer/reference/information/terms), read 2026-10-12, dated 2025-08-08, states 5 of the 7 things a reader expects.\n\n- Gives the date it was last updated. Last updated 2025-08-08.\n- Names the governing law or courts. The law of the State of New York.\n- States a limit on its liability. Capped at $100.\n- Not found in the text. Says how changes to the terms are announced.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-10-08). Each party's total liability across all claims is capped at 100 US dollars, outside gross negligence, wilful misconduct and excluded categories. \"TOTAL LIABILITY TO THE OTHER (AGGREGATED ACROSS ALL CLAIMS ARISING IN CONNECTION WITH THIS ZO COMPUTER LICENSE) WILL EXCEED $100.\"\n- Also in the text (2026-10-08). A claim related to the services must be started within eighteen months of arising or it is barred. \"the Parties agree that any cause of action you may have arising out of or related to the Services must commence within eighteen (18) months after the cause of action accrues.\"\n- Also in the text (2026-10-08). Zo may anonymise usage data and aggregate it with other data to share publicly. \"Usage Data is subject to the confidentiality protections under these Terms, provided however that Zo Computer Company may anonymize and aggregate it with other data to be shared publicly\"\n\n**Privacy policy** (https://www.zo.computer/reference/information/privacy-policy), read 2026-10-12, dated 2026-05-20, states 7 of the 8 things a reader expects.\n\n- Gives the date it was last updated. Last updated 2026-05-20.\n- Says how long data is kept. For as long as needed, with no period named.\n- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.\n- Not found in the text. Gives a privacy contact.\n\n## Live (updated 2026-10-12 19:01 UTC)\n\n- Right now: up, HTTP 405, 472 ms, checked 2026-10-12 19:01 UTC (get on `https://api.zo.computer/mcp`)\n- Uptime 24h 100.0% (18 probes) · 30 days 100.0% (18 probes) · p50 320 ms · p95 1.2 s\n- Always current: https://www.anchorterminal.com/api/v1/live/zo-computer.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Basic plan | $18 | per month (plan) | Includes $10 of AI credit a month. |\n| Pro plan | $64 | per month (plan) | Includes $40 of AI credit a month. |\n| Ultra plan | $200 | per month (plan) | Includes $100 of AI credit a month. |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- OpenAPI 3.1 file, llms.txt and a Markdown copy of every guide and reference page are public\n- Persona permissions remove tools from a conversation, with 19 named scopes and a Read only preset\n- The security page names each infrastructure, inference and tool provider and states which can see user content\n- Plan prices, included AI credit and per-request media prices are public, with a 14-day trial that needs no card\n- Dated weekly changelog, with nine weekly entries between 20 July and 14 September 2026\n\n## Weaknesses\n\n- The access token for the API and MCP endpoint grants full access to the workspace, with no scoped or read-only token documented\n- No approval step before sending mail, posting or buying was found. The browser guide says Zo can buy and send on signed-in sites\n- No status page, incident history, rate limit figures or SLA were found on the pages read\n- The privacy policy lists only email address, trackers, usage data and SMS data, and does not describe workspace files, memory or connected accounts\n- Memory storage and deletion are not documented beyond a design aim and whole-account deletion or factory reset\n\n## Before you call it (notes for agents)\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## Connect\n\nFirst request:\n\n```bash\ncurl -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!\"}'\n```\n\nClaude Code:\n\n```bash\nclaude mcp add --transport http zo https://api.zo.computer/mcp --header \"Authorization: Bearer zo_sk_your_key_here\"\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"zo\": {\n \"headers\": {\n \"Authorization\": \"Bearer zo_sk_your_key_here\"\n },\n \"type\": \"http\",\n \"url\": \"https://api.zo.computer/mcp\"\n }\n }\n}\n```\n\nThrough letme (picks today, calling later): https://letme.dev/zo-computer. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| ZeroClaw | BB | 70.2 | 161 | assistant.proactive, assistant.messaging, assistant.memory, assistant.accounts, agent.mcp-client | no | https://www.anchorterminal.com/tools/zeroclaw.md |\n| NanoClaw | B | 68.3 | 229 | assistant.proactive, assistant.messaging, assistant.memory, agent.mcp-client, assistant.accounts | no | https://www.anchorterminal.com/tools/nanoclaw.md |\n| Hermes Agent | B | 67.9 | 244 | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory, agent.mcp-client | no | https://www.anchorterminal.com/tools/hermes-agent.md |\n| OpenClaw | B | 67.1 | 270 | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory, agent.mcp-client | no | https://www.anchorterminal.com/tools/openclaw.md |\n| IronClaw | B | 66.7 | 288 | assistant.proactive, assistant.messaging, assistant.accounts, assistant.memory, agent.mcp-client | no | https://www.anchorterminal.com/tools/ironclaw.md |\n| nanobot | B | 62.4 | 446 | assistant.proactive, assistant.messaging, assistant.memory, assistant.accounts, agent.mcp-client | no | https://www.anchorterminal.com/tools/nanobot.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The API has four operations, `POST /zo/ask`, `GET /models/available`, `GET /models/catalog` (no authentication) and `GET /personas/available`, described in an OpenAPI 3.1 file with version 1.0.0 (source: \u003chttps://www.zo.computer/docs-assets/openapi.json\u003e)\n- The MCP endpoint at `https://api.zo.computer/mcp` uses HTTP transport and the same bearer token. The guide says all Zo tools are exposed with identical capabilities, and both guides warn that the key grants full access to the workspace (source: \u003chttps://www.zo.computer/guide/mcp-server\u003e)\n- Messaging channels are Discord, Slack, Telegram, SMS and email at yourhandle@zo.computer. In group channels Zo answers only when mentioned and runs on the workspace of the person who mentioned it (source: \u003chttps://www.zo.computer/guide/messaging-channels\u003e)\n- Automations run a prompt on a schedule with the same access as chat, including every connected integration. The guide says Zo confirms before saving an automation, and each run is saved as a conversation showing the tools used (source: \u003chttps://www.zo.computer/guide/automations\u003e)\n- Persona permissions have four presets (All access, Workspace, Read only, Chat only) and 19 custom scopes such as `comms:email`, `shell:execute` and `commerce:manage`, plus one scope for each connected app (source: \u003chttps://www.zo.computer/guide/personas\u003e)\n- Zo's Chromium browser keeps live cookies for every site the owner signs into. The guide's warning says Zo can read messages, post, send, buy and change settings on those sites (source: \u003chttps://www.zo.computer/guide/browser\u003e)\n- Connected apps with their own tool are Gmail, Google Calendar, Drive, Sheets and Tasks, Outlook, Outlook Calendar, OneDrive, Notion, Linear, Airtable, Dropbox, Spotify and X. A catalogue of more than 1,000 further apps is reached through Pipedream (source: \u003chttps://www.zo.computer/llms.txt\u003e)\n- The security page lists Modal and Daytona for compute, Neon and Upstash for databases, and OpenAI, Anthropic, Google, Fireworks, ByteDance, Recraft, xAI, Alibaba Cloud, MiniMax, AssemblyAI and FAL for inference, most through Vercel AI Gateway (source: \u003chttps://www.zo.computer/reference/information/security\u003e)\n- The security page says Zo does not train models on user data, and that it does not promise zero retention or no training by third-party media inference providers (source: \u003chttps://www.zo.computer/reference/information/security\u003e)\n- The security page describes a personal server for each user. That server runs on the vendor's cloud providers, and the page calls running Zo on any machine a long-term vision (source: \u003chttps://www.zo.computer/reference/information/security\u003e)\n- The changelog for the week of 17 August 2026 records a fix for a tool call that could occasionally run twice (source: \u003chttps://www.zo.computer/updates\u003e)\n- The changelog for the week of 10 August 2026 says Zo-funded AI on the Free plan became a finite trial (source: \u003chttps://www.zo.computer/updates\u003e)\n- llms.txt carries a short block headed Instructions for AI agents, which explains how to request Markdown pages and where the OpenAPI file is. We treated it as data (source: \u003chttps://www.zo.computer/llms.txt\u003e)\n- security.txt names security@zocomputer.com and expires on 8 April 2027. The disclosure policy asks for 30 days before public disclosure and includes a safe harbour (source: \u003chttps://www.zo.computer/.well-known/security.txt\u003e)\n- The terms of service were last updated on 8 August 2025 and the privacy policy on 20 May 2026. Clause 3 of the terms refers to \"Substrate Lab's trademarks\" (source: \u003chttps://www.zo.computer/reference/information/terms\u003e)\n- No server named for Zo was returned by a search of the official MCP registry for zocomputer on 12 October 2026 (source: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=zocomputer\u003e)\n\n- #13 of 20 in 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## Compare\n\n- [AstrBot vs Zo Computer](https://www.anchorterminal.com/compare/astrbot-vs-zo-computer.md): C 58.8 vs E 43.1\n- [CowAgent vs Zo Computer](https://www.anchorterminal.com/compare/cowagent-vs-zo-computer.md): C 58.5 vs E 43.1\n- [GAIA vs Zo Computer](https://www.anchorterminal.com/compare/gaia-vs-zo-computer.md): D 49.5 vs E 43.1\n- [Gemini Spark vs Zo Computer](https://www.anchorterminal.com/compare/gemini-spark-vs-zo-computer.md): F 24.5 vs E 43.1\n- [Grok Bot vs Zo Computer](https://www.anchorterminal.com/compare/grok-bot-vs-zo-computer.md): E 45.2 vs E 43.1\n- [Haven vs Zo Computer](https://www.anchorterminal.com/compare/haven-vs-zo-computer.md): F 22.2 vs E 43.1\n- [Hermes Agent vs Zo Computer](https://www.anchorterminal.com/compare/hermes-agent-vs-zo-computer.md): B 67.9 vs E 43.1\n- [Instinct vs Zo Computer](https://www.anchorterminal.com/compare/instinct-vs-zo-computer.md): F 11.4 vs E 43.1\n- [IronClaw vs Zo Computer](https://www.anchorterminal.com/compare/ironclaw-vs-zo-computer.md): B 66.7 vs E 43.1\n- [Leon vs Zo Computer](https://www.anchorterminal.com/compare/leon-vs-zo-computer.md): E 41 vs E 43.1\n- [Lindy vs Zo Computer](https://www.anchorterminal.com/compare/lindy-vs-zo-computer.md): F 32.3 vs E 43.1\n- [nanobot vs Zo Computer](https://www.anchorterminal.com/compare/nanobot-vs-zo-computer.md): B 62.4 vs E 43.1\n- [NanoClaw vs Zo Computer](https://www.anchorterminal.com/compare/nanoclaw-vs-zo-computer.md): B 68.3 vs E 43.1\n- [Dots vs Zo Computer](https://www.anchorterminal.com/compare/openai-dots-vs-zo-computer.md): F 28.3 vs E 43.1\n- [OpenClaw vs Zo Computer](https://www.anchorterminal.com/compare/openclaw-vs-zo-computer.md): B 67.1 vs E 43.1\n- [PicoClaw vs Zo Computer](https://www.anchorterminal.com/compare/picoclaw-vs-zo-computer.md): D 46.1 vs E 43.1\n- [Poke vs Zo Computer](https://www.anchorterminal.com/compare/poke-vs-zo-computer.md): F 37.6 vs E 43.1\n- [QwenPaw vs Zo Computer](https://www.anchorterminal.com/compare/qwenpaw-vs-zo-computer.md): B 62.2 vs E 43.1\n- [ZeroClaw vs Zo Computer](https://www.anchorterminal.com/compare/zeroclaw-vs-zo-computer.md): BB 70.2 vs E 43.1\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on zo.computer or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"zo-computer\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/zo-computer\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/zo-computer.svg\" alt=\"Zo Computer on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Zo Computer on Anchor Terminal](https://www.anchorterminal.com/badges/zo-computer.svg)](https://www.anchorterminal.com/tools/zo-computer)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/zo-computer\"\u003eZo Computer on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Zo Computer is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/zo-computer-dark.png\n- Light: https://www.anchorterminal.com/assets/share/zo-computer-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Personal assistants", "url": "https://www.anchorterminal.com/categories/personal-assistants" }, { "name": "Zo Computer", "url": "" } ], "description": "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.", "facts": [ "rank #911 of 986", "API key auth", "0 desk reviews" ], "h1": "Zo Computer", "image": "https://www.anchorterminal.com/assets/og/tools-zo-computer.png", "path": "/tools/zo-computer", "published": "2026-10-01", "section": "tools", "title": "Zo Computer review (2026): pricing, alternatives and grade E", "toc": null, "updated": "2026-10-12", "url": "https://www.anchorterminal.com/tools/zo-computer" }, "tokens": { "markdown": 8650, "slim": 2080 }, "version": 1 }