# Clay vs Leadsets

> Leadsets scores 62.9 (B) to Clay's 58.3 (C) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/clay-vs-leadsets
- Markdown: https://www.anchorterminal.com/compare/clay-vs-leadsets.md (~5,150 tokens)
- Slim: https://www.anchorterminal.com/compare/clay-vs-leadsets.min.md (~1,080 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/clay-vs-leadsets.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-22

Leadsets scores 62.9 (B) on agent readiness against Clay's 58.3 (C), and leads in 5 of 7 scored categories. Clay leads on schema & documentation. Both do lead search.

- Clay: grade C, 58.3/100, rank #862 of 1571. Markdown https://www.anchorterminal.com/tools/clay.md · JSON https://www.anchorterminal.com/api/v1/tools/clay.json
- Leadsets: grade B, 62.9/100, rank #661 of 1571. Markdown https://www.anchorterminal.com/tools/leadsets.md · JSON https://www.anchorterminal.com/api/v1/tools/leadsets.json
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 276 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### Clay (C)

Good for: Agents building prospect lists and enriching contacts or accounts through many providers at once.

Ahead on:
- Schema & documentation, 84 against 58

Watch for: API keys carry no scopes and act with the user's workspace access

### Leadsets (B)

Good for: Prospect search, contact enrichment with verified work emails and company-site scraping for an agent on a flat monthly plan rather than credits.

Ahead on:
- Agent ergonomics, 90 against 66
- Security & auth, 67 against 48
- Payments & pricing, 50 against 45
- Maintenance & community, 80 against 75
- Transparency & trust, 67 against 61

Also in its favour:
- Free to start without a card

Watch for: No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing


## Why the edge

### Schema & documentation: Clay +26

- Clay (84): A public OpenAPI 3 spec, per the 14 October check (25). llms.txt and Markdown copies of every page, re-read on 4 November, with 18 API reference pages now that Audiences privacy deletion and its status call were added in the week of 26 October (10). Pages say when to use each primitive, and deprecated filters-mode endpoints name their replacement (16 of 20). Typed request bodies, with a query grammar fetched from a reference endpoint rather than enums (12 of 15). curl examples on every guide, but error bodies carry only a message, and the errors page says they don't include stable codes (9 of 15). v0 in the path and a weekly product changelog that names CLI, MCP and API changes, without an API-specific log (12 of 15). 25 + 10 + 16 + 12 + 9 + 12 = 84.
- Leadsets (58): No OpenAPI file or other machine-readable contract found in the docs or llms.txt, and the MCP server answers `initialize` with 401 without a key, so its tool schemas couldn't be read (0). llms.txt, llms-full.txt and a Markdown twin of every page (10). The REST reference says what each route does, what it costs and what it returns, with little on when not to use it, and the MCP definitions are unread (12 of 20). People search inputs are typed with enums for seniority and function, ranges for `limit` (1 to 100) and `max_age_days`, ISO country codes and booleans, with one nested `priorities` object (13 of 15). cURL, TypeScript and Python examples and a documented response, plus an errors page that lists 11 types with what to do (15). /v1 in the path and a dated, semver CHANGELOG.md for the TypeScript SDK, but the API changelog had no entries on 22 November 2026 (8 of 15). 0 + 10 + 12 + 13 + 15 + 8 = 58.

### Agent ergonomics: Leadsets +24

- 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.
- Leadsets (90): Eight MCP tools per the docs, with sizes unread, and REST responses sized by `limit` and a `count_only` mode that returns only a count, but no field selection found (20 of 25). Cursor pagination, typed filters, `max_age_days`, `exclude_stale` and `has_verified_email` (20). Every error has a status, a `type`, a `request_id`, the meter and `charged`, and the docs say whether to retry each one (20). `Idempotency-Key` on every paid call for 24 hours, with 409 `idempotency_conflict` for a reused key with a new body. MCP tool annotations couldn't be read (15 of 20). One required header and defaults such as `limit` 25, and official TypeScript and Python SDKs that retry 429 and 5xx (15). 20 + 20 + 20 + 15 + 15 = 90.

### Security & auth: Leadsets +19

- 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.
- Leadsets (67): Bearer keys with a full, data or read access level, an expiry of never, 30, 90 or 365 days, hashed storage, revocation within a minute and a documented rotation procedure. MCP clients can use OAuth with PKCE S256 and dynamic client registration, with no scopes in the server metadata. No query-string key documented (30). A read-level key can call only the usage endpoints, and every data tool reads rather than writes, so there is nothing destructive to confirm. Members see and revoke only their own keys (16 of 20). scrape_company and scrape_jobs return text from company websites, and no prompt-injection guidance was found (3 of 15). A request log in the dashboard, an optional `X-Leadsets-Client` label, rate-limit headers and `request_id` on every response (12 of 15). /.well-known/security.txt answered 404. The SDK repository's SECURITY.md names security@leadsets.ai with acknowledgement within 3 business days. No bug bounty, and SOC 2 Type I readiness has a target of Q3 2027 (6 of 20). 30 + 16 + 3 + 12 + 6 = 67.

