{
  "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-10T02:07:14.071620897Z",
          "lastOk": true,
          "lastStatus": 200,
          "lastMs": 20,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 25,
          "p95ms24h": 86,
          "samples24h": 250,
          "samples30d": 1999,
          "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": 22,
              "ok": 22
            }
          ]
        },
        "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-10T02:07:14.071620897Z"
      }
    },
    "answer": "StackOne scores 69.1 (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": "stackone",
      "name": "StackOne",
      "vendor": "StackOne Technologies Limited",
      "vendorUrl": "https://www.stackone.com",
      "kind": "mcp",
      "category": "aggregator",
      "summary": "StackOne is a hosted gateway from StackOne Technologies Limited that gives AI agents actions across more than 540 business apps over MCP, SDKs, A2A or HTTP, with managed authentication, per-user grants, policies and logs.",
      "url": "https://www.anchorterminal.com/tools/stackone",
      "markdownUrl": "https://www.anchorterminal.com/tools/stackone.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/stackone.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/stackone.json",
      "repo": "https://github.com/StackOneHQ/stackone-ai-node",
      "license": "Proprietary service under StackOne's SaaS Terms and Conditions. The Agent SDKs (`@stackone/ai`, `stackone-ai`) and the Defender package (`@stackone/defender`) are Apache-2.0",
      "transports": [
        "streamable-http",
        "http"
      ],
      "remoteUrl": "https://mcp.stackone.com/mcp",
      "packages": [
        {
          "registry": "npm",
          "name": "@stackone/ai"
        },
        {
          "registry": "pypi",
          "name": "stackone-ai"
        },
        {
          "registry": "npm",
          "name": "@stackone/defender"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve. A person signs up in the dashboard, creates a project and a connector profile, and links an account. MCP clients connect to `https://mcp.stackone.com/mcp` with OAuth (scopes `mcp offline_access`, one-hour access tokens, a 90-day grant) and the user picks the linked accounts and actions at consent. Most clients register themselves, and a few need a client ID and secret created in the dashboard. Backend calls go to `https://api.stackone.com/mcp` or `POST /actions/rpc` with a project API key as the Basic auth username and the linked account in `x-account-id`. Keys take scopes (Platform API, Actions, Connectors, Credentials, Unified API) and can be disabled or deleted. Session token URLs (`https://api.stackone.com/mcp?token=...`) cover one linked account, carry the access in the URL and expire after one year by default.",
      "pricing": "freemium",
      "pricingNotes": "Free to start with no card, per the pricing page. Gateway Starter is free with 1,000 credits a seat a month, one credit per tool call or API call, and extra credits at $60 per 20,000. Gateway Team is $600 a month ($6,000 a year) with 5,000 credits a seat a month and extra credits at $20 per 20,000. The pricing calculator's markup gives 10 seats included on Team and $15 a further seat, which the page text doesn't state. OEM Core is free with a monthly credit allowance and volume prices on request. Enterprise plans are priced on contract. Browser use, premium defence and data sync cost more than one credit, at rates not published. The Service Consumption Schedule of 30 March 2026 gives $0.003 per Action Call as overage and counts unsuccessful requests, while the pricing page says background and failed calls aren't billed (https://www.stackone.com/pricing/, checked 2026-10-09).",
      "priceSummary": "$600 / mo",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the pricing page, the SaaS terms or the Service Consumption Schedule (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 30,
        "npmWeekly": 277,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.stackone.com/introduction",
      "llmsTxt": "https://docs.stackone.com/llms.txt",
      "openapi": "https://api.eu1.stackone.com/v2/oas/stackone.json",
      "registryName": "com.stackone/mcp",
      "capabilities": [
        "automation.apps",
        "automation.auth",
        "automation.actions",
        "agent.tools",
        "auth.audit"
      ],
      "tags": [
        "hosted",
        "mcp",
        "a2a",
        "freemium",
        "free-tier",
        "no-card",
        "oauth",
        "api-key",
        "openapi",
        "llms-txt",
        "typescript",
        "python",
        "enterprise",
        "status-page",
        "soc2",
        "mcp-registry",
        "closed-source"
      ],
      "lastRelease": "2026-09-24",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 69.1,
        "grade": "B",
        "agentReady": false,
        "rank": 198,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 3,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 84,
          "payments": 38,
          "reliability": 80,
          "schema": 78,
          "security": 69,
          "transparency": 69
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -2,
        "negativeNotes": [
          "27 April 2026. `@stackone/ai` v2.8.1 fixed a flaw in which tools fetched concurrently for several accounts were stamped with the wrong `x-account-id`, so a call could run against another linked account. It is recorded as a bug fix in the changelog, with no advisory found. Fixed and documented, so 2 points (https://github.com/StackOneHQ/stackone-ai-node/blob/main/CHANGELOG.md)."
        ],
        "verdict": "StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed.",
        "bestFor": "A company that wants one governed MCP endpoint for staff agents across business systems, and product teams embedding per-customer connections with HR, recruiting and CRM coverage.",
        "strengths": [
          "The MCP server at `https://mcp.stackone.com/mcp` uses OAuth per person. Access tokens last one hour, a grant lasts 90 days, and each user can revoke it under Connected Apps",
          "Advanced Tool Search replaces the tool list with two tools, search and execute, and is on by default at the OAuth consent screen",
          "Since 24 July 2026 every tool carries `readOnlyHint`, `destructiveHint` and `openWorldHint`, derived from an effects value on each action",
          "API keys are limited to one project and take scopes for the Platform API, Actions, Connectors, Credentials and the Unified API. Credentials access is off by default",
          "Rate limit published at 1,000 requests a minute per API key, with `Retry-After` in seconds on 429 and 408 responses",
          "Defender scans tool results for prompt injection and is on for new projects. Its Light Scan engine is open source under Apache-2.0"
        ],
        "weaknesses": [
          "Session token URLs (`https://api.stackone.com/mcp?token=...`) put the credential in the query string, cover one linked account and expire after one year by default",
          "The Service Consumption Schedule counts every request, successful or not, as an Action Call. The pricing page says failed calls aren't billed",
          "Defender's default mode is Monitor, which records a verdict and passes the tool result to the agent unchanged",
          "Policies apply only to signed-in members. A call made with a project API key is memberless and is governed by connector profile scoping alone",
          "The Logs API, audit logs, SIEM export and an uptime SLA are Enterprise only on Gateway plans, and Starter keeps action logs for one day",
          "The Acceptable Use Policy bars competitive analysis or benchmarking other than for internal comparison, and probing or testing the Service's vulnerability without authorisation. This matters before any probe is run",
          "`@stackone/ai` stamped tools with the wrong `x-account-id` when accounts were fetched concurrently, until v2.8.1 on 27 April 2026. No advisory was found"
        ],
        "agentNotes": [
          "Send `Accept: application/json,text/event-stream` on every MCP request to `https://api.stackone.com/mcp`, by POST only. Without it the server answers 406",
          "In `search_execute` mode call `{provider}_search_actions` first and pass the returned `action_id` to `{provider}_execute_action`. Never hardcode action ids",
          "Pass the API key as the Basic auth username with an empty password, and name the linked account in `x-account-id`",
          "On 429 or 408 wait the seconds given in `Retry-After`. StackOne has already retried a provider's 429 up to five times within a 60-second request lifetime",
          "On 412 read `errorCode` and `details.statusReasons`. `AccountErrorStatus` needs a person to re-authenticate the linked account"
        ],
        "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": 69.1
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 84,
          "payments": 38,
          "reliability": 80,
          "schema": 78,
          "security": 69,
          "transparency": 50
        },
        "provenanceScore": 88
      },
      "connect": {
        "install": "npm install @stackone/ai",
        "http": "curl -X POST \"https://api.stackone.com/actions/rpc\" \\\n  -u \"$STACKONE_API_KEY:\" \\\n  -H \"x-account-id: your-account-id\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"action\": \"bamboohr_list_employees\", \"query\": {\"page_size\": 25}}'",
        "claudeCode": "claude mcp add --transport http --scope user stackone https://mcp.stackone.com/mcp"
      },
      "letme": {
        "capability": "https://letme.dev/automation.apps",
        "tool": "https://letme.dev/stackone"
      },
      "area": "business",
      "unitPrices": [
        {
          "item": "Gateway Team plan",
          "unit": "month",
          "usd": 600,
          "note": "5,000 credits a seat a month, one credit per tool call or API call. $6,000 billed yearly"
        },
        {
          "item": "Extra credits, Gateway Starter",
          "unit": "1k-calls",
          "usd": 3,
          "note": "$60 per 20,000 credits, valid 12 months. Advanced capabilities cost more than one credit a call"
        },
        {
          "item": "Extra credits, Gateway Team",
          "unit": "1k-calls",
          "usd": 1,
          "note": "$20 per 20,000 credits, valid 12 months"
        }
      ],
      "provenance": {
        "legalEntity": "StackOne Technologies Limited",
        "domain": "stackone.com",
        "domainRegistered": "2013-06-25",
        "endpointOnVendorDomain": true,
        "terms": "https://www.stackone.com/terms/saas-terms/",
        "privacy": "https://www.stackone.com/terms/privacy-policy/",
        "statusPage": "https://status.stackone.com",
        "changelog": "https://www.stackone.com/changelog/",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The SaaS Terms and Conditions, effective 30 March 2026, name StackOne Technologies Limited, company number 14684360, registered at 2 Communications Road, Newbury, Berkshire, RG19 6AB, under the laws of England and Wales. They take effect when a customer first accesses the Service or signs an order.",
          "The contact page says StackOne operates in the United States as StackOne Technologies Inc., 2261 Market Street, San Francisco.",
          "The Platform Privacy Policy, last updated 1 December 2023, covers the web application and API and says it does not cover the website. A separate Privacy Notice covers the website.",
          "The MCP server answers at mcp.stackone.com, the API at api.stackone.com and A2A at a2a.stackone.com.",
          "www.stackone.com/.well-known/security.txt returned 404.",
          "RDAP for stackone.com gives a registration date of 2013-06-25. The company was incorporated later, per its company number.",
          "status.stackone.com runs on incident.io and lists the Web Dashboard, the API (US, EU and UK) and the Connectors Hub.",
          "trust.stackone.com, which the terms cite for the security policy and the sub-processor list, answered our reader with a bot check and was not read."
        ],
        "score": 88
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/stackone.json",
      "live": {
        "slug": "stackone",
        "probe": {
          "target": "https://mcp.stackone.com/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-10-10T02:07:26.369561075Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 377,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 112,
          "p95ms24h": 295,
          "samples24h": 107,
          "samples30d": 107,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 22,
              "ok": 22
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.stackone.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-10T02:06:29.204045169Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "StackOneHQ/stackone-ai-node",
            "version": "v2.10.0",
            "released": "2026-07-27",
            "seenAt": "2026-10-09T17:21:48.091098138Z"
          },
          {
            "registry": "npm",
            "name": "@stackone/ai",
            "version": "2.10.0",
            "seenAt": "2026-10-09T17:21:45.859326927Z"
          },
          {
            "registry": "npm",
            "name": "@stackone/defender",
            "version": "0.8.3",
            "seenAt": "2026-10-09T17:21:46.919917579Z"
          },
          {
            "registry": "pypi",
            "name": "stackone-ai",
            "version": "2.10.1",
            "released": "2026-07-28",
            "seenAt": "2026-10-09T17:21:46.731430671Z"
          }
        ],
        "githubStars": 30,
        "npmWeekly": 277,
        "pypiWeekly": 120,
        "pages": [
          {
            "url": "https://www.stackone.com/changelog/",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:33.415845489Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "a8dc254bb424"
          },
          {
            "url": "https://www.stackone.com/pricing/",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:35.567295878Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "98687cfb089f"
          },
          {
            "url": "https://www.stackone.com/terms/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:37.551620202Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "011ecd948b67"
          },
          {
            "url": "https://www.stackone.com/terms/saas-terms/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:54:39.532884111Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "393a890498df"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.stackone.com/mcp",
          "checkedAt": "2026-10-09T21:40:55.809059913Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-09T21:40:55.809059913Z"
        },
        "updatedAt": "2026-10-10T02:07:26.369561075Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Anchor Terminal",
        "b": "StackOne Technologies Limited",
        "name": "Vendor"
      },
      {
        "a": "https://letme.dev",
        "b": "https://mcp.stackone.com/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "Streamable HTTP, HTTP",
        "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 service under StackOne's SaaS Terms and Conditions. The Agent SDKs (`@stackone/ai`, `stackone-ai`) and the Defender package (`@stackone/defender`) are Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "2",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "com.stackone/mcp",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-02",
        "b": "2026-09-24",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "2026-03-30",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2023-12-01",
        "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": "not found in the text",
        "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": "30 stars, 277 npm/wk",
        "name": "Popularity"
      },
      {
        "a": "3.3/5 (6)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "StackOne scores 69.1 (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 StackOne?"
      },
      {
        "answer": "letme needs no key. StackOne takes an API key or an OAuth sign-in.",
        "question": "Do letme and StackOne need an API key?"
      },
      {
        "answer": "Yes. letme has a hosted endpoint at https://letme.dev and StackOne at https://mcp.stackone.com/mcp.",
        "question": "Can an agent call letme and StackOne without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Payments \u0026 pricing, 50 against 38"
        ],
        "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, 80 against 10",
          "Schema \u0026 documentation, 78 against 68",
          "Agent ergonomics, 75 against 54",
          "Security \u0026 auth, 69 against 23",
          "Maintenance \u0026 community, 84 against 35",
          "Transparency \u0026 trust, 69 against 37"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "A company that wants one governed MCP endpoint for staff agents across business systems, and product teams embedding per-customer connections with HR, recruiting and CRM coverage.",
        "slug": "stackone",
        "watchFor": "Session token URLs (`https://api.stackone.com/mcp?token=...`) put the credential in the query string, cover one linked account and expire after one year by default"
      }
    ],
    "job": {
      "capability": "agent.tools",
      "name": "Tool access for agents"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/composio-rube-vs-stackone.json",
        "title": "Composio (API + MCP) vs StackOne",
        "url": "https://www.anchorterminal.com/compare/composio-rube-vs-stackone"
      },
      {
        "json": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.json",
        "title": "Merge Agent Handler vs StackOne",
        "url": "https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone"
      },
      {
        "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/smithery-vs-stackone.json",
        "title": "Smithery vs StackOne",
        "url": "https://www.anchorterminal.com/compare/smithery-vs-stackone"
      },
      {
        "json": "https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.json",
        "title": "StackOne vs Unified.to MCP Server",
        "url": "https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/stackone-vs-zapier-mcp.json",
        "title": "StackOne vs Zapier MCP (agent actions)",
        "url": "https://www.anchorterminal.com/compare/stackone-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-one.json",
        "title": "letme vs One",
        "url": "https://www.anchorterminal.com/compare/letme-vs-one"
      },
      {
        "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-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": 70,
        "edge": "stackone",
        "key": "reliability",
        "letme": 10,
        "name": "Reliability",
        "stackone": 80,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 10,
        "edge": "stackone",
        "key": "schema",
        "letme": 68,
        "name": "Schema \u0026 documentation",
        "stackone": 78,
        "weight": 13
      },
      {
        "by": 21,
        "edge": "stackone",
        "key": "ergonomics",
        "letme": 54,
        "name": "Agent ergonomics",
        "stackone": 75,
        "weight": 13
      },
      {
        "by": 46,
        "edge": "stackone",
        "key": "security",
        "letme": 23,
        "name": "Security \u0026 auth",
        "stackone": 69,
        "weight": 14
      },
      {
        "by": 12,
        "edge": "letme",
        "key": "payments",
        "letme": 50,
        "name": "Payments \u0026 pricing",
        "stackone": 38,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 49,
        "edge": "stackone",
        "key": "maintenance",
        "letme": 35,
        "name": "Maintenance \u0026 community",
        "stackone": 84,
        "weight": 7
      },
      {
        "by": 32,
        "edge": "stackone",
        "key": "transparency",
        "letme": 37,
        "name": "Transparency \u0026 trust",
        "stackone": 69,
        "weight": 7
      }
    ],
    "summary": "StackOne scores 69.1 (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.",
      "stackone": "StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/letme-vs-stackone",
    "json": "https://www.anchorterminal.com/compare/letme-vs-stackone.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/letme-vs-stackone.md",
    "slim": "https://www.anchorterminal.com/compare/letme-vs-stackone.min.md"
  },
  "markdown": "StackOne scores 69.1 (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- StackOne: grade B, 69.1/100, rank #198 of 950. Markdown https://www.anchorterminal.com/tools/stackone.md · JSON https://www.anchorterminal.com/api/v1/tools/stackone.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 38\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### StackOne (B)\n\nGood for: A company that wants one governed MCP endpoint for staff agents across business systems, and product teams embedding per-customer connections with HR, recruiting and CRM coverage.\n\nAhead on:\n- Reliability, 80 against 10\n- Schema \u0026 documentation, 78 against 68\n- Agent ergonomics, 75 against 54\n- Security \u0026 auth, 69 against 23\n- Maintenance \u0026 community, 84 against 35\n- Transparency \u0026 trust, 69 against 37\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Session token URLs (`https://api.stackone.com/mcp?token=...`) put the credential in the query string, cover one linked account and expire after one year by default\n\n\n## Score by category\n\n| Category | Weight | letme | StackOne | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 10 | 80 | StackOne +70 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 78 | StackOne +10 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 75 | StackOne +21 |\n| Security \u0026 auth | 14% (17.5 this run) | 23 | 69 | StackOne +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 50 | 38 | letme +12 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 35 | 84 | StackOne +49 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 69 | StackOne +32 |\n| Negative events | ≤15 | -2 | -2 | |\n| **Total** | | **36.4 · F** | **69.1 · B** | |\n\n## Facts side by side\n\n| Fact | letme | StackOne |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Anchor Terminal | StackOne Technologies Limited |\n| Hosted endpoint | `https://letme.dev` | `https://mcp.stackone.com/mcp` |\n| Transports | HTTP, Streamable HTTP | Streamable HTTP, HTTP |\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 service under StackOne's SaaS Terms and Conditions. The Agent SDKs (`@stackone/ai`, `stackone-ai`) and the Defender package (`@stackone/defender`) are Apache-2.0 |\n| Tools exposed | 2 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.stackone/mcp` |\n| Last release | 2026-10-02 | 2026-09-24 |\n| Terms last updated | couldn't be read | 2026-03-30 |\n| Privacy policy last updated | couldn't be read | 2023-12-01 |\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 | not found in the text |\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 | 30 stars, 277 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**StackOne.** StackOne's MCP server signs each person in with OAuth, lets them grant individual accounts and actions, and by default exposes two search and execute tools in place of the full catalogue. Session token URLs carry the credential in the query string for a year by default, and the Consumption Schedule and pricing page disagree on whether failed calls are billed.\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### StackOne\n\n1. Send `Accept: application/json,text/event-stream` on every MCP request to `https://api.stackone.com/mcp`, by POST only. Without it the server answers 406\n2. In `search_execute` mode call `{provider}_search_actions` first and pass the returned `action_id` to `{provider}_execute_action`. Never hardcode action ids\n3. Pass the API key as the Basic auth username with an empty password, and name the linked account in `x-account-id`\n4. On 429 or 408 wait the seconds given in `Retry-After`. StackOne has already retried a provider's 429 up to five times within a 60-second request lifetime\n5. On 412 read `errorCode` and `details.statusReasons`. `AccountErrorStatus` needs a person to re-authenticate the linked account\n\n## Questions\n\n### Which is better for AI agents, letme or StackOne?\n\nStackOne scores 69.1 (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 StackOne need an API key?\n\nletme needs no key. StackOne takes an API key or an OAuth sign-in.\n\n### Can an agent call letme and StackOne without installing anything?\n\nYes. letme has a hosted endpoint at https://letme.dev and StackOne at https://mcp.stackone.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/letme-vs-stackone.json, and with the fewest tokens: https://www.anchorterminal.com/compare/letme-vs-stackone.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"letme\", \"b\": \"stackone\"}`. From a terminal: `anchor compare letme stackone`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/letme.json and https://www.anchorterminal.com/api/v1/tools/stackone.json\n\n## Other comparisons with letme or StackOne\n\n- [Composio (API + MCP) vs StackOne](https://www.anchorterminal.com/compare/composio-rube-vs-stackone.md)\n- [Merge Agent Handler vs StackOne](https://www.anchorterminal.com/compare/merge-agent-handler-vs-stackone.md)\n- [One vs StackOne](https://www.anchorterminal.com/compare/one-vs-stackone.md)\n- [Smithery vs StackOne](https://www.anchorterminal.com/compare/smithery-vs-stackone.md)\n- [StackOne vs Unified.to MCP Server](https://www.anchorterminal.com/compare/stackone-vs-unified-to-mcp.md)\n- [StackOne vs Zapier MCP (agent actions)](https://www.anchorterminal.com/compare/stackone-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 One](https://www.anchorterminal.com/compare/letme-vs-one.md)\n- [letme vs Smithery](https://www.anchorterminal.com/compare/letme-vs-smithery.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 StackOne",
        "url": ""
      }
    ],
    "description": "StackOne scores 69.1 (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",
      "StackOne B 69.1",
      "scores"
    ],
    "h1": "letme vs StackOne",
    "image": "https://www.anchorterminal.com/assets/og/compare-letme-vs-stackone.png",
    "path": "/compare/letme-vs-stackone",
    "published": "2026-10-01",
    "section": "tools",
    "title": "letme vs StackOne for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/letme-vs-stackone"
  },
  "tokens": {
    "markdown": 2400,
    "slim": 830
  },
  "version": 1
}