{
  "data": {
    "a": {
      "slug": "clay",
      "name": "Clay",
      "vendor": "Clay Labs Inc.",
      "vendorUrl": "https://www.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",
      "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-10-14).",
      "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-10-06",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 57.7,
        "grade": "C",
        "agentReady": false,
        "rank": 633,
        "ranked": true,
        "rankOf": 1076,
        "categoryRank": 8,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 66,
          "maintenance": 75,
          "payments": 30,
          "reliability": 45,
          "schema": 84,
          "security": 48,
          "transparency": 64
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-14"
        },
        "negative": 0,
        "verdict": "A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI released several times a fortnight, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, 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 with JSON output and typed exit codes, released five times between 25 September and 6 October 2026",
          "Valid security.txt 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",
          "Privacy policy dated September 2020 with no retention periods",
          "Pricing page gives two different prices for Launch and Growth, and says API access is Enterprise"
        ],
        "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",
          "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": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 57.7
          }
        ],
        "editorialScores": {
          "ergonomics": 66,
          "maintenance": 75,
          "payments": 30,
          "reliability": 45,
          "schema": 84,
          "security": 48,
          "transparency": 28
        },
        "provenanceScore": 99
      },
      "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/terms-of-service",
        "privacy": "https://www.clay.com/privacy",
        "statusPage": "https://status.clay.com",
        "changelog": "https://www.clay.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-10-14",
        "notes": [
          "The terms (last updated 23 May 2024) name Clay Labs Inc. with New York law. The privacy policy is dated 11 September 2020.",
          "clay.com/.well-known/security.txt names security@clay.com and trust.clay.com, expiring 2027-07-31.",
          "status.clay.com answered with a bot check to both curl and WebFetch, 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": 99
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/clay.json",
      "live": {
        "slug": "clay",
        "probe": {
          "target": "https://api.clay.com/public/v0",
          "method": "get",
          "lastAt": "2026-10-14T09:41:46.249843895Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 152,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 149,
          "p95ms24h": 229,
          "samples24h": 17,
          "samples30d": 17,
          "days": [
            {
              "date": "2026-10-14",
              "probes": 17,
              "ok": 17
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.clay.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-14T08:52:50.29728454Z"
        },
        "updatedAt": "2026-10-14T09:41:46.249843895Z"
      }
    },
    "answer": "Clay scores 57.7 (C) on agent readiness against RocketReach API's 51.2 (D), and leads in 5 of 7 scored categories. RocketReach API leads on reliability and agent ergonomics.",
    "b": {
      "slug": "rocketreach",
      "name": "RocketReach API",
      "vendor": "RocketReach, LLC",
      "vendorUrl": "https://rocketreach.co",
      "kind": "http-api",
      "category": "lead-data",
      "summary": "RocketReach is a contact and company database with people and company search, contact lookup, bulk lookup and single-address email verification. Agents reach it through a REST API (v2) with an account API key, or a hosted MCP server with OAuth.",
      "url": "https://www.anchorterminal.com/tools/rocketreach",
      "markdownUrl": "https://www.anchorterminal.com/tools/rocketreach.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/rocketreach.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/rocketreach.json",
      "repo": "https://github.com/rocketreach/rocketreach_python",
      "license": "Proprietary service under RocketReach's Terms of Service. The Python SDK on GitHub is MIT",
      "transports": [
        "http",
        "streamable-http"
      ],
      "remoteUrl": "https://api.rocketreach.co/api/v2",
      "packages": [
        {
          "registry": "pypi",
          "name": "rocketreach"
        }
      ],
      "auth": "mixed",
      "authNotes": "A person signs up in a browser and generates a key in account settings. REST calls send it in the `Api-Key` header. One key is active per account, and generating a new one invalidates the old. The `api_key` query parameter is deprecated. The MCP server at https://mcp.rocketreach.co/mcp uses OAuth 2.1 with PKCE and open dynamic client registration, with one scope, `rocketreach:read`, and the user approves access in a browser. The docs list an account with API access as a prerequisite.",
      "pricing": "paid",
      "pricingNotes": "No price was read. The pricing page is drawn by script and showed only its title (checked 2026-10-09). The docs name four API plans, Essentials, Pro, Ultimate and Custom, and tell users without a paid plan to email for an API plan. Universal Credits cost 2 for a professional email, 3 for a personal email, 6 for a phone and 1 a page of person search. Whether a free account or trial includes API calls was not established. Fees are non-refundable under the Subscription Agreement.",
      "priceSummary": "Paid",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the docs index, the reference pages or the terms (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": 9,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.rocketreach.co/",
      "llmsTxt": "https://docs.rocketreach.co/llms.txt",
      "capabilities": [
        "lead.search",
        "lead.enrichment",
        "email.verification",
        "email.finder",
        "data.company"
      ],
      "tags": [
        "hosted",
        "mcp",
        "oauth",
        "api-key",
        "llms-txt",
        "webhooks",
        "async-jobs",
        "credits",
        "lead-search",
        "enrichment",
        "email-verification",
        "status-page",
        "closed-source"
      ],
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 51.2,
        "grade": "D",
        "agentReady": false,
        "rank": 805,
        "ranked": true,
        "rankOf": 1076,
        "categoryRank": 13,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 72,
          "maintenance": 31,
          "payments": 10,
          "reliability": 64,
          "schema": 72,
          "security": 34,
          "transparency": 58
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": 0,
        "verdict": "The hosted MCP server has nine documented tools, OAuth 2.1 with dynamic client registration and machine-readable error codes, and searches cost no credits. Plan prices were not readable, the docs send API plan requests to email, the terms require a human account holder, and the `account` tool returns the account's API key to the model.",
        "bestFor": "Teams that already hold a RocketReach plan and want an agent to search people and companies, reveal emails and phones, and verify single addresses over MCP.",
        "strengths": [
          "Hosted MCP server with nine documented tools, OAuth 2.1 with PKCE, dynamic client registration, one-hour access tokens and rotating refresh tokens",
          "MCP errors carry a stable `error_code` in `_meta`, with `retry_after_seconds`, `credit_type` or the failing `field`",
          "Rate limits published per plan and per endpoint by minute, hour, day and month, and 429 responses carry `Retry-After`",
          "Lookups that find no data are not charged, B and F grade emails are not charged, and repeat lookups of a profile are free while the plan is active",
          "Status page with separate API and MCP components, and the 27 September 2026 maintenance was announced 12 days ahead"
        ],
        "weaknesses": [
          "The pricing page is drawn by script and was not read, and the docs tell users without a paid plan to email for an API plan",
          "The MCP `account` tool returns the account's API key in its response, and the OAuth access token carries the same key inside it",
          "One API key per account with no scopes. The single MCP scope `rocketreach:read` covers the tools that spend credits and add contacts",
          "On 20 August 2026 the status page shows ten hours of degraded performance across the site, API and MCP, then a 29-minute outage",
          "The terms say account holders warrant they are human and forbid automated extraction of lookup data. No deduction is taken, and it matters before any probe is run",
          "No changelog or deprecation policy was found, and the Python SDK's last code change is dated 26 March 2025"
        ],
        "agentNotes": [
          "Search first with `person_search` or `company_search`, which cost no credits, then look up only the profile IDs needed",
          "Treat `status: \"pending\"` as normal. Poll `check_person_status` after at least 3 seconds, and polling is free",
          "Do not echo the `account` tool's output to users or logs. It includes the account's API key",
          "Send the key in the `Api-Key` header. The `api_key` query parameter is deprecated",
          "Bulk lookup takes 1 to 100 queries and needs a webhook. Results arrive at the webhook, signed in `X-RocketReach-Signature`",
          "Do not loop on `unknown` from `email_verify`, or on `lookup_failed` and `not_found`. The last two are terminal"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 51.2
          }
        ],
        "editorialScores": {
          "ergonomics": 72,
          "maintenance": 31,
          "payments": 10,
          "reliability": 64,
          "schema": 72,
          "security": 34,
          "transparency": 45
        },
        "provenanceScore": 70
      },
      "connect": {
        "claudeCode": "claude mcp add rocketreach https://mcp.rocketreach.co/mcp",
        "config": {
          "mcpServers": {
            "rocketreach": {
              "url": "https://mcp.rocketreach.co/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/lead.search",
        "tool": "https://letme.dev/rocketreach"
      },
      "area": "web-data",
      "provenance": {
        "legalEntity": "RocketReach, LLC",
        "domain": "rocketreach.co",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://rocketreach.co/terms",
        "privacy": "https://rocketreach.co/privacy",
        "statusPage": "https://status.rocketreach.co",
        "changelog": "",
        "securityTxt": "valid",
        "checked": "2026-10-09",
        "notes": [
          "The Terms of Service (updated 31 January 2024) name RocketReach, LLC, 144 N 7th St, PO #421, Brooklyn, NY 11211, are governed by Washington law, and say they apply to users of the API and their end users.",
          "The API answers at api.rocketreach.co and the MCP server at mcp.rocketreach.co, both subdomains of the vendor's domain.",
          "https://rocketreach.co/.well-known/security.txt gives a contact address and expires on 8 June 2029.",
          "Paid subscribers also accept a Subscription Agreement at https://rocketreach.co/subscriber_terms, and a DPA at https://rocketreach.co/dpa forms part of the terms.",
          "No changelog was found on the docs site or the main site. The registration date of rocketreach.co was not established."
        ],
        "score": 70
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/rocketreach.json",
      "live": {
        "slug": "rocketreach",
        "probe": {
          "target": "https://api.rocketreach.co/api/v2",
          "method": "get",
          "lastAt": "2026-10-14T09:42:05.038892767Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 553,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 558,
          "p95ms24h": 984,
          "samples24h": 248,
          "samples30d": 1174,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-11",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-12",
              "probes": 247,
              "ok": 247
            },
            {
              "date": "2026-10-13",
              "probes": 248,
              "ok": 248
            },
            {
              "date": "2026-10-14",
              "probes": 100,
              "ok": 100
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.rocketreach.co",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-14T09:39:39.603415232Z"
        },
        "versions": [
          {
            "registry": "pypi",
            "name": "rocketreach",
            "version": "2.1.8",
            "released": "2025-03-26",
            "seenAt": "2026-10-13T23:21:46.54539208Z"
          }
        ],
        "githubStars": 18,
        "pypiWeekly": 14653,
        "securityTxt": {
          "url": "https://rocketreach.co/.well-known/security.txt",
          "state": "valid",
          "expires": "2029-06-08T12:13:00Z",
          "checkedAt": "2026-10-13T15:45:31.303580155Z"
        },
        "llmsTxt": {
          "url": "https://docs.rocketreach.co/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-10-13T14:12:29.674557672Z"
        },
        "domain": {
          "domain": "rocketreach.co",
          "checkedAt": "2026-10-11T13:14:56.065752776Z"
        },
        "pages": [
          {
            "url": "https://rocketreach.co/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-13T20:22:20.975114224Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "bb39d156c3b5"
          },
          {
            "url": "https://rocketreach.co/terms",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-13T20:22:23.303877917Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "ac842cb8d9d8"
          }
        ],
        "updatedAt": "2026-10-14T09:42:05.038892767Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Clay Labs Inc.",
        "b": "RocketReach, LLC",
        "name": "Vendor"
      },
      {
        "a": "https://api.clay.com/public/v0",
        "b": "https://api.rocketreach.co/api/v2",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP",
        "b": "HTTP, 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": "Proprietary service under RocketReach's Terms of Service. The Python SDK on GitHub is MIT",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "9",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-06",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2024-05-23",
        "b": "2024-01-31",
        "name": "Terms last updated"
      },
      {
        "a": "2020-09-11",
        "b": "2026-09-30",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Clay scores 57.7 (C) on agent readiness against RocketReach API's 51.2 (D), and leads in 5 of 7 scored categories. RocketReach API leads on reliability and agent ergonomics.",
        "question": "Which is better for AI agents, Clay or RocketReach API?"
      },
      {
        "answer": "Both take an API key or an OAuth sign-in.",
        "question": "Do Clay and RocketReach API need an API key?"
      },
      {
        "answer": "Yes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and RocketReach API at https://api.rocketreach.co/api/v2.",
        "question": "Can an agent call Clay and RocketReach API without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 84 against 72",
          "Security \u0026 auth, 48 against 34",
          "Payments \u0026 pricing, 30 against 10",
          "Maintenance \u0026 community, 75 against 31",
          "Transparency \u0026 trust, 64 against 58"
        ],
        "also": null,
        "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, 64 against 45",
          "Agent ergonomics, 72 against 66"
        ],
        "also": null,
        "goodFor": "Teams that already hold a RocketReach plan and want an agent to search people and companies, reveal emails and phones, and verify single addresses over MCP.",
        "slug": "rocketreach",
        "watchFor": "The pricing page is drawn by script and was not read, and the docs tell users without a paid plan to email for an API plan"
      }
    ],
    "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-rocketreach.json",
        "title": "Apollo API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/apollo-vs-rocketreach"
      },
      {
        "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-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-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-rocketreach.json",
        "title": "Coresignal API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/coresignal-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/crustdata-vs-rocketreach.json",
        "title": "Crustdata API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/crustdata-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/enrich-layer-vs-rocketreach.json",
        "title": "Enrich Layer API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/enrich-layer-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-rocketreach.json",
        "title": "Explorium AgentSource vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/explorium-agentsource-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach.json",
        "title": "FullEnrich API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fuse-mcp-vs-rocketreach.json",
        "title": "Fuse MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/fuse-mcp-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/gojiberry-vs-rocketreach.json",
        "title": "Gojiberry vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/gojiberry-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/leadmagic-vs-rocketreach.json",
        "title": "LeadMagic API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/leadmagic-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/lusha-vs-rocketreach.json",
        "title": "Lusha API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/lusha-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/people-data-labs-vs-rocketreach.json",
        "title": "People Data Labs vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/people-data-labs-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/prospeo-vs-rocketreach.json",
        "title": "Prospeo API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/prospeo-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/rocketreach-vs-zoominfo.json",
        "title": "RocketReach API vs ZoomInfo API + MCP",
        "url": "https://www.anchorterminal.com/compare/rocketreach-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/clearbit-vs-rocketreach.json",
        "title": "Clearbit vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/clearbit-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.json",
        "title": "Dropcontact API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fullcontact-vs-rocketreach.json",
        "title": "FullContact vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/fullcontact-vs-rocketreach"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hunter-vs-rocketreach.json",
        "title": "Hunter API + MCP vs RocketReach API",
        "url": "https://www.anchorterminal.com/compare/hunter-vs-rocketreach"
      }
    ],
    "scores": [
      {
        "by": 19,
        "clay": 45,
        "edge": "rocketreach",
        "key": "reliability",
        "name": "Reliability",
        "rocketreach": 64,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 12,
        "clay": 84,
        "edge": "clay",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "rocketreach": 72,
        "weight": 13
      },
      {
        "by": 6,
        "clay": 66,
        "edge": "rocketreach",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "rocketreach": 72,
        "weight": 13
      },
      {
        "by": 14,
        "clay": 48,
        "edge": "clay",
        "key": "security",
        "name": "Security \u0026 auth",
        "rocketreach": 34,
        "weight": 14
      },
      {
        "by": 20,
        "clay": 30,
        "edge": "clay",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "rocketreach": 10,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 44,
        "clay": 75,
        "edge": "clay",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "rocketreach": 31,
        "weight": 7
      },
      {
        "by": 6,
        "clay": 64,
        "edge": "clay",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "rocketreach": 58,
        "weight": 7
      }
    ],
    "summary": "Clay scores 57.7 (C) on agent readiness against RocketReach API's 51.2 (D), and leads in 5 of 7 scored categories. RocketReach API leads on reliability and agent ergonomics. Both do lead search.",
    "verdicts": {
      "clay": "A documented Public API with an OpenAPI spec, llms.txt and plan-capped search, plus a JSON-first CLI released several times a fortnight, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, and the privacy policy dates from 2020.",
      "rocketreach": "The hosted MCP server has nine documented tools, OAuth 2.1 with dynamic client registration and machine-readable error codes, and searches cost no credits. Plan prices were not readable, the docs send API plan requests to email, the terms require a human account holder, and the `account` tool returns the account's API key to the model."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/clay-vs-rocketreach",
    "json": "https://www.anchorterminal.com/compare/clay-vs-rocketreach.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/clay-vs-rocketreach.md",
    "slim": "https://www.anchorterminal.com/compare/clay-vs-rocketreach.min.md"
  },
  "markdown": "Clay scores 57.7 (C) on agent readiness against RocketReach API's 51.2 (D), and leads in 5 of 7 scored categories. RocketReach API leads on reliability and agent ergonomics. Both do lead search.\n\n- Clay: grade C, 57.7/100, rank #633 of 1076. Markdown https://www.anchorterminal.com/tools/clay.md · JSON https://www.anchorterminal.com/api/v1/tools/clay.json\n- RocketReach API: grade D, 51.2/100, rank #805 of 1076. Markdown https://www.anchorterminal.com/tools/rocketreach.md · JSON https://www.anchorterminal.com/api/v1/tools/rocketreach.json\n- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md\n- All 171 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- Schema \u0026 documentation, 84 against 72\n- Security \u0026 auth, 48 against 34\n- Payments \u0026 pricing, 30 against 10\n- Maintenance \u0026 community, 75 against 31\n- Transparency \u0026 trust, 64 against 58\n\nWatch for: API keys carry no scopes and act with the user's workspace access\n\n### RocketReach API (D)\n\nGood for: Teams that already hold a RocketReach plan and want an agent to search people and companies, reveal emails and phones, and verify single addresses over MCP.\n\nAhead on:\n- Reliability, 64 against 45\n- Agent ergonomics, 72 against 66\n\nWatch for: The pricing page is drawn by script and was not read, and the docs tell users without a paid plan to email for an API plan\n\n\n## Score by category\n\n| Category | Weight | Clay | RocketReach API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 64 | RocketReach API +19 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 72 | Clay +12 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 72 | RocketReach API +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 48 | 34 | Clay +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 10 | Clay +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 31 | Clay +44 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 58 | Clay +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.7 · C** | **51.2 · D** | |\n\n## Facts side by side\n\n| Fact | Clay | RocketReach API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Clay Labs Inc. | RocketReach, LLC |\n| Hosted endpoint | `https://api.clay.com/public/v0` | `https://api.rocketreach.co/api/v2` |\n| Transports | HTTP | 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 | Proprietary service under RocketReach's Terms of Service. The Python SDK on GitHub is MIT |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | none |\n| Terms last updated | 2024-05-23 | 2024-01-31 |\n| Privacy policy last updated | 2020-09-11 | 2026-09-30 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | yes | yes |\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 released several times a fortnight, give agents Clay's people search and multi-provider enrichment. Keys have no scopes, the Claude Code plugin auto-approves most CLI calls, and the privacy policy dates from 2020.\n\n**RocketReach API.** The hosted MCP server has nine documented tools, OAuth 2.1 with dynamic client registration and machine-readable error codes, and searches cost no credits. Plan prices were not readable, the docs send API plan requests to email, the terms require a human account holder, and the `account` tool returns the account's API key to the model.\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. Ask the user before enabling the plugin's auto-approve hook in a shared workspace\n\n### RocketReach API\n\n1. Search first with `person_search` or `company_search`, which cost no credits, then look up only the profile IDs needed\n2. Treat `status: \"pending\"` as normal. Poll `check_person_status` after at least 3 seconds, and polling is free\n3. Do not echo the `account` tool's output to users or logs. It includes the account's API key\n4. Send the key in the `Api-Key` header. The `api_key` query parameter is deprecated\n5. Bulk lookup takes 1 to 100 queries and needs a webhook. Results arrive at the webhook, signed in `X-RocketReach-Signature`\n6. Do not loop on `unknown` from `email_verify`, or on `lookup_failed` and `not_found`. The last two are terminal\n\n## Questions\n\n### Which is better for AI agents, Clay or RocketReach API?\n\nClay scores 57.7 (C) on agent readiness against RocketReach API's 51.2 (D), and leads in 5 of 7 scored categories. RocketReach API leads on reliability and agent ergonomics.\n\n### Do Clay and RocketReach API need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Clay and RocketReach API without installing anything?\n\nYes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and RocketReach API at https://api.rocketreach.co/api/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clay-vs-rocketreach.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clay-vs-rocketreach.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clay\", \"b\": \"rocketreach\"}`. From a terminal: `anchor compare clay rocketreach`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clay.json and https://www.anchorterminal.com/api/v1/tools/rocketreach.json\n\n## Other comparisons with Clay or RocketReach API\n\n- [Apollo API + MCP vs Clay](https://www.anchorterminal.com/compare/apollo-vs-clay.md)\n- [Apollo API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/apollo-vs-rocketreach.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 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 ZoomInfo API + MCP](https://www.anchorterminal.com/compare/clay-vs-zoominfo.md)\n- [Coresignal API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/coresignal-vs-rocketreach.md)\n- [Crustdata API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/crustdata-vs-rocketreach.md)\n- [Enrich Layer API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/enrich-layer-vs-rocketreach.md)\n- [Explorium AgentSource vs RocketReach API](https://www.anchorterminal.com/compare/explorium-agentsource-vs-rocketreach.md)\n- [FullEnrich API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/fullenrich-vs-rocketreach.md)\n- [Fuse MCP vs RocketReach API](https://www.anchorterminal.com/compare/fuse-mcp-vs-rocketreach.md)\n- [Gojiberry vs RocketReach API](https://www.anchorterminal.com/compare/gojiberry-vs-rocketreach.md)\n- [LeadMagic API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/leadmagic-vs-rocketreach.md)\n- [Lusha API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/lusha-vs-rocketreach.md)\n- [People Data Labs vs RocketReach API](https://www.anchorterminal.com/compare/people-data-labs-vs-rocketreach.md)\n- [Prospeo API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/prospeo-vs-rocketreach.md)\n- [RocketReach API vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/rocketreach-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- [Clearbit vs RocketReach API](https://www.anchorterminal.com/compare/clearbit-vs-rocketreach.md)\n- [Dropcontact API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/dropcontact-vs-rocketreach.md)\n- [FullContact vs RocketReach API](https://www.anchorterminal.com/compare/fullcontact-vs-rocketreach.md)\n- [Hunter API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/hunter-vs-rocketreach.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-14",
    "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": "Clay vs RocketReach API",
        "url": ""
      }
    ],
    "description": "Clay scores 57.7 (C) to RocketReach's 51.2 (D) for lead search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Clay C 57.7",
      "RocketReach API D 51.2",
      "scores"
    ],
    "h1": "Clay vs RocketReach API",
    "image": "https://www.anchorterminal.com/assets/og/compare-clay-vs-rocketreach.png",
    "path": "/compare/clay-vs-rocketreach",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Clay vs RocketReach for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-14",
    "url": "https://www.anchorterminal.com/compare/clay-vs-rocketreach"
  },
  "tokens": {
    "markdown": 2650,
    "slim": 630
  },
  "version": 1
}
