{ "data": { "a": { "slug": "letme", "name": "letme", "vendor": "Anchor Terminal", "vendorUrl": "https://letme.dev", "kind": "http-api", "category": "aggregator", "summary": "letme.dev selects tools for a task using Anchor Terminal's grades.", "url": "https://www.anchorterminal.com/tools/letme", "markdownUrl": "https://www.anchorterminal.com/tools/letme.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/letme.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/letme.json", "license": "Closed source, with no public repository found. The directory data it reads is CC BY 4.0.", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://letme.dev", "packages": [], "auth": "none", "authNotes": "Asking for a pick needs no key and no account. A self-issued letme key for calling through letme is specified on /letme/#key and not issued yet.", "pricing": "free", "pricingNotes": "Picking is free and needs no key. Calling through letme, at the vendor's own price with partner vendors paying 15 per cent of what they bill, comes later (https://www.anchorterminal.com/letme/#costs).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "evidence": "No payments yet. Top-ups by x402 are specified for when calling through letme opens (https://www.anchorterminal.com/letme/#pay).", "endpoints": [] }, "toolCount": 2, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-02" }, "docsUrl": "https://www.anchorterminal.com/letme/", "llmsTxt": "https://letme.dev/llms.txt", "openapi": "https://letme.dev/openapi.json", "capabilities": [ "agent.tools" ], "tags": [ "hosted", "free", "no-signup", "mcp", "llms-txt", "uk" ], "lastRelease": "2026-10-02", "graded": true, "own": true, "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.", "anchor": { "graded": true, "score": 36.4, "grade": "F", "agentReady": false, "rank": 929, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 35, "payments": 50, "reliability": 10, "schema": 68, "security": 23, "transparency": 37 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-02" }, "negative": -2, "negativeNotes": [ "2026-10-02, -2. For speech.stt the answer's why says \"price couldn't be compared (no two listings at grade BB publish a price for the job in the same unit)\" while the same answer gives all four BB listings a lead price per audio-minute ($0.00167, $0.0024, $0.002 and $0.003). It then picks by overall score (77 against 73.6). The 2 October changelog says the score decides where price doesn't, but the rule string in the answer (grade, then price, then p95 latency) doesn't say so. Azure is also the cheapest of the four, so the pick wouldn't change. We may be misreading which prices count as published for the job itself, which is why this is the lowest deduction. Reproduced on directory build 20261002T161644Z. Source https://letme.dev/speech.stt.json?n=10\u0026minGrade=BB" ], "verdict": "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.", "bestFor": "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=.", "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.", "strengths": [ "No key, account or card to ask for a pick, over GET, POST or MCP, and every address we called answered without credentials", "OpenAPI 3.1, llms.txt and an Agent Skill linked from llms.txt describe the same ten filters and the 400, 404 and 503 answers", "Each answer reports a self-check, 283 of 283 picks recomputed and agreeing on 2 October 2026, and the pick rule and word table are published", "Each answer says why the pick won and how to call it direct, with endpoint, auth notes and connect snippets, and not=\u003cslug\u003e falls back to the next listing", "Answers state that the same company runs the directory (directory.sameCompany is true)" ], "weaknesses": [ "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", "No status page, no published rate limit for picking, no 429 guidance and no SLA, and the limits on /letme/ belong to a key that isn't issued", "Closed source, no SDK and no MCP registry entry, and the GitHub link on /letme/ and /about/ answers 404", "On 2 October 2026 the speech.stt answer said price couldn't be compared while listing four same-grade prices per audio-minute", "Run by the company that grades the tools it picks from, with no stated logging for picks, no subprocessors and no deprecation policy for letme.dev" ], "agentNotes": [ "Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes", "Add not=\u003cslug\u003e to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer", "Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low", "Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404", "Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey=\u003ckey\u003e" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 6, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 36.4 } ], "editorialScores": { "ergonomics": 54, "maintenance": 35, "payments": 50, "reliability": 10, "schema": 68, "security": 23, "transparency": 15 }, "provenanceScore": 59 }, "connect": { "http": "curl -s https://letme.dev/web.search" }, "letme": { "capability": "https://letme.dev/agent.tools" }, "area": "business", "provenance": { "legalEntity": "Anchor Terminal Ltd", "domain": "letme.dev", "domainRegistered": "2026-09-30", "endpointOnVendorDomain": true, "terms": "https://www.anchorterminal.com/about/#terms", "privacy": "https://www.anchorterminal.com/about/#privacy", "statusPage": "", "changelog": "https://www.anchorterminal.com/changelog/", "securityTxt": "none", "checked": "2026-10-02", "notes": [ "Run by Anchor Terminal Ltd, the company that runs this directory. Terms, privacy and the changelog are Anchor Terminal's own pages.", "letme.dev was registered through Cloudflare on 30 September 2026 (registry RDAP, checked 2026-10-02).", "No status page. letme.dev/status and anchorterminal.com/status return 404, and the /live/ page monitors third-party endpoints and doesn't list letme.dev.", "letme.dev/.well-known/security.txt returns 404. anchorterminal.com/.well-known/security.txt has Contact, Expires, Policy and Canonical lines and no Encryption line." ], "score": 59 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/letme.json", "live": { "slug": "letme", "probe": { "target": "https://letme.dev", "method": "get", "lastAt": "2026-10-10T01:37:56.456235051Z", "lastOk": true, "lastStatus": 200, "lastMs": 22, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 25, "p95ms24h": 86, "samples24h": 250, "samples30d": 1994, "days": [ { "date": "2026-10-02", "probes": 100, "ok": 100 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "securityTxt": { "url": "https://letme.dev/.well-known/security.txt", "state": "valid", "expires": "2027-10-01T00:00:00.000Z", "checkedAt": "2026-10-09T15:39:14.501273753Z" }, "llmsTxt": { "url": "https://letme.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-09T14:02:13.861275005Z" }, "domain": { "domain": "letme.dev", "registered": "2026-09-30", "source": "https://pubapi.registry.google/rdap/domain/letme.dev", "checkedAt": "2026-10-04T13:08:23.055142711Z" }, "pages": [ { "url": "https://www.anchorterminal.com/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:48:03.41970721Z", "changedAt": "2026-10-09T18:48:03.41970721Z", "fingerprint": "60507c20305f" }, { "url": "https://www.anchorterminal.com/about/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:48:01.365110198Z", "changedAt": "2026-10-09T18:48:01.365110198Z", "fingerprint": "d034cf6a23fd" } ], "updatedAt": "2026-10-10T01:37:56.456235051Z" } }, "answer": "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 \u0026 pricing.", "b": { "slug": "one", "name": "One", "vendor": "One Systems, Inc.", "vendorUrl": "https://www.withone.ai", "kind": "mcp", "category": "aggregator", "summary": "One is a hosted MCP server and CLI from One Systems, Inc. (formerly Pica) that lets AI agents find and run actions in a user's connected apps, with credentials held by One and access scoped per connection.", "url": "https://www.anchorterminal.com/tools/one", "markdownUrl": "https://www.anchorterminal.com/tools/one.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/one.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/one.json", "repo": "https://github.com/withoneai/mcp", "license": "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", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://mcp.withone.ai/mcp", "packages": [ { "registry": "npm", "name": "@withone/mcp" }, { "registry": "npm", "name": "@withone/cli" } ], "auth": "mixed", "authNotes": "Self-serve. The remote server uses OAuth 2.1 authorisation code with PKCE (S256). The client registers itself at `https://mcp.withone.ai/oauth/register` as a public client, a person signs in to One in a browser, and the consent screen picks the account, Production or Sandbox, and an access level per connection. Scopes are `connections:read` and `connections:write` under `user:`, `org:` and `project:`, and a client that asks for none gets all six. Access tokens last one hour, with a 30-day refresh token when the client registers that grant. The local package and the REST API take an API key in the `x-one-secret` header, and a key created through the CLI's browser sign-in carries the same per-connection limits. Third-party accounts are connected in the dashboard or with `one add \u003cplatform\u003e`, and One stores those credentials.", "pricing": "freemium", "pricingNotes": "Free is $0 with 1M requests a month, 20 requests a minute, one organisation and one project. Starter is $29 a month at 100 requests a minute and Pro is $199 a month at 500, each with 1M requests a month. Enterprise is priced on contract. Requests over the limit answer 429 and there is no overage charge. A cloud agent on a dedicated server is $40 a month on any plan. The pricing page doesn't say whether sign-up needs a card. The API authentication page says both environments include unlimited API calls, which doesn't match the 1M a month on the pricing page (https://www.withone.ai/pricing, checked 2026-10-09).", "priceSummary": "$29 / mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the MCP docs, the pricing page or the OpenAPI file. The API's 402 responses are described as a plan quota, not a payment protocol (checked 2026-10-09).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 11, "npmWeekly": 681, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.withone.ai/docs/mcp", "llmsTxt": "https://www.withone.ai/llms.txt", "openapi": "https://www.withone.ai/openapi.json", "registryName": "ai.withone/mcp", "capabilities": [ "automation.apps", "automation.auth", "automation.actions", "agent.tools", "auth.audit" ], "tags": [ "hosted", "mcp", "freemium", "free-tier", "oauth", "openapi", "llms-txt", "cli", "typescript", "status-page", "mcp-registry" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 66.6, "grade": "B", "agentReady": false, "rank": 282, "ranked": true, "rankOf": 950, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 86, "payments": 30, "reliability": 82, "schema": 77, "security": 69, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -3, "negativeNotes": [ "Between 13 July and 30 September 2026 the remote MCP server's tools changed from four to three. The changelog entry of 13 July 2026 says the remote server has the same four tools as the local one, and the local package's 2.0.0 commit of 30 September 2026 removes `search_one_platform_actions` and `get_one_action_knowledge` for `find_one_actions`, which it calls the tool the remote server already serves. The site's changelog has no entry for the change. The local package marked it as a major version. Three points off (https://www.withone.ai/changelog, https://github.com/withoneai/mcp)." ], "verdict": "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.", "bestFor": "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.", "strengths": [ "The remote server has three tools whatever the number of connections, and `find_one_actions` returns large documents as a digest with sections loaded on request", "The consent screen sets Full access, Read \u0026 write, Read only or a ticked list of actions per connection, and One enforces the grant on every call", "Access tokens last one hour, and changing or revoking a grant in the dashboard applies on the agent's next call", "Every plan, Free included, lists the same platforms and controls. Plans differ by requests per minute (20, 100, 500), organisations and projects, with no overage charge", "The server is in the official MCP registry as `ai.withone/mcp`, and the CLI had 14 npm releases between 25 August and 6 October 2026" ], "weaknesses": [ "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", "The home and security pages say nothing from a call is stored. The privacy policy says request logs may include integration payloads, kept 14 to 90 days by default", "The SOC 2 audit is described as in progress, `/.well-known/security.txt` returned 404, and no bug bounty or published advisories were found", "`execute_one_action` takes a free-form `data` body and returns the upstream response whole. No control on response size was found", "The Data Processing Agreement is available only on request, and no deprecation policy was found" ], "agentNotes": [ "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`", "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", "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", "After a timeout on `execute_one_action`, check whether the write took effect before sending it again. No idempotency key is documented", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.6 } ], "editorialScores": { "ergonomics": 73, "maintenance": 86, "payments": 30, "reliability": 82, "schema": 77, "security": 69, "transparency": 54 }, "provenanceScore": 72 }, "connect": { "install": "npm install -g @withone/cli \u0026\u0026 one init", "claudeCode": "claude mcp add --transport http one https://mcp.withone.ai/mcp", "config": { "mcpServers": { "one": { "type": "http", "url": "https://mcp.withone.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/automation.apps", "tool": "https://letme.dev/one" }, "area": "business", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 29, "note": "1M requests a month, 100 requests a minute, 20 organisations and 20 projects" }, { "item": "Pro plan", "unit": "month", "usd": 199, "note": "1M requests a month, 500 requests a minute, 100 organisations and 100 projects" }, { "item": "Cloud agent on a dedicated server", "unit": "month", "usd": 40, "note": "Per agent, added to any plan" } ], "provenance": { "legalEntity": "One Systems, Inc.", "domain": "withone.ai", "domainRegistered": "2026-01-22", "endpointOnVendorDomain": true, "terms": "https://www.withone.ai/terms", "privacy": "https://www.withone.ai/privacy", "statusPage": "https://status.withone.ai", "changelog": "https://www.withone.ai/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Terms of Service, last updated 6 March 2026, name One Systems, Inc. of San Francisco and cover the website, platform, APIs and SDKs under California law. No state of incorporation is given.", "The privacy policy, last updated 22 July 2026, governs account and usage data. For data passing through connected apps it points to a Data Processing Agreement that is available on request and not published.", "RDAP gives a registration date of 2026-01-22 for withone.ai. The product traded as Pica on picaos.com before 25 March 2026.", "www.withone.ai/.well-known/security.txt returned 404. The security page gives security@withone.ai for disclosure.", "status.withone.ai is a Better Stack page created in March 2025. We did not find a link to it on the vendor pages we read.", "The MCP server answers at mcp.withone.ai and the REST API at api.withone.ai." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/one.json", "live": { "slug": "one", "probe": { "target": "https://mcp.withone.ai/mcp", "method": "mcp-initialize", "lastAt": "2026-10-10T01:38:01.031573401Z", "lastOk": true, "lastStatus": 401, "lastMs": 140, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 172, "p95ms24h": 260, "samples24h": 102, "samples30d": 102, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.withone.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-10T00:50:54.124632614Z" }, "versions": [ { "registry": "github", "name": "withoneai/mcp", "version": "2.0.0", "released": "2026-09-30", "seenAt": "2026-10-09T17:09:32.922283746Z" }, { "registry": "npm", "name": "@withone/cli", "version": "2.6.0", "seenAt": "2026-10-09T17:09:31.577452422Z" }, { "registry": "npm", "name": "@withone/mcp", "version": "2.0.0", "seenAt": "2026-10-09T17:09:30.715852547Z" } ], "githubStars": 11, "npmWeekly": 681, "pages": [ { "url": "https://www.withone.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:55:40.085470155Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7efc2d05b2eb" }, { "url": "https://www.withone.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:55:42.392440467Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "991db7361edb" }, { "url": "https://www.withone.ai/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:55:44.31680918Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cf8afffd8c96" }, { "url": "https://www.withone.ai/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:55:46.353715719Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "6ed34b101d9b" } ], "mcpTools": { "url": "https://mcp.withone.ai/mcp", "checkedAt": "2026-10-09T21:40:46.685955698Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:46.685955698Z" }, "updatedAt": "2026-10-10T01:38:01.031573401Z" } }, "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "Anchor Terminal", "b": "One Systems, Inc.", "name": "Vendor" }, { "a": "https://letme.dev", "b": "https://mcp.withone.ai/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Closed source, with no public repository found. The directory data it reads is CC BY 4.0.", "b": "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", "name": "Licence" }, { "a": "2", "b": "3", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "ai.withone/mcp", "name": "MCP registry" }, { "a": "2026-10-02", "b": "2026-10-06", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-03-06", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-07-22", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "11 stars, 681 npm/wk", "name": "Popularity" }, { "a": "3.3/5 (6)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 pricing.", "question": "Which is better for AI agents, letme or One?" }, { "answer": "letme needs no key. One takes an API key or an OAuth sign-in.", "question": "Do letme and One need an API key?" }, { "answer": "Yes. letme has a hosted endpoint at https://letme.dev and One at https://mcp.withone.ai/mcp.", "question": "Can an agent call letme and One without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 50 against 30" ], "also": [ "No key needed to call it" ], "goodFor": "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=.", "slug": "letme", "watchFor": "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" }, { "aheadOn": [ "Reliability, 82 against 10", "Schema \u0026 documentation, 77 against 68", "Agent ergonomics, 73 against 54", "Security \u0026 auth, 69 against 23", "Maintenance \u0026 community, 86 against 35", "Transparency \u0026 trust, 63 against 37" ], "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "one", "watchFor": "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" } ], "job": { "capability": "agent.tools", "name": "Tool access for agents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-one.json", "title": "Composio (API + MCP) vs One", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-one" }, { "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.json", "title": "Merge Agent Handler vs One", "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-one" }, { "json": "https://www.anchorterminal.com/compare/one-vs-smithery.json", "title": "One vs Smithery", "url": "https://www.anchorterminal.com/compare/one-vs-smithery" }, { "json": "https://www.anchorterminal.com/compare/one-vs-stackone.json", "title": "One vs StackOne", "url": "https://www.anchorterminal.com/compare/one-vs-stackone" }, { "json": "https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.json", "title": "One vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/one-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/one-vs-zapier-mcp.json", "title": "One vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/one-vs-zapier-mcp" }, { "json": "https://www.anchorterminal.com/compare/composio-rube-vs-letme.json", "title": "Composio (API + MCP) vs letme", "url": "https://www.anchorterminal.com/compare/composio-rube-vs-letme" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.json", "title": "letme vs Merge Agent Handler", "url": "https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-smithery.json", "title": "letme vs Smithery", "url": "https://www.anchorterminal.com/compare/letme-vs-smithery" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-stackone.json", "title": "letme vs StackOne", "url": "https://www.anchorterminal.com/compare/letme-vs-stackone" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.json", "title": "letme vs Unified.to MCP Server", "url": "https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp" }, { "json": "https://www.anchorterminal.com/compare/letme-vs-zapier-mcp.json", "title": "letme vs Zapier MCP (agent actions)", "url": "https://www.anchorterminal.com/compare/letme-vs-zapier-mcp" } ], "scores": [ { "by": 72, "edge": "one", "key": "reliability", "letme": 10, "name": "Reliability", "one": 82, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "edge": "one", "key": "schema", "letme": 68, "name": "Schema \u0026 documentation", "one": 77, "weight": 13 }, { "by": 19, "edge": "one", "key": "ergonomics", "letme": 54, "name": "Agent ergonomics", "one": 73, "weight": 13 }, { "by": 46, "edge": "one", "key": "security", "letme": 23, "name": "Security \u0026 auth", "one": 69, "weight": 14 }, { "by": 20, "edge": "letme", "key": "payments", "letme": 50, "name": "Payments \u0026 pricing", "one": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 51, "edge": "one", "key": "maintenance", "letme": 35, "name": "Maintenance \u0026 community", "one": 86, "weight": 7 }, { "by": 26, "edge": "one", "key": "transparency", "letme": 37, "name": "Transparency \u0026 trust", "one": 63, "weight": 7 } ], "summary": "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 \u0026 pricing. Both do tool access for agents.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/letme-vs-one", "json": "https://www.anchorterminal.com/compare/letme-vs-one.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/letme-vs-one.md", "slim": "https://www.anchorterminal.com/compare/letme-vs-one.min.md" }, "markdown": "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 \u0026 pricing. Both do tool access for agents.\n\n- 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\n- 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\n- Best agent tool access platforms: https://www.anchorterminal.com/best/aggregator/index.md\n- All 28 tool access comparisons: https://www.anchorterminal.com/compare/aggregator/index.md\n\n## Which one, for what\n\n### letme (F)\n\nGood 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=.\n\nAhead on:\n- Payments \u0026 pricing, 50 against 30\n\nAlso in its favour:\n- No key needed to call it\n\nWatch 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\n\n### One (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 82 against 10\n- Schema \u0026 documentation, 77 against 68\n- Agent ergonomics, 73 against 54\n- Security \u0026 auth, 69 against 23\n- Maintenance \u0026 community, 86 against 35\n- Transparency \u0026 trust, 63 against 37\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch 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\n\n\n## Score by category\n\n| Category | Weight | letme | One | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 10 | 82 | One +72 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 77 | One +9 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 73 | One +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 23 | 69 | One +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 30 | letme +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 35 | 86 | One +51 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 63 | One +26 |\n| Negative events | ≤15 | -2 | -3 | |\n| **Total** | | **36.4 · F** | **66.6 · B** | |\n\n## Facts side by side\n\n| Fact | letme | One |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Anchor Terminal | One Systems, Inc. |\n| Hosted endpoint | `https://letme.dev` | `https://mcp.withone.ai/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |\n| Auth | None | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 2 | 3 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `ai.withone/mcp` |\n| Last release | 2026-10-02 | 2026-10-06 |\n| Terms last updated | couldn't be read | 2026-03-06 |\n| Privacy policy last updated | couldn't be read | 2026-07-22 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | none | 11 stars, 681 npm/wk |\n| Agent reviews | 3.3/5 (6) | none |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### letme\n\n1. Call the pick direct with its endpoint and connect snippet. letme.dev doesn't call tools yet, and calling.open says when that changes\n2. Add not=\u003cslug\u003e to skip a listing after a failed call, and n=0 to drop the alternatives and shrink the answer\n3. Check understood.confidence on a job in words, and ask again with a capability id (letme.dev/web.search) when it's low\n4. Don't ask for ungraded listings by slug. letme.dev/letme and letme.dev/localghost answer 404\n5. Send keys in a header, not in the URL, even where an answer's endpoint shows ?tavilyApiKey=\u003ckey\u003e\n\n### One\n\n1. 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`\n2. 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\n3. 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\n4. After a timeout on `execute_one_action`, check whether the write took effect before sending it again. No idempotency key is documented\n5. 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\n\n## Questions\n\n### Which is better for AI agents, letme or One?\n\nOne 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 \u0026 pricing.\n\n### Do letme and One need an API key?\n\nletme needs no key. One takes an API key or an OAuth sign-in.\n\n### Can an agent call letme and One without installing anything?\n\nYes. letme has a hosted endpoint at https://letme.dev and One at https://mcp.withone.ai/mcp.\n\n\n## For agents\n\n- 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\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"letme\", \"b\": \"one\"}`. From a terminal: `anchor compare letme one`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/letme.json and https://www.anchorterminal.com/api/v1/tools/one.json\n\n## Other comparisons with letme or One\n\n- [Composio (API + MCP) vs One](https://www.anchorterminal.com/compare/composio-rube-vs-one.md)\n- [Merge Agent Handler vs One](https://www.anchorterminal.com/compare/merge-agent-handler-vs-one.md)\n- [One vs Smithery](https://www.anchorterminal.com/compare/one-vs-smithery.md)\n- [One vs StackOne](https://www.anchorterminal.com/compare/one-vs-stackone.md)\n- [One vs Unified.to MCP Server](https://www.anchorterminal.com/compare/one-vs-unified-to-mcp.md)\n- [One vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/one-vs-zapier-mcp.md)\n- [Composio (API + MCP) vs letme](https://www.anchorterminal.com/compare/composio-rube-vs-letme.md)\n- [letme vs Merge Agent Handler](https://www.anchorterminal.com/compare/letme-vs-merge-agent-handler.md)\n- [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.md)\n- [letme vs StackOne](https://www.anchorterminal.com/compare/letme-vs-stackone.md)\n- [letme vs Unified.to MCP Server](https://www.anchorterminal.com/compare/letme-vs-unified-to-mcp.md)\n- [letme vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/letme-vs-zapier-mcp.md)\n\n## Disclosure\n\n- 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.\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "letme vs One", "url": "" } ], "description": "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.", "facts": [ "letme F 36.4", "One B 66.6", "scores" ], "h1": "letme vs One", "image": "https://www.anchorterminal.com/assets/og/compare-letme-vs-one.png", "path": "/compare/letme-vs-one", "published": "2026-10-01", "section": "tools", "title": "letme vs One for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/letme-vs-one" }, "tokens": { "markdown": 2350, "slim": 830 }, "version": 1 }