{
  "data": {
    "a": {
      "slug": "clay",
      "name": "Clay",
      "vendor": "Clay Labs Inc.",
      "vendorUrl": "https://www.clay.com",
      "company": "clay.com",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Clay is a go-to-market data and automation platform that searches its own database of companies and people and runs enrichment across 150+ data providers. Agents use it through the Public API v0, the clay CLI and a coding-agent plugin.",
      "url": "https://www.anchorterminal.com/tools/clay",
      "markdownUrl": "https://www.anchorterminal.com/tools/clay.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clay.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clay.json",
      "dns": "clay.grade.anchorterminal.com",
      "repo": "https://github.com/clay-run/agent-plugins",
      "license": "Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file",
      "transports": [
        "http"
      ],
      "remoteUrl": "https://api.clay.com/public/v0",
      "packages": [],
      "auth": "mixed",
      "authNotes": "The Public API takes a personal API key in the clay-api-key header, tied to a Clay user and their workspace access, created in the app, with the CLI (clay api-keys create) or by an agent through the plugin. The CLI signs in with OAuth in a browser or with a device code (clay login --device), one workspace per sign-in. Custom functions need API or MCP access switched on per function (https://developers.clay.com/public-api/authentication).",
      "pricing": "freemium",
      "pricingNotes": "Free plan with 100 data credits and 500 actions a month. Launch from $167 a month and Growth from $446 a month on the plan cards, while the FAQ on the same page says $185 and $495. Data credits start at $0.05 and actions at under a cent. Failed enrichments aren't charged. The FAQ lists Clay API access under Enterprise, while the developer docs give search limits for Free, Trial and paid plans (https://www.clay.com/pricing, https://developers.clay.com/searches, checked 2026-11-04).",
      "priceSummary": "$0.05 / credit",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI spec or the pricing page (checked 2026-10-14).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-14"
      },
      "docsUrl": "https://developers.clay.com",
      "llmsTxt": "https://developers.clay.com/llms.txt",
      "openapi": "https://developers.clay.com/openapi.json",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "data.company"
      ],
      "tags": [
        "hosted",
        "freemium",
        "api-key",
        "openapi",
        "llms-txt",
        "cli",
        "closed-source",
        "lead-search",
        "enrichment",
        "soc2",
        "webhooks"
      ],
      "lastRelease": "2026-11-04",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 58.3,
        "grade": "C",
        "agentReady": false,
        "rank": 857,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 12,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 75,
          "payments": 45,
          "reliability": 40,
          "schema": 84,
          "security": 48,
          "transparency": 61
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-04"
        },
        "negative": 0,
        "verdict": "A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI and plugin released 36 times since 7 August, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, the new terms set no uptime target, and the privacy policy dates from 2020.",
        "bestFor": "Agents building prospect lists and enriching contacts or accounts through many providers at once.",
        "strengths": [
          "Public OpenAPI spec, llms.txt and Markdown copies of the docs",
          "Search and enrichment across Clay's database and 150+ providers through one API",
          "Failed enrichments use no credits or actions",
          "CLI and plugin with JSON output and typed exit codes, released 36 times between 7 August and 4 November 2026",
          "Valid security.txt to July 2027 and SOC 2 Type II listed"
        ],
        "weaknesses": [
          "API keys carry no scopes and act with the user's workspace access",
          "The Claude Code plugin auto-approves most clay CLI commands, including ones that spend credits",
          "No request-rate number published, and error bodies have no stable codes",
          "The 1 November 2026 terms dropped the 99.0 per cent uptime target, and no SLA was found",
          "Privacy policy dated September 2020 with no retention periods, and pricing gives two prices each for Launch and Growth"
        ],
        "agentNotes": [
          "Fetch GET /search/query-mode/reference before writing a search query",
          "Poll routine results until a terminal 200, since 202 means still running",
          "Expect HTTP 402 when a plan's search cap is hit, and tell the user the reset date",
          "Check GET /credits/balance before large batch runs",
          "When a CLI command answers approval_required, tell the user what it would do and let them approve or deny it",
          "Ask the user before enabling the plugin's auto-approve hook in a shared workspace"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 58.3
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 75,
          "payments": 45,
          "reliability": 40,
          "schema": 84,
          "security": 48,
          "transparency": 28
        },
        "provenanceScore": 94,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-04",
            "maintenance": "2026-11-04",
            "payments": "2026-11-04",
            "reliability": "2026-11-04",
            "schema": "2026-11-04",
            "security": "2026-11-04",
            "transparency": "2026-11-04"
          },
          "last": "2026-11-04",
          "lastMoved": "2026-11-13",
          "oldest": "2026-11-04",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl https://api.clay.com/public/v0/me \\\n  -H \"clay-api-key: $CLAY_PUBLIC_API_KEY\"",
        "claudeCode": "Set up the Clay plugin by following the steps in https://github.com/clay-run/agent-plugins"
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/clay"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Data credit",
          "unit": "credit",
          "usd": 0.05,
          "note": "Starting price per the pricing FAQ. Used when buying data from Clay's providers. Cheaper at volume"
        },
        {
          "item": "Launch plan",
          "unit": "month",
          "usd": 167,
          "note": "Plan card headline. The FAQ says from $185 a month"
        }
      ],
      "provenance": {
        "legalEntity": "Clay Labs Inc.",
        "domain": "clay.com",
        "domainRegistered": "1992-11-13",
        "endpointOnVendorDomain": true,
        "terms": "https://www.clay.com/legal/terms-of-service",
        "privacy": "https://www.clay.com/privacy",
        "statusPage": "https://status.clay.com",
        "changelog": "https://www.clay.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-11-04",
        "notes": [
          "The Clay Services Agreement (last updated 1 November 2026) names Clay Labs, Inc. with New York law; the May 2024 version is archived at /legal/terms-of-service-may-23-2024. The privacy policy is dated 11 September 2020.",
          "clay.com/.well-known/security.txt (served at www.clay.com) names security@clay.com and trust.clay.com, expiring 2027-07-31.",
          "status.clay.com answered robots.txt with a Cloudflare bot check on 4 November, so its components and history weren't read.",
          "The API answers at api.clay.com and the docs at developers.clay.com.",
          "RDAP gives clay.com a registration date of 1992-11-13."
        ],
        "score": 94
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/clay.json",
      "live": {
        "slug": "clay",
        "probe": {
          "target": "https://api.clay.com/public/v0",
          "method": "get",
          "lastAt": "2026-11-18T21:50:39.866047462Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 301,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 119,
          "p95ms24h": 273,
          "samples24h": 242,
          "samples30d": 7829,
          "days": [
            {
              "date": "2026-10-18",
              "probes": 256,
              "ok": 256
            },
            {
              "date": "2026-10-19",
              "probes": 255,
              "ok": 255
            },
            {
              "date": "2026-10-20",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-21",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-22",
              "probes": 253,
              "ok": 253
            },
            {
              "date": "2026-10-23",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-24",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-25",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-10-26",
              "probes": 252,
              "ok": 252
            },
            {
              "date": "2026-10-27",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-28",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-10-29",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-10-30",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-31",
              "probes": 251,
              "ok": 251
            },
            {
              "date": "2026-11-01",
              "probes": 249,
              "ok": 249
            },
            {
              "date": "2026-11-02",
              "probes": 250,
              "ok": 250
            },
            {
              "date": "2026-11-03",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-11-04",
              "probes": 246,
              "ok": 246
            },
            {
              "date": "2026-11-05",
              "probes": 185,
              "ok": 185
            },
            {
              "date": "2026-11-06",
              "probes": 241,
              "ok": 241
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 220,
              "ok": 220
            }
          ],
          "since": "2026-10-14T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.clay.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T21:50:40.07384422Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "clay-run/agent-plugins",
            "version": "clay-cli-v1.21.0",
            "released": "2026-11-18",
            "seenAt": "2026-11-18T17:36:33.189836062Z"
          }
        ],
        "githubStars": 152,
        "securityTxt": {
          "url": "https://clay.com/.well-known/security.txt",
          "state": "valid",
          "expires": "2027-07-31T00:00:00.000Z",
          "checkedAt": "2026-11-18T16:31:41.275747623Z"
        },
        "llmsTxt": {
          "url": "https://developers.clay.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:13:39.348979244Z"
        },
        "domain": {
          "domain": "clay.com",
          "registered": "1992-11-13",
          "source": "https://rdap.verisign.com/com/v1/domain/clay.com",
          "checkedAt": "2026-11-15T15:26:29.983335746Z"
        },
        "pages": [
          {
            "url": "https://www.clay.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-11-17T21:20:19.116048629Z",
            "changedAt": "2026-11-17T21:20:19.116048629Z",
            "fingerprint": "846e3e0555d4"
          },
          {
            "url": "https://www.clay.com/pricing",
            "kind": "pricing",
            "status": 304,
            "checkedAt": "2026-11-17T21:20:23.207378549Z",
            "changedAt": "2026-11-07T14:26:49.021799488Z",
            "fingerprint": "bb5d6ec962be"
          },
          {
            "url": "https://www.clay.com/privacy",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-17T21:20:25.214237322Z",
            "changedAt": "2026-11-06T13:47:51.71498752Z",
            "fingerprint": "16c5785fb595"
          },
          {
            "url": "https://www.clay.com/legal/terms-of-service",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-17T21:20:21.518603588Z",
            "changedAt": "2026-11-06T13:47:47.817841965Z",
            "fingerprint": "8a7faa9726c3"
          },
          {
            "url": "https://www.clay.com/terms-of-service",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-04T08:38:40.984132884Z",
            "changedAt": "2026-11-03T08:04:32.731555169Z",
            "fingerprint": "149d41c853e1"
          }
        ],
        "github": {
          "repo": "clay-run/agent-plugins",
          "checkedAt": "2026-11-16T11:50:56.390543852Z",
          "stars": 150,
          "archived": false,
          "issuesEnabled": true,
          "pushedAt": "2026-11-12T17:23:38Z",
          "openIssues": 10,
          "openPRs": 3,
          "issuesOpened90d": 0,
          "issuesClosed90d": 0,
          "prsMerged90d": 0,
          "replies": {
            "sampled": 11,
            "unanswered": 10,
            "medianDays": 1.6
          }
        },
        "updatedAt": "2026-11-18T21:50:39.866047462Z"
      },
      "streak": {
        "days": 35,
        "from": "2026-10-14",
        "sinceWatching": true,
        "best": 35
      }
    },
    "answer": "Clay scores 58.3 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics.",
    "b": {
      "slug": "retriever",
      "name": "Retriever",
      "vendor": "Retriever",
      "vendorUrl": "https://retriever.run",
      "company": "retriever.run",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "Retriever is a hosted prospecting agent that finds and qualifies companies and contacts, enriches them with emails and phone numbers, and runs email and LinkedIn outreach, through a REST API and a remote MCP server.",
      "url": "https://www.anchorterminal.com/tools/retriever",
      "markdownUrl": "https://www.anchorterminal.com/tools/retriever.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/retriever.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/retriever.json",
      "dns": "retriever.grade.anchorterminal.com",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://api.retriever.run/mcp",
      "packages": [],
      "auth": "mixed",
      "authNotes": "Bearer API key (`ret_live_...`) made in the app under Settings \u003e API keys after a browser signup, shown once. The MCP server also takes OAuth 2.1 with dynamic client registration and PKCE, and the access token it issues is an ordinary API key named after the connection. No scopes or expiry were found: a key works as its creator in that person's organisation. Keys are revoked one by one in Settings; removing a connector doesn't revoke its key. The MCP docs also accept the key in the URL as `?api_key=`, with a warning about logs.",
      "pricing": "paid",
      "pricingNotes": "Starter from $80 a month billed quarterly for 6,000 credits ($0.0134 a credit), up to 40,000 credits a month, with one-off top-ups and credits kept 12 months. Email senders $2 each or $30 for unlimited, LinkedIn senders $10 an account. Credits per action are published, a work email 4 to 12, a phone 15 to 60, a company 0.5 to 2. Enterprise is through sales. No free tier or no-card trial was found; the terms say only that free tiers may be offered.",
      "priceSummary": "$0.0134 / credit",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the pricing page, the docs, llms.txt or the OpenAPI file, 18 November 2026. Credits come with a subscription bought in the app.",
        "endpoints": []
      },
      "toolCount": 67,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.retriever.run",
      "llmsTxt": "https://docs.retriever.run/llms.txt",
      "openapi": "https://docs.retriever.run/openapi.yaml",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.finder",
        "data.company",
        "web.search",
        "web.scrape"
      ],
      "tags": [
        "hosted",
        "mcp",
        "remote-mcp",
        "oauth",
        "openapi",
        "llms-txt",
        "closed-source",
        "paid",
        "subscription",
        "linkedin",
        "outreach",
        "no-status-page",
        "platform-rules",
        "eu"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 32,
        "grade": "F",
        "agentReady": false,
        "rank": 1455,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 21,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 49
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": -15,
        "warnings": [
          {
            "kind": "platform-rules",
            "name": "Breaks the rules of the platforms it acts on",
            "text": "Retriever connects a customer's LinkedIn accounts and sends invitations, messages, profile visits and post likes from them on a schedule, with messages a model writes, which LinkedIn's rules on automated activity forbid.",
            "deduct": -15,
            "since": "2026-11-18",
            "sources": [
              "https://docs.retriever.run/mcp/tools.md",
              "https://retriever.run/pricing",
              "https://www.linkedin.com/help/linkedin/answer/90586",
              "https://www.linkedin.com/help/linkedin/answer/a1341387"
            ]
          }
        ],
        "verdict": "Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.",
        "bestFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "strengths": [
          "OpenAPI 3.1 file, llms.txt and Markdown docs, with an errors page of stable codes and the action to take for each",
          "Remote MCP server with OAuth 2.1, dynamic client registration and PKCE, so a client connects without pasting a key",
          "Rate limits published per key and class (30 a minute for runs, 120 for services, 600 for reads and MCP messages), with Retry-After on 429",
          "Idempotency keys on run creation and a recipe for safe retries, plus read-only, destructive and idempotent hints on the MCP tools",
          "Credits per action and the dollar price per credit published without a login"
        ],
        "weaknesses": [
          "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted",
          "No status page, changelog, security.txt, disclosure policy or certification found",
          "Keys have no scopes or expiry, and the MCP docs accept the key in the URL as `?api_key=`",
          "No free tier or trial without a card found; access needs a browser signup and a subscription from $80 a month",
          "The terms and privacy policy name only \"Retriever\" under French law, with no company number or address, and the privacy policy doesn't mention connected LinkedIn or email accounts"
        ],
        "agentNotes": [
          "Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account",
          "Send an `Idempotency-Key` with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run",
          "Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them",
          "Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it",
          "On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "F",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 32
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 5,
          "payments": 30,
          "reliability": 45,
          "schema": 82,
          "security": 23,
          "transparency": 43
        },
        "provenanceScore": 54,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -s https://api.retriever.run/credits -H \"Authorization: Bearer $RETRIEVER_API_KEY\"",
        "claudeCode": "claude mcp add --transport http --scope user retriever https://api.retriever.run/mcp",
        "config": {
          "mcpServers": {
            "retriever": {
              "url": "https://api.retriever.run/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/retriever"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Credit, Starter plan",
          "unit": "credit",
          "usd": 0.0134,
          "note": "$80 a month billed quarterly for 6,000 credits"
        },
        {
          "item": "Work email found",
          "unit": "tx",
          "usd": 0.06,
          "note": "4 to 12 credits, about $0.06 to $0.18 per the pricing page"
        },
        {
          "item": "Phone number found",
          "unit": "tx",
          "usd": 0.22,
          "note": "15 to 60 credits, about $0.22 to $0.89 per the pricing page"
        },
        {
          "item": "LinkedIn sender",
          "unit": "account-month",
          "usd": 10,
          "note": "Per connected LinkedIn account"
        }
      ],
      "provenance": {
        "legalEntity": "Retriever",
        "domain": "retriever.run",
        "domainRegistered": "2026-04-07",
        "endpointOnVendorDomain": true,
        "terms": "https://retriever.run/terms",
        "privacy": "https://retriever.run/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The terms and privacy policy, both last updated 30 August 2026, name the entity only as Retriever, choose French law and the Paris courts, and give emma@retriever.run as the contact. No company number, address or register entry was found; the French company register (annuaire-entreprises.data.gouv.fr) answered with a bot check, so it wasn't searched.",
          "retriever.run/robots.txt allows every crawler. docs.retriever.run publishes rules that didn't close the pages read. The site carries a content-signals preamble in robots.txt with no ai-input=no.",
          "RDAP gives retriever.run a registration date of 7 April 2026.",
          "/.well-known/security.txt answered 404. No status page or changelog is linked from the site or the docs.",
          "The privacy policy names Vercel, Railway, Supabase, Anthropic and OpenAI as examples of subprocessors and says personal data isn't sold. It doesn't cover the LinkedIn and email accounts customers connect, or the data providers named on the pricing page."
        ],
        "score": 54
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/retriever.json",
      "live": {
        "slug": "retriever",
        "probe": {
          "target": "https://api.retriever.run/mcp",
          "method": "get",
          "lastAt": "2026-11-18T21:51:12.571692585Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 193,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 201,
          "p95ms24h": 385,
          "samples24h": 172,
          "samples30d": 172,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 172,
              "ok": 172
            }
          ],
          "since": "2026-11-18T04:42:08.539827226Z"
        },
        "securityTxt": {
          "url": "https://retriever.run/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:40.595836687Z"
        },
        "llmsTxt": {
          "url": "https://docs.retriever.run/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:58.22750683Z"
        },
        "pages": [
          {
            "url": "https://retriever.run/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:43.303154652Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "df5f8e8262ec"
          },
          {
            "url": "https://retriever.run/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-11-18T21:52:45.492573613Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "7d5324c0992b"
          }
        ],
        "updatedAt": "2026-11-18T21:52:45.492573613Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "edges": [
      {
        "by": 70,
        "category": "maintenance",
        "leads": "clay",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "clay plugin 2.35.0 on 4 November 2026, requiring CLI 1.14.0, whose tag sits on the 3 November release commit (30). 36 plugin releases from 7 August to 4 November, the last three (15 October, 3 and 4 November) changing skill content, plus weekly dated product roundups to the week of 26 October (20). Weekly dated product roundups and a support address, with the plugin's issue handling not visible (12 of 15). No official SDKs, the CLI is current (8 of 15). CLI binaries ship from GitHub releases, and the repository has no licence file (5 of 10). 30 + 20 + 12 + 8 + 5 = 75.",
          "b": "No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026."
        },
        "scores": {
          "a": 75,
          "b": 5
        }
      },
      {
        "by": 25,
        "category": "security",
        "leads": "clay",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "A personal API key tied to the user's workspace access, with no scopes documented. The CLI uses OAuth per workspace (15 of 30). Functions need API or MCP access switched on one by one, workspace roles apply, and the changelog adds IP access restrictions (week of 21 September) and MCP client allowlisting (week of 26 October). CLI 1.14.0 (3 November) can hold commands that delete, send or run at scale for the user's approval, but the Claude Code plugin's hook still auto-approves most clay CLI commands, including ones that spend credits (8 of 20). Claygent web research returns untrusted text, and no injection guidance was found (3 of 15). Credit balances and a workflow-run query, with no per-call audit log found (6 of 15). security.txt valid to 31 July 2027 naming security@clay.com and trust.clay.com, re-read on 4 November, and SOC 2 Type II, ISO 27001 and ISO 42001 listed on the pricing page. No bug bounty found (16 of 20). 15 + 8 + 3 + 6 + 16 = 48.",
          "b": "The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0)."
        },
        "scores": {
          "a": 48,
          "b": 23
        }
      },
      {
        "by": 15,
        "category": "payments",
        "leads": "clay",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Data credits from $0.05 and plan prices public, though on 4 November the plan cards still say $167 and $446 a month for Launch and Growth while the FAQ says $185 and $495 (15 of 20). A free plan with 100 data credits and 500 actions a month, and a page footer saying no credit card is required, while the FAQ lists Clay API access under Enterprise (15 of 20). A person signs up in a browser, and CLI sign-in opens a browser or a device code (0). 0 + 15 + 15 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.",
          "b": "No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0)."
        },
        "scores": {
          "a": 45,
          "b": 30
        }
      },
      {
        "by": 12,
        "category": "transparency",
        "leads": "clay",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed service under the Clay Services Agreement, last updated 1 November 2026 (New York law), and a plugin repository with no licence (12 of 30). The privacy policy still dates from 11 September 2020, gives no retention periods and says nothing on AI training. The new terms incorporate a DPA with breach notice without undue delay and 30 days' notice of new sub-processors, and say customer data isn't used to train models without approval, but name no retention periods (8 of 30). Deprecated endpoints are marked in the spec without removal dates (8 of 20). The DPA links a sub-processor list through a Google Doc that points to trust.clay.com/subprocessors, a Vanta page drawn by script whose robots.txt answers with the app page, so the list wasn't read (0). 12 + 8 + 8 + 0 = 28.",
          "b": "Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed \"with reasonable notice\" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20)."
        },
        "scores": {
          "a": 61,
          "b": 49
        }
      },
      {
        "by": 9,
        "category": "ergonomics",
        "leads": "retriever",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Table queries select fields and take a limit, and searches return up to 500 per request (20 of 25). Cursor pagination and stateful iterators, structured filters and an advanced query language (20). Status codes as the error category and a message, with no stable codes in the API, though the CLI has typed exit codes (10 of 20). Items carry caller IDs for matching results and failed enrichments aren't charged, but there are no idempotency keys (8 of 20). No official SDKs, and the CLI is JSON-first (8 of 15). 20 + 20 + 10 + 8 + 8 = 66.",
          "b": "67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15)."
        },
        "scores": {
          "a": 66,
          "b": 75
        }
      },
      {
        "by": 5,
        "category": "reliability",
        "leads": "retriever",
        "name": "Reliability",
        "reasons": {
          "a": "Graded with the hosted lines on the Public API. status.clay.com is linked from every page footer but answered with a Cloudflare bot check on 14 October, and on 4 November its robots.txt answered the same check, so the host is treated as blocked and its components stay unconfirmed (10 of 20, per the 14 October check, not re-read on 4 November). No readable history (5). A per-workspace request limit with no number, and published search-result caps per plan (8 of 15). 429 with Retry-After and X-RateLimit headers, backoff with jitter, and retries of 5xx only when a request is safe to retry, re-read on 4 November. No idempotency keys (12 of 15). The terms of 1 November 2026 replaced the May 2024 version and no longer set the 99.0 per cent monthly uptime target with fee credits, and no other SLA was found (0). The API is v0, and Workflows and run search are labelled alpha or beta (5 of 10). 10 + 5 + 8 + 12 + 0 + 5 = 40.",
          "b": "No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10)."
        },
        "scores": {
          "a": 40,
          "b": 45
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Clay Labs Inc.",
        "b": "Retriever",
        "name": "Vendor"
      },
      {
        "a": "https://api.clay.com/public/v0",
        "b": "https://api.retriever.run/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Freemium",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file",
        "b": "none",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "67",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "yes",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-11-04",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "not read yet",
        "b": "2026-08-30",
        "name": "Terms last updated"
      },
      {
        "a": "2020-09-11",
        "b": "2026-08-30",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not read yet",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not read yet",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Clay scores 58.3 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics.",
        "question": "Which is better for AI agents, Clay or Retriever?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Clay and Retriever need an API key?"
      },
      {
        "answer": "Yes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Retriever at https://api.retriever.run/mcp.",
        "question": "Can an agent call Clay and Retriever without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Security \u0026 auth, 48 against 23",
          "Payments \u0026 pricing, 45 against 30",
          "Maintenance \u0026 community, 75 against 5",
          "Transparency \u0026 trust, 61 against 49"
        ],
        "also": [
          "No incidents deducted, where Retriever loses 15 points for them"
        ],
        "goodFor": "Agents building prospect lists and enriching contacts or accounts through many providers at once.",
        "slug": "clay",
        "watchFor": "API keys carry no scopes and act with the user's workspace access"
      },
      {
        "aheadOn": [
          "Reliability, 45 against 40",
          "Agent ergonomics, 75 against 66"
        ],
        "also": null,
        "goodFor": "A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.",
        "slug": "retriever",
        "watchFor": "Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted"
      }
    ],
    "history": {
      "clay": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.9,
          "from": 56.4,
          "fromGrade": "C",
          "to": 58.3,
          "toGrade": "C"
        },
        {
          "causes": [
            "terms"
          ],
          "date": "2026-11-04",
          "delta": -1.3,
          "from": 57.7,
          "fromGrade": "C",
          "to": 56.4,
          "toGrade": "C"
        }
      ],
      "retriever": null
    },
    "job": {
      "capability": "lead.search",
      "name": "Lead search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-clay.json",
        "title": "Apollo API + MCP vs Clay",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-clay"
      },
      {
        "json": "https://www.anchorterminal.com/compare/apollo-vs-retriever.json",
        "title": "Apollo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-coresignal.json",
        "title": "Clay vs Coresignal API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-coresignal"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-crustdata.json",
        "title": "Clay vs Crustdata API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-crustdata"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-databar.json",
        "title": "Clay vs Databar",
        "url": "https://www.anchorterminal.com/compare/clay-vs-databar"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-dievio.json",
        "title": "Clay vs Dievio",
        "url": "https://www.anchorterminal.com/compare/clay-vs-dievio"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-enrich-layer.json",
        "title": "Clay vs Enrich Layer API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-enrich-layer"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource.json",
        "title": "Clay vs Explorium AgentSource",
        "url": "https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-fullenrich.json",
        "title": "Clay vs FullEnrich API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-fullenrich"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-fuse-mcp.json",
        "title": "Clay vs Fuse MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-fuse-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-gojiberry.json",
        "title": "Clay vs Gojiberry",
        "url": "https://www.anchorterminal.com/compare/clay-vs-gojiberry"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-hunter.json",
        "title": "Clay vs Hunter API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-hunter"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-leadmagic.json",
        "title": "Clay vs LeadMagic API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-leadmagic"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-lusha.json",
        "title": "Clay vs Lusha API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-lusha"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-people-data-labs.json",
        "title": "Clay vs People Data Labs",
        "url": "https://www.anchorterminal.com/compare/clay-vs-people-data-labs"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-prospeo.json",
        "title": "Clay vs Prospeo API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-prospeo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-rocketreach.json",
        "title": "Clay vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/clay-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-zoominfo.json",
        "title": "Clay vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/coresignal-vs-retriever.json",
        "title": "Coresignal API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-retriever.json",
        "title": "Crustdata API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dievio-vs-retriever.json",
        "title": "Dievio vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dievio-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.json",
        "title": "Enrich Layer API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.json",
        "title": "Explorium AgentSource vs Retriever",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever.json",
        "title": "FullEnrich API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.json",
        "title": "Fuse MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever.json",
        "title": "Gojiberry vs Retriever",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever.json",
        "title": "LeadMagic API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-retriever.json",
        "title": "Lusha API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.json",
        "title": "People Data Labs vs Retriever",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/prospeo-vs-retriever.json",
        "title": "Prospeo API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/prospeo-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach.json",
        "title": "Retriever vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo.json",
        "title": "Retriever vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zoominfo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-clearbit.json",
        "title": "Clay vs Clearbit",
        "url": "https://www.anchorterminal.com/compare/clay-vs-clearbit"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-dropcontact.json",
        "title": "Clay vs Dropcontact API + MCP",
        "url": "https://www.anchorterminal.com/compare/clay-vs-dropcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-fullcontact.json",
        "title": "Clay vs FullContact",
        "url": "https://www.anchorterminal.com/compare/clay-vs-fullcontact"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clay-vs-zerobounce.json",
        "title": "Clay vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/clay-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clearbit-vs-retriever.json",
        "title": "Clearbit vs Retriever",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/databar-vs-retriever.json",
        "title": "Databar vs Retriever",
        "url": "https://www.anchorterminal.com/compare/databar-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever.json",
        "title": "Dropcontact API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever.json",
        "title": "FullContact vs Retriever",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-retriever"
      },
      {
        "json": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce.json",
        "title": "Retriever vs ZeroBounce",
        "url": "https://www.anchorterminal.com/compare/retriever-vs-zerobounce"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-retriever.json",
        "title": "Hunter API + MCP vs Retriever",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-retriever"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 5,
        "clay": 40,
        "edge": "retriever",
        "key": "reliability",
        "name": "Reliability",
        "retriever": 45,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 2,
        "clay": 84,
        "edge": "clay",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "retriever": 82,
        "weight": 13
      },
      {
        "by": 9,
        "clay": 66,
        "edge": "retriever",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "retriever": 75,
        "weight": 13
      },
      {
        "by": 25,
        "clay": 48,
        "edge": "clay",
        "key": "security",
        "name": "Security \u0026 auth",
        "retriever": 23,
        "weight": 14
      },
      {
        "by": 15,
        "clay": 45,
        "edge": "clay",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "retriever": 30,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 70,
        "clay": 75,
        "edge": "clay",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "retriever": 5,
        "weight": 7
      },
      {
        "by": 12,
        "clay": 61,
        "edge": "clay",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "retriever": 49,
        "weight": 7
      }
    ],
    "summary": "Clay scores 58.3 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics. Both do lead search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "clay": "A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI and plugin released 36 times since 7 August, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, the new terms set no uptime target, and the privacy policy dates from 2020.",
      "retriever": "Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/clay-vs-retriever",
    "json": "https://www.anchorterminal.com/compare/clay-vs-retriever.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/clay-vs-retriever.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/clay-vs-retriever.min.md"
  },
  "markdown": "Clay scores 58.3 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics. Both do lead search.\n\n- Clay: grade C, 58.3/100, rank #857 of 1557. Markdown https://www.anchorterminal.com/tools/clay.md · JSON https://www.anchorterminal.com/api/v1/tools/clay.json\n- Retriever: grade F, 32/100, rank #1455 of 1557. Markdown https://www.anchorterminal.com/tools/retriever.md · JSON https://www.anchorterminal.com/api/v1/tools/retriever.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 253 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md\n\n## Which one, for what\n\n### Clay (C)\n\nGood for: Agents building prospect lists and enriching contacts or accounts through many providers at once.\n\nAhead on:\n- Security \u0026 auth, 48 against 23\n- Payments \u0026 pricing, 45 against 30\n- Maintenance \u0026 community, 75 against 5\n- Transparency \u0026 trust, 61 against 49\n\nAlso in its favour:\n- No incidents deducted, where Retriever loses 15 points for them\n\nWatch for: API keys carry no scopes and act with the user's workspace access\n\n### Retriever (F)\n\nGood for: A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.\n\nAhead on:\n- Reliability, 45 against 40\n- Agent ergonomics, 75 against 66\n\nWatch for: Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Clay +70\n\n- Clay (75): clay plugin 2.35.0 on 4 November 2026, requiring CLI 1.14.0, whose tag sits on the 3 November release commit (30). 36 plugin releases from 7 August to 4 November, the last three (15 October, 3 and 4 November) changing skill content, plus weekly dated product roundups to the week of 26 October (20). Weekly dated product roundups and a support address, with the plugin's issue handling not visible (12 of 15). No official SDKs, the CLI is current (8 of 15). CLI binaries ship from GitHub releases, and the repository has no licence file (5 of 10). 30 + 20 + 12 + 8 + 5 = 75.\n- Retriever (5): No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.\n\n### Security \u0026 auth: Clay +25\n\n- Clay (48): A personal API key tied to the user's workspace access, with no scopes documented. The CLI uses OAuth per workspace (15 of 30). Functions need API or MCP access switched on one by one, workspace roles apply, and the changelog adds IP access restrictions (week of 21 September) and MCP client allowlisting (week of 26 October). CLI 1.14.0 (3 November) can hold commands that delete, send or run at scale for the user's approval, but the Claude Code plugin's hook still auto-approves most clay CLI commands, including ones that spend credits (8 of 20). Claygent web research returns untrusted text, and no injection guidance was found (3 of 15). Credit balances and a workflow-run query, with no per-call audit log found (6 of 15). security.txt valid to 31 July 2027 naming security@clay.com and trust.clay.com, re-read on 4 November, and SOC 2 Type II, ISO 27001 and ISO 42001 listed on the pricing page. No bug bounty found (16 of 20). 15 + 8 + 3 + 6 + 16 = 48.\n- Retriever (23): The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (20), less 10 because the MCP docs offer the key in the URL as `?api_key=` (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).\n\n### Payments \u0026 pricing: Clay +15\n\n- Clay (45): No x402, MPP or L402 (0). Data credits from $0.05 and plan prices public, though on 4 November the plan cards still say $167 and $446 a month for Launch and Growth while the FAQ says $185 and $495 (15 of 20). A free plan with 100 data credits and 500 actions a month, and a page footer saying no credit card is required, while the FAQ lists Clay API access under Enterprise (15 of 20). A person signs up in a browser, and CLI sign-in opens a browser or a device code (0). 0 + 15 + 15 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.\n- Retriever (30): No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).\n\n### Transparency \u0026 trust: Clay +12\n\n- Clay (61): Closed service under the Clay Services Agreement, last updated 1 November 2026 (New York law), and a plugin repository with no licence (12 of 30). The privacy policy still dates from 11 September 2020, gives no retention periods and says nothing on AI training. The new terms incorporate a DPA with breach notice without undue delay and 30 days' notice of new sub-processors, and say customer data isn't used to train models without approval, but name no retention periods (8 of 30). Deprecated endpoints are marked in the spec without removal dates (8 of 20). The DPA links a sub-processor list through a Google Doc that points to trust.clay.com/subprocessors, a Vanta page drawn by script whose robots.txt answers with the app page, so the list wasn't read (0). 12 + 8 + 8 + 0 = 28.\n- Retriever (49): Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed \"with reasonable notice\" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).\n\n### Agent ergonomics: Retriever +9\n\n- Clay (66): Table queries select fields and take a limit, and searches return up to 500 per request (20 of 25). Cursor pagination and stateful iterators, structured filters and an advanced query language (20). Status codes as the error category and a message, with no stable codes in the API, though the CLI has typed exit codes (10 of 20). Items carry caller IDs for matching results and failed enrichments aren't charged, but there are no idempotency keys (8 of 20). No official SDKs, and the CLI is JSON-first (8 of 15). 20 + 20 + 10 + 8 + 8 = 66.\n- Retriever (75): 67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).\n\n### Reliability: Retriever +5\n\n- Clay (40): Graded with the hosted lines on the Public API. status.clay.com is linked from every page footer but answered with a Cloudflare bot check on 14 October, and on 4 November its robots.txt answered the same check, so the host is treated as blocked and its components stay unconfirmed (10 of 20, per the 14 October check, not re-read on 4 November). No readable history (5). A per-workspace request limit with no number, and published search-result caps per plan (8 of 15). 429 with Retry-After and X-RateLimit headers, backoff with jitter, and retries of 5xx only when a request is safe to retry, re-read on 4 November. No idempotency keys (12 of 15). The terms of 1 November 2026 replaced the May 2024 version and no longer set the 99.0 per cent monthly uptime target with fee credits, and no other SLA was found (0). The API is v0, and Workflows and run search are labelled alpha or beta (5 of 10). 10 + 5 + 8 + 12 + 0 + 5 = 40.\n- Retriever (45): No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists \"Dedicated support \u0026 SLA\" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).\n\n## Score by category\n\n| Category | Weight | Clay | Retriever | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 40 | 45 | Retriever +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 84 | 82 | Clay +2 |\n| Agent ergonomics | 13% | 66 | 75 | Retriever +9 |\n| Security \u0026 auth | 14% | 48 | 23 | Clay +25 |\n| Payments \u0026 pricing | 10% | 45 | 30 | Clay +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 75 | 5 | Clay +70 |\n| Transparency \u0026 trust | 7% | 61 | 49 | Clay +12 |\n| Negative events | ≤15 | 0 | -15 | |\n| **Total** | | **58.3 · C** | **32 · F** | |\n\n## Facts side by side\n\n| Fact | Clay | Retriever |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Clay Labs Inc. | Retriever |\n| Hosted endpoint | `https://api.clay.com/public/v0` | `https://api.retriever.run/mcp` |\n| Transports | HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file | none |\n| Tools exposed | none | 67 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-11-04 | none |\n| Terms last updated | not read yet | 2026-08-30 |\n| Privacy policy last updated | 2020-09-11 | 2026-08-30 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n\n## How the scores have moved\n\n### Clay\n\n- +1.9 on 13 November 2026: checklist\n- -1.3 on 4 November 2026: terms\n\n### Retriever\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Clay.** A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI and plugin released 36 times since 7 August, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, the new terms set no uptime target, and the privacy policy dates from 2020.\n\n**Retriever.** Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.\n\n## Before you call either\n\n### Clay\n\n1. Fetch GET /search/query-mode/reference before writing a search query\n2. Poll routine results until a terminal 200, since 202 means still running\n3. Expect HTTP 402 when a plan's search cap is hit, and tell the user the reset date\n4. Check GET /credits/balance before large batch runs\n5. When a CLI command answers approval_required, tell the user what it would do and let them approve or deny it\n6. Ask the user before enabling the plugin's auto-approve hook in a shared workspace\n\n### Retriever\n\n1. Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account\n2. Send an `Idempotency-Key` with each run and replay with the same key after a timeout, so a retry doesn't start a second billed run\n3. Run `getEmail`, `getPhoneNumber` and `webResearch` through `service_batch_execute`, even for one person; `service_execute` refuses them\n4. Check `credits` before a paid run, and call `service_inspect` for a service's `thingsToKnow` and credit cost before executing it\n5. On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again\n\n## Questions\n\n### Which is better for AI agents, Clay or Retriever?\n\nClay scores 58.3 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics.\n\n### Do Clay and Retriever need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Clay and Retriever without installing anything?\n\nYes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Retriever at https://api.retriever.run/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clay-vs-retriever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clay-vs-retriever.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clay\", \"b\": \"retriever\"}`. From a terminal: `anchor compare clay retriever`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clay.json and https://www.anchorterminal.com/api/v1/tools/retriever.json\n\n## Other comparisons with Clay or Retriever\n\n- [Apollo API + MCP vs Clay](https://www.anchorterminal.com/compare/apollo-vs-clay.md)\n- [Apollo API + MCP vs Retriever](https://www.anchorterminal.com/compare/apollo-vs-retriever.md)\n- [Clay vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clay-vs-coresignal.md)\n- [Clay vs Crustdata API + MCP](https://www.anchorterminal.com/compare/clay-vs-crustdata.md)\n- [Clay vs Databar](https://www.anchorterminal.com/compare/clay-vs-databar.md)\n- [Clay vs Dievio](https://www.anchorterminal.com/compare/clay-vs-dievio.md)\n- [Clay vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/clay-vs-enrich-layer.md)\n- [Clay vs Explorium AgentSource](https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource.md)\n- [Clay vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clay-vs-fullenrich.md)\n- [Clay vs Fuse MCP](https://www.anchorterminal.com/compare/clay-vs-fuse-mcp.md)\n- [Clay vs Gojiberry](https://www.anchorterminal.com/compare/clay-vs-gojiberry.md)\n- [Clay vs Hunter API + MCP](https://www.anchorterminal.com/compare/clay-vs-hunter.md)\n- [Clay vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/clay-vs-leadmagic.md)\n- [Clay vs Lusha API + MCP](https://www.anchorterminal.com/compare/clay-vs-lusha.md)\n- [Clay vs People Data Labs](https://www.anchorterminal.com/compare/clay-vs-people-data-labs.md)\n- [Clay vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clay-vs-prospeo.md)\n- [Clay vs RocketReach API](https://www.anchorterminal.com/compare/clay-vs-rocketreach.md)\n- [Clay vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/clay-vs-zoominfo.md)\n- [Coresignal API + MCP vs Retriever](https://www.anchorterminal.com/compare/coresignal-vs-retriever.md)\n- [Crustdata API + MCP vs Retriever](https://www.anchorterminal.com/compare/crustdata-vs-retriever.md)\n- [Dievio vs Retriever](https://www.anchorterminal.com/compare/dievio-vs-retriever.md)\n- [Enrich Layer API + MCP vs Retriever](https://www.anchorterminal.com/compare/enrich-layer-vs-retriever.md)\n- [Explorium AgentSource vs Retriever](https://www.anchorterminal.com/compare/explorium-agentsource-vs-retriever.md)\n- [FullEnrich API + MCP vs Retriever](https://www.anchorterminal.com/compare/fullenrich-vs-retriever.md)\n- [Fuse MCP vs Retriever](https://www.anchorterminal.com/compare/fuse-mcp-vs-retriever.md)\n- [Gojiberry vs Retriever](https://www.anchorterminal.com/compare/gojiberry-vs-retriever.md)\n- [LeadMagic API + MCP vs Retriever](https://www.anchorterminal.com/compare/leadmagic-vs-retriever.md)\n- [Lusha API + MCP vs Retriever](https://www.anchorterminal.com/compare/lusha-vs-retriever.md)\n- [People Data Labs vs Retriever](https://www.anchorterminal.com/compare/people-data-labs-vs-retriever.md)\n- [Prospeo API + MCP vs Retriever](https://www.anchorterminal.com/compare/prospeo-vs-retriever.md)\n- [Retriever vs RocketReach API](https://www.anchorterminal.com/compare/retriever-vs-rocketreach.md)\n- [Retriever vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/retriever-vs-zoominfo.md)\n- [Clay vs Clearbit](https://www.anchorterminal.com/compare/clay-vs-clearbit.md)\n- [Clay vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clay-vs-dropcontact.md)\n- [Clay vs FullContact](https://www.anchorterminal.com/compare/clay-vs-fullcontact.md)\n- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)\n- [Clearbit vs Retriever](https://www.anchorterminal.com/compare/clearbit-vs-retriever.md)\n- [Databar vs Retriever](https://www.anchorterminal.com/compare/databar-vs-retriever.md)\n- [Dropcontact API + MCP vs Retriever](https://www.anchorterminal.com/compare/dropcontact-vs-retriever.md)\n- [FullContact vs Retriever](https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md)\n- [Retriever vs ZeroBounce](https://www.anchorterminal.com/compare/retriever-vs-zerobounce.md)\n- [Hunter API + MCP vs Retriever](https://www.anchorterminal.com/compare/hunter-vs-retriever.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Clay vs Retriever",
        "url": ""
      }
    ],
    "description": "Clay scores 58.3 (C) to Retriever's 32 (F) for lead search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Clay C 58.3",
      "Retriever F 32",
      "scores"
    ],
    "h1": "Clay vs Retriever",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/clay-vs-retriever",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Clay vs Retriever for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/clay-vs-retriever"
  },
  "tokens": {
    "markdown": 4800,
    "slim": 1080
  },
  "version": 1
}