### Transparency & trust: Leadsets +6

- 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.
- Leadsets (67): Closed service with terms naming Mobylogix LLC under Texas law. The SDK is MIT (15). The privacy policy, terms, DPA and compliance page say where dataset records come from (licensed suppliers and permitted public sources such as company websites), what is held, that uploaded files are deleted 30 days after a job, and how to opt out. The suppliers aren't named, and the privacy policy says analytics run only on the public website while the compliance page lists PostHog and Google Analytics as "Product analytics (customers only)" (20 of 30). Breaking changes get 90 days' notice by email and material changes to plans or terms 30 days, with no dated notices yet (15 of 20). Subprocessors named (Vercel, Supabase, Stripe, Resend, PostHog, Google Analytics), all in the US, with 30 days' notice before adding one (18 of 20). 15 + 20 + 15 + 18 = 68.

### Payments & pricing: Leadsets +5

- 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.
- Leadsets (50): No x402, MPP or L402. An exhausted Free meter answers 402 `free_records_exhausted` with no payment requirements (0). Plan prices and their per-window limits are public, with no per-record price, and scraping units are priced per pack ($9 for 1,000, $19 for 5,000, $49 for 20,000), so plan-only pricing with a per-unit add-on (20 of 30). Free plan of 1,000 enrichment records, 100 search records and 1,000 data calls, one time, "no card required" (30). A person signs up in a browser and makes the key in the dashboard (0). 0 + 20 + 30 + 0 = 50.

### Maintenance & community: Leadsets +5

- 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.
- Leadsets (80): The product is about two weeks old. The TypeScript SDK 0.2.1 was tagged on 22 November 2026, the day of this check (30). Four SDK tags (0.1.0 and 0.1.1 on 11 November, 0.2.0 on 19 November, 0.2.1 on 22 November) and four PyPI releases from 11 to 19 November, all within 90 days (20). A support email with response times by plan and an API changelog with no entries yet. GitHub issues weren't read (7 of 25). In the official MCP registry as io.github.leadsets/leadsets since 14 November 2026, under a namespace proved through GitHub, and current official SDKs in two languages (15). The SDK has no runtime dependencies, CI on Node 20, 22 and 24, and npm trusted publishing with provenance, and the CI run results weren't read (8 of 10). 30 + 20 + 7 + 15 + 8 = 80.

## Score by category

| Category | Weight | Clay | Leadsets | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 40 | 40 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 58 | Clay +26 |
| Agent ergonomics | 13% | 66 | 90 | Leadsets +24 |
| Security & auth | 14% | 48 | 67 | Leadsets +19 |
| Payments & pricing | 10% | 45 | 50 | Leadsets +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 75 | 80 | Leadsets +5 |
| Transparency & trust | 7% | 61 | 67 | Leadsets +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **58.3 · C** | **62.9 · B** | |

## Facts side by side

| Fact | Clay | Leadsets |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Clay Labs Inc. | Leadsets |
| Hosted endpoint | `https://api.clay.com/public/v0` | `https://mcp.leadsets.ai` |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Clay Terms of Service. The agent plugin repository carries no licence file | none |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.leadsets/leadsets` |
| Last release | 2026-11-04 | 2026-11-22 |
| Terms last updated | not read yet | 2026-11-15 |
| Privacy policy last updated | 2020-09-11 | 2026-11-19 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |

## How the scores have moved

### Clay

- +1.9 on 13 November 2026: checklist
- -1.3 on 4 November 2026: terms

### Leadsets

No score change since it was listed.

## 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.

**Leadsets.** Agents get eight MCP tools or REST routes with typed errors that say whether to retry, idempotency keys on paid calls, read-only keys and a free tier with no card. The product is about two weeks old, with no status page, no OpenAPI file, an empty API changelog and no named data suppliers.

## Before you call either

### Clay

1. Fetch GET /search/query-mode/reference before writing a search query
2. Poll routine results until a terminal 200, since 202 means still running
3. Expect HTTP 402 when a plan's search cap is hit, and tell the user the reset date
4. Check GET /credits/balance before large batch runs
5. When a CLI command answers approval_required, tell the user what it would do and let them approve or deny it
6. Ask the user before enabling the plugin's auto-approve hook in a shared workspace

### Leadsets

1. Call get_usage before a large run. It costs nothing and returns every meter with its reset time
2. Send an `Idempotency-Key` on every paid call, and reuse it on a retry so records are counted once
3. If a 429 has type `weekly_limit`, stop until `resets_at`. For `window_full` and `too_many_concurrent`, wait for Retry-After
4. Use a read-level key for monitoring only. Data tools answer 403 `forbidden` to it
5. Treat text from scrape_company and scrape_jobs as untrusted website content, since no injection guidance was found

## Questions

### Which is better for AI agents, Clay or Leadsets?

Leadsets scores 62.9 (B) on agent readiness against Clay's 58.3 (C), and leads in 5 of 7 scored categories. Clay leads on schema & documentation.

### Do Clay and Leadsets need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Clay and Leadsets without installing anything?

Yes. Clay has a hosted endpoint at https://api.clay.com/public/v0 and Leadsets at https://mcp.leadsets.ai.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/clay-vs-leadsets.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clay-vs-leadsets.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "clay", "b": "leadsets"}`. From a terminal: `anchor compare clay leadsets`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clay.json and https://www.anchorterminal.com/api/v1/tools/leadsets.json

