# Boski vs Orchid (slim) > Boski scores 26.2 (F) to Orchid's 20.2 (F) for assistants reached by message. Prices, MCP, x402, uptime and agent notes side by side. - Full: https://www.anchorterminal.com/compare/boski-vs-orchid-ai.md (~3,250 tokens) · this version ~480 tokens · JSON https://www.anchorterminal.com/compare/boski-vs-orchid-ai.json · canonical https://www.anchorterminal.com/compare/boski-vs-orchid-ai - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-13 Boski scores 26.2 (F) on agent readiness against Orchid's 20.2 (F), and leads in 4 of 7 scored categories. Orchid leads on reliability. Both do assistants reached by message. - Boski: F 26.2, rank #981 of 1010 · https://www.anchorterminal.com/tools/boski.min.md - Orchid: F 20.2, rank #992 of 1010 · https://www.anchorterminal.com/tools/orchid-ai.min.md - Boski, good for People who want an agent working on personal goals between conversations, and who want ChatGPT or Codex to read their saved preferences. Ahead on Schema & documentation, 15 against 10; Agent ergonomics, 13 against 0; Security & auth, 45 against 0. - Orchid, good for A founder or operator who wants Gmail and calendar triage by text with approval before anything leaves. Ahead on Reliability, 50 against 25. | Category | Boski | Orchid | | --- | --- | --- | | Reliability (16%) | 25 | 50 | | Performance (10%) | pending | pending | | Schema & documentation (13%) | 15 | 10 | | Agent ergonomics (13%) | 13 | 0 | | Security & auth (14%) | 45 | 0 | | Payments & pricing (10%) | 10 | 10 | | Task success (10%) | pending | pending | | Maintenance & community (7%) | 23 | 24 | | Transparency & trust (7%) | 63 | 60 | | Fact (where they differ) | Boski | Orchid | | --- | --- | --- | | Vendor | Boski, Inc. | Zero Email, Inc. | | Licence | Closed service under Boski's Terms of Service (Boski, Inc., a Delaware corporation, effective 20 August 2026). | Closed service under Orchid's Terms of Service (Zero Email, Inc., last updated 16 January 2026). | | Read-only variant documented | yes | no |