Head to head · Lead search · October 2026 research run
FullEnrich API + MCP vs Leadsets
FullEnrich API + MCP scores 64.7 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 4 of 7 scored categories. Leadsets leads on agent ergonomics, security & auth and maintenance & community. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 276 leads comparisons
Which one, for what
Best for Maximising find rate on known contacts, especially mobiles, without a long-term contract.
Ahead on
- Reliability, 70 against 40
- Schema & documentation, 76 against 58
- Payments & pricing, 60 against 50
Watch for
Enrichment sources are data providers the vendor doesn't name
Leadsets B
Best 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 57
- Maintenance & community, 80 against 48
Watch for
No status page, SLA or incident history found, and the terms promise no uninterrupted service unless agreed in writing
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Leadsets +32
FullEnrich API + MCP 48
Every dated source of the vendor's own was looked for, in the MCP and skills repository (tags and CHANGELOG), the product changelog (answered 400 on 4 November; newest entry 30 November 2024 per the 1 October check), the docs (no changelog page; the OpenAPI file's Last-Modified date records no listed change). 1.0.4 on 27 August 2026 only links the repository from server.json and corrects the README, a packaging release that counts half and can't set recency. 1.0.2 (10 August) rewrote the full-crm skill's description and steps as well as adding the portable package, and 1.0.3 on 11 August changed skill behaviour (opt-out signals, a confirmation before sequencer changes), so both count in full. The newest of them, 1.0.3, is 85 days back (20). From 6 August, 1.0.2 and 1.0.3 in full and 1.0.4 at half make 2.5, under three (0; was 20). Support by email and help centre (6 of 15). Listed in the official MCP registry as io.github.FullEnrich/fullenrich, a GitHub-verified namespace (15). The skills repo has tests and a version-locked publish workflow (7 of 10). 20+0+6+15+7 = 48.
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.
Reliability FullEnrich API + MCP +30
FullEnrich API + MCP 70
Better Stack status page, but with one component (app.fullenrich.com/app) and none for the API or MCP (15 of 20). Its incident history, read on 4 November month by month from December 2025 to November 2026, says "No incidents reported" for every month, so the page has never posted an incident in the history we read (20, this run's value for a never-posted page; was 15 with the history unread). The monitor bar shows uptime figures of 100 and 99.983 per cent across its 30 to 90 day views, with no incident posted. 60 calls a minute on every endpoint, 100 contacts a bulk and 100 concurrent enrichments per workspace (15). The v2 OpenAPI documents a 429 on six operations with code error.rate.limit and the message "Too many requests. Try again in 1m", and identical re-submissions within 3 months aren't charged again, but there is no safe-retry guidance for writes (10 of 15; was 5). No SLA found (0). Generally available, no beta label on the API or MCP (10). 15+20+15+10+0+10 = 70.
Leadsets 40
No status page found, and the support page answers "Where can I check if Leadsets is down?" by pointing to the 503 error and support email (0). No incident history to read (5). Limits published with numbers per plan, per rolling five hours and per week, for records, requests and concurrent searches (15). Three 429 types with Retry-After, backoff advice for 500 and 503, and an Idempotency-Key on paid calls that makes retries safe for 24 hours (15). The terms say "We aim for high availability but don't guarantee uninterrupted service unless agreed in writing", and no SLA is published (0). No page calls the service beta or preview, but the changelog says "No releases yet. Release notes start at launch.", so half credit as a judgement call (5). 0 + 5 + 15 + 15 + 0 + 5 = 40.
Agent ergonomics Leadsets +24
FullEnrich API + MCP 66
13 MCP tools with short descriptions. Search returns a free preview of 10 results plus a count, and bulk output goes to CSV or JSON exports rather than the chat (17 of 25). Structured filters for people and companies, single-record lookups and export endpoints (16 of 20). The OpenAPI file documents error codes per operation, 20 named codes in all, for missing fields, an enrichment still in progress, unknown keys and the rate limit, which an agent can act on (14 of 20; was 8). Asynchronous enrichment with polling or a signed webhook, identical inputs within 3 months return without a new charge, and the MCP guide asks for a balance check and confirmation before paid steps. No tool annotations confirmed (12 of 20). No official SDKs found (7 of 15). 17+16+14+12+7 = 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.
Schema & documentation FullEnrich API + MCP +18
FullEnrich API + MCP 76
OpenAPI file for v2 at docs.fullenrich.com/api/v2/reference/openapi.yaml (version 2.0.0, eight paths, Last-Modified 3 November 2026), with a v1 file alongside (25). llms.txt with 34 links and Markdown twins (10). The MCP keeps tool descriptions short on purpose and moves workflow guidance into separate skills, so a client without skills gets less of it (12 of 20). Typed inputs, with helper tools that list valid industry, seniority and function codes (12 of 15). Test contacts that cost 0 credits and signed webhook examples. The OpenAPI file gives 400, 401, 402, 404 and 429 responses with a code and message schema and named examples such as error.enrichment.first_name.empty and error.rate.limit, though the docs have no separate error page (12 of 15; was 8, the 1 October check found no error reference). v1 and v2 paths. The public product changelog stopped at 30 November 2024 per the 1 October check and answered 400 "Invalid page" on 4 November, and only the MCP package has a current CHANGELOG (5 of 15). 25+10+12+12+12+5 = 76.
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.
Security & auth Leadsets +10
FullEnrich API + MCP 57
Bearer API key for REST, no scopes found. The MCP signs in with OAuth and holds no static secret in the client. Webhooks are signed with HMAC-SHA1 keyed with the API key itself (20 of 30). The MCP isn't read-only, and confirmation before enrichment is recommended but left to the client. Workspace admins can set monthly credit limits per member, which block further credit-consuming MCP actions, and the skills add a confirmation before any sequencer change and honour opt-out and do-not-contact signals (10 of 20). Results are mostly structured contact fields (8 of 15). A free credits endpoint, and per-member usage views that include MCP activity, no per-call log found (7 of 15; was 5, aligned with people-data-labs' usage view). SOC 2 Type 2 per the trust page, with the report on request, vulnerability reports to support@fullenrich.com per the repository's SECURITY.md, security.txt 404 on 4 November, no bug bounty (12 of 20, as people-data-labs). 20+10+8+7+12 = 57.
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.
Payments & pricing FullEnrich API + MCP +10
FullEnrich API + MCP 60
No x402, MPP or L402 (0). Per-unit credit costs and plan prices are public, on the pricing page and its Markdown twin, 1 credit a work email, 3 a personal email, 10 a mobile, 0.25 a search result, Pro from $29 a month for 500 credits ($55 for 1,000) (20). 50 trial credits with no card, API and MCP included (20). A person signs up in a browser (0). 0+20+20+0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
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.
Score by category
| Category | Weight | FullEnrich API + MCP | Leadsets | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 40 | FullEnrich API + MCP +30 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 58 | FullEnrich API + MCP +18 |
| Agent ergonomics | 13% | 66 | 90 | Leadsets +24 |
| Security & auth | 14% | 57 | 67 | Leadsets +10 |
| Payments & pricing | 10% | 60 | 50 | FullEnrich API + MCP +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 80 | Leadsets +32 |
| Transparency & trust | 7% | 68 | 67 | FullEnrich API + MCP +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.7/100 | B 62.9/100 |
Facts side by side
| Fact | FullEnrich API + MCP | Leadsets |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | FullEnrich | Leadsets |
| Hosted endpoint | https://app.fullenrich.com/api/v2 | https://mcp.leadsets.ai |
| Transports | HTTP, Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Tools exposed | 13 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.FullEnrich/fullenrich | io.github.leadsets/leadsets |
| Last release | 2026-08-27 | 2026-11-22 |
| Terms last updated | 2026-08-20 | 2026-11-15 |
| Privacy policy last updated | 2026-08-20 | 2026-11-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 3.5/5 (2) | none |
How the scores have moved
Verdicts
FullEnrich API + MCP
Credits are spent only on found data, identical re-runs within 3 months are free, and the v2 OpenAPI documents error codes per operation. The status page covers only the web app, no MCP release since 27 August changed more than packaging, and the enrichment data providers aren't named.
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
FullEnrich API + MCP
- Send identical names, domains and LinkedIn URLs when re-running, or deduplication misses and you pay again
- Expect 30 to 90 seconds a contact. Use the webhook or poll
get_enrichment_results - Ask for mobiles only when needed. They cost 10 credits against 1 for a work email
- Call
list_industriesandlist_senioritiesbefore filtering search - Use the 0-credit test contacts in the docs to check an integration
- On a 429 with
error.rate.limit, wait a minute before retrying. The limit is 60 calls a minute on every endpoint
Leadsets
- Call get_usage before a large run. It costs nothing and returns every meter with its reset time
- Send an
Idempotency-Keyon every paid call, and reuse it on a retry so records are counted once - If a 429 has type
weekly_limit, stop untilresets_at. Forwindow_fullandtoo_many_concurrent, wait for Retry-After - Use a read-level key for monitoring only. Data tools answer 403
forbiddento it - 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, FullEnrich API + MCP or Leadsets?
FullEnrich API + MCP scores 64.7 (B) on agent readiness against Leadsets's 62.9 (B), and leads in 4 of 7 scored categories. Leadsets leads on agent ergonomics, security & auth and maintenance & community.
Do FullEnrich API + MCP and Leadsets need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call FullEnrich API + MCP and Leadsets without installing anything?
Yes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and Leadsets at https://mcp.leadsets.ai.
Other comparisons with FullEnrich API + MCP or Leadsets
- Apollo API + MCP vs FullEnrich API + MCP
- Apollo API + MCP vs Leadsets
- Clay vs FullEnrich API + MCP
- Clay vs Leadsets
- Coresignal API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs Leadsets
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Leadsets
- Dievio vs FullEnrich API + MCP
- Dievio vs Leadsets
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Leadsets
- Explorium AgentSource vs FullEnrich API + MCP
- Explorium AgentSource vs Leadsets
- FullEnrich API + MCP vs Fuse MCP
- FullEnrich API + MCP vs Gojiberry
- FullEnrich API + MCP vs Hunter API + MCP
- FullEnrich API + MCP vs LeadMagic API + MCP
- FullEnrich API + MCP vs Lusha API + MCP
- FullEnrich API + MCP vs People Data Labs
- FullEnrich API + MCP vs Prospeo API + MCP
- FullEnrich API + MCP vs Retriever
- FullEnrich API + MCP vs RocketReach API
- FullEnrich API + MCP vs ZoomInfo API + MCP
- Fuse MCP vs Leadsets
- Gojiberry vs Leadsets
- LeadMagic API + MCP vs Leadsets
- Leadsets vs Lusha API + MCP
- Leadsets vs People Data Labs
- Leadsets vs Prospeo API + MCP
- Leadsets vs Retriever
- Leadsets vs RocketReach API
- Leadsets vs ZoomInfo API + MCP
- Clearbit vs FullEnrich API + MCP
- Clearbit vs Leadsets
- Databar vs FullEnrich API + MCP
- Databar vs Leadsets
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs Leadsets
- FullContact vs FullEnrich API + MCP
- FullContact vs Leadsets
- FullEnrich API + MCP vs ZeroBounce
- Hunter API + MCP vs Leadsets
- Leadsets vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/fullenrich-vs-leadsets.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fullenrich.json·/api/v1/tools/leadsets.json - From a terminal
anchor compare fullenrich leadsets(the CLI) - Over MCP
compare_tools {"a": "fullenrich", "b": "leadsets"}at/mcp, no key