## Other comparisons with Clay or Leadsets

- [Apollo API + MCP vs Clay](https://www.anchorterminal.com/compare/apollo-vs-clay.md)
- [Apollo API + MCP vs Leadsets](https://www.anchorterminal.com/compare/apollo-vs-leadsets.md)
- [Clay vs Coresignal API + MCP](https://www.anchorterminal.com/compare/clay-vs-coresignal.md)
- [Clay vs Crustdata API + MCP](https://www.anchorterminal.com/compare/clay-vs-crustdata.md)
- [Clay vs Databar](https://www.anchorterminal.com/compare/clay-vs-databar.md)
- [Clay vs Dievio](https://www.anchorterminal.com/compare/clay-vs-dievio.md)
- [Clay vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/clay-vs-enrich-layer.md)
- [Clay vs Explorium AgentSource](https://www.anchorterminal.com/compare/clay-vs-explorium-agentsource.md)
- [Clay vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/clay-vs-fullenrich.md)
- [Clay vs Fuse MCP](https://www.anchorterminal.com/compare/clay-vs-fuse-mcp.md)
- [Clay vs Gojiberry](https://www.anchorterminal.com/compare/clay-vs-gojiberry.md)
- [Clay vs Hunter API + MCP](https://www.anchorterminal.com/compare/clay-vs-hunter.md)
- [Clay vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/clay-vs-leadmagic.md)
- [Clay vs Lusha API + MCP](https://www.anchorterminal.com/compare/clay-vs-lusha.md)
- [Clay vs People Data Labs](https://www.anchorterminal.com/compare/clay-vs-people-data-labs.md)
- [Clay vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clay-vs-prospeo.md)
- [Clay vs Retriever](https://www.anchorterminal.com/compare/clay-vs-retriever.md)
- [Clay vs RocketReach API](https://www.anchorterminal.com/compare/clay-vs-rocketreach.md)
- [Clay vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/clay-vs-zoominfo.md)
- [Coresignal API + MCP vs Leadsets](https://www.anchorterminal.com/compare/coresignal-vs-leadsets.md)
- [Crustdata API + MCP vs Leadsets](https://www.anchorterminal.com/compare/crustdata-vs-leadsets.md)
- [Dievio vs Leadsets](https://www.anchorterminal.com/compare/dievio-vs-leadsets.md)
- [Enrich Layer API + MCP vs Leadsets](https://www.anchorterminal.com/compare/enrich-layer-vs-leadsets.md)
- [Explorium AgentSource vs Leadsets](https://www.anchorterminal.com/compare/explorium-agentsource-vs-leadsets.md)
- [FullEnrich API + MCP vs Leadsets](https://www.anchorterminal.com/compare/fullenrich-vs-leadsets.md)
- [Fuse MCP vs Leadsets](https://www.anchorterminal.com/compare/fuse-mcp-vs-leadsets.md)
- [Gojiberry vs Leadsets](https://www.anchorterminal.com/compare/gojiberry-vs-leadsets.md)
- [LeadMagic API + MCP vs Leadsets](https://www.anchorterminal.com/compare/leadmagic-vs-leadsets.md)
- [Leadsets vs Lusha API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-lusha.md)
- [Leadsets vs People Data Labs](https://www.anchorterminal.com/compare/leadsets-vs-people-data-labs.md)
- [Leadsets vs Prospeo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-prospeo.md)
- [Leadsets vs Retriever](https://www.anchorterminal.com/compare/leadsets-vs-retriever.md)
- [Leadsets vs RocketReach API](https://www.anchorterminal.com/compare/leadsets-vs-rocketreach.md)
- [Leadsets vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/leadsets-vs-zoominfo.md)
- [Clay vs Clearbit](https://www.anchorterminal.com/compare/clay-vs-clearbit.md)
- [Clay vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/clay-vs-dropcontact.md)
- [Clay vs FullContact](https://www.anchorterminal.com/compare/clay-vs-fullcontact.md)
- [Clay vs ZeroBounce](https://www.anchorterminal.com/compare/clay-vs-zerobounce.md)
- [Clearbit vs Leadsets](https://www.anchorterminal.com/compare/clearbit-vs-leadsets.md)
- [Databar vs Leadsets](https://www.anchorterminal.com/compare/databar-vs-leadsets.md)
- [Dropcontact API + MCP vs Leadsets](https://www.anchorterminal.com/compare/dropcontact-vs-leadsets.md)
- [FullContact vs Leadsets](https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.md)
- [Hunter API + MCP vs Leadsets](https://www.anchorterminal.com/compare/hunter-vs-leadsets.md)
- [Leadsets vs ZeroBounce](https://www.anchorterminal.com/compare/leadsets-vs-zerobounce.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
