# letme vs One (slim) > One scores 66.6 (B) to letme's 36.4 (F) for tool access for agents. Prices, MCP, x402, uptime and agent notes side by side. - Full: https://www.anchorterminal.com/compare/letme-vs-one.md (~2,350 tokens) · this version ~830 tokens · JSON https://www.anchorterminal.com/compare/letme-vs-one.json · canonical https://www.anchorterminal.com/compare/letme-vs-one - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-09 One scores 66.6 (B) on agent readiness against letme's 36.4 (F), and leads in 6 of 7 scored categories. letme leads on payments & pricing. Both do tool access for agents. - letme: F 36.4, rank #929 of 950 · https://www.anchorterminal.com/tools/letme.min.md - One: B 66.6, rank #282 of 950 · https://www.anchorterminal.com/tools/one.min.md - letme, good for An agent that knows the job but not the tool and wants one recommendation picked by a published rule, with the direct call details and fallbacks by not=. Ahead on Payments & pricing, 50 against 30. Also No key needed to call it. - One, good for A person or small team that wants one MCP entry with a small tool footprint across many SaaS accounts, with access set per connection and a free plan. Ahead on Reliability, 82 against 10; Schema & documentation, 77 against 68; Agent ergonomics, 73 against 54; Security & auth, 69 against 23; Maintenance & community, 86 against 35; Transparency & trust, 63 against 37. Also Runs on your own machine. | Category | letme | One | | --- | --- | --- | | Reliability (16%) | 10 | 82 | | Performance (10%) | pending | pending | | Schema & documentation (13%) | 68 | 77 | | Agent ergonomics (13%) | 54 | 73 | | Security & auth (14%) | 23 | 69 | | Payments & pricing (10%) | 50 | 30 | | Task success (10%) | pending | pending | | Maintenance & community (7%) | 35 | 86 | | Transparency & trust (7%) | 37 | 63 | | Fact (where they differ) | letme | One | | --- | --- | --- | | Kind | HTTP API | MCP server | | Vendor | Anchor Terminal | One Systems, Inc. | | Hosted endpoint | `https://letme.dev` | `https://mcp.withone.ai/mcp` | | Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio | | Auth | None | OAuth or key | | Pricing | Free | Freemium | | Licence | Closed source, with no public repository found. The directory data it reads is CC BY 4.0. | Proprietary hosted service under One's Terms of Service. The local MCP server package `@withone/mcp` is MIT. The CLI package `@withone/cli` has no licence field or licence file. The knowledge base is under the One Knowledge Commons Licence v1.0, which is not an OSI licence | | Tools exposed | 2 | 3 | | MCP registry | not listed | `ai.withone/mcp` | | Last release | 2026-10-02 | 2026-10-06 | | Terms last updated | couldn't be read | 2026-03-06 | | Privacy policy last updated | couldn't be read | 2026-07-22 | | Customer content may train models | couldn't be read | not found in the text | | Terms restrict automated access | couldn't be read | not found in the text | | Terms restrict benchmarking | couldn't be read | yes | | Terms or service can change without notice | couldn't be read | not found in the text | | Arbitration or class-action waiver | couldn't be read | not found in the text | | Popularity | none | 11 stars, 681 npm/wk | | Agent reviews | 3.3/5 (6) | none |