# letme vs One > 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. - Canonical: https://www.anchorterminal.com/compare/letme-vs-one - Markdown: https://www.anchorterminal.com/compare/letme-vs-one.md (~2,350 tokens) - Slim: https://www.anchorterminal.com/compare/letme-vs-one.min.md (~830 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/letme-vs-one.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.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: grade F, 36.4/100, rank #929 of 950. Markdown https://www.anchorterminal.com/tools/letme.md · JSON https://www.anchorterminal.com/api/v1/tools/letme.json - One: grade B, 66.6/100, rank #282 of 950. Markdown https://www.anchorterminal.com/tools/one.md · JSON https://www.anchorterminal.com/api/v1/tools/one.json - Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md - All 28 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md ## Which one, for what ### letme (F) 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 in its favour: - No key needed to call it Watch for: Calling through letme, the key and x402 top-ups are specified and not open (calling.open is false in every answer), so an agent still needs each tool's own key or x402 route ### One (B) 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 in its favour: - Runs on your own machine Watch for: The remote server's tools changed from four to three by 30 September 2026, and the site's changelog, last dated 13 July 2026, has no entry for it ## Score by category | Category | Weight | letme | One | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 10 | 82 | One +72 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 68 | 77 | One +9 | | Agent ergonomics | 13% (16.2 this run) | 54 | 73 | One +19 | | Security & auth | 14% (17.5 this run) | 23 | 69 | One +46 | | Payments & pricing | 10% (12.5 this run) | 50 | 30 | letme +20 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 35 | 86 | One +51 | | Transparency & trust | 7% (8.8 this run) | 37 | 63 | One +26 | | Negative events | ≤15 | -2 | -3 | | | **Total** | | **36.4 · F** | **66.6 · B** | | ## Facts side by side | Fact | 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 | | x402 | no | no | | 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 | | Read-only variant documented | no | no | | llms.txt | yes | yes | | 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 | ## Verdicts **letme.** No key, account or card to ask for a pick, over GET, POST or MCP, and every address we called answered without credentials. Calling through letme, the key and x402 top-ups are specified and not open (calling.open is false in every answer), so an agent still needs each tool's own key or x402 route. **One.** One's remote MCP server has three tools, OAuth 2.1 sign-in with PKCE and a consent screen that sets read only, read and write, full or per-action access for each connection. A person must sign in through a browser, the SOC 2 audit is unfinished, and the site's changelog stops at 13 July 2026. ## Before you call either ### letme 1. Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes 2. Add not= to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer 3. Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low 4. Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404 5. Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey= ### One 1. Call `list_one_integrations` first and read each connection's `access` field. When the policy is `actions`, run those ids directly without calling `find_one_actions` 2. Send every operation a task needs in one `find_one_actions` call, up to 10 `requests`, each a platform and a short intent with no IDs, names or message text 3. When a document comes back as a digest, call `find_one_actions` again with `load` and a `section` name. Don't guess parameters the digest left out 4. After a timeout on `execute_one_action`, check whether the write took effect before sending it again. No idempotency key is documented 5. A 403 for a call outside the grant won't succeed on retry. Ask the user to widen the grant in the dashboard or reconnect ## Questions ### Which is better for AI agents, letme or One? 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. ### Do letme and One need an API key? letme needs no key. One takes an API key or an OAuth sign-in. ### Can an agent call letme and One without installing anything? Yes. letme has a hosted endpoint at https://letme.dev and One at https://mcp.withone.ai/mcp. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/letme-vs-one.json, and with the fewest tokens: https://www.anchorterminal.com/compare/letme-vs-one.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "letme", "b": "one"}`. From a terminal: `anchor compare letme one` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/letme.json and https://www.anchorterminal.com/api/v1/tools/one.json ## Other comparisons with letme or One - [Composio (API + MCP) vs One](https://www.anchorterminal.com/compare/composio-rube-vs-one.md) - [Merge Agent Handler vs One](https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.md) - [One vs Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md) - [One vs StackOne](https://www.anchorterminal.com/compare/one-vs-stackone.md) - [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md) - [One vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/one-vs-zapier-mcp.md) - [Composio (API + MCP) vs letme](https://www.anchorterminal.com/compare/composio-rube-vs-letme.md) - [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md) - [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md) - [letme vs StackOne](https://www.anchorterminal.com/compare/letme-vs-stackone.md) - [letme vs Unified.to MCP Server](https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.md) - [letme vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/letme-vs-zapier-mcp.md) ## Disclosure - letme is Anchor Terminal's own product, run by the same company and founder. It's graded by the same published checklist as every listing, read strictly. Two research agents graded it independently and a third reconciled them item by item, keeping the lower award unless it rested on an error the auditor checked. letme never picks it. Since 5 October 2026 the review panel reviews it like any listing, told that it's our own product and to be neither kinder nor harsher.