Head to head · Lead enrichment · October 2026 research run
FullContact vs Leadsets
Leadsets scores 62.9 (B) on agent readiness against FullContact's 44.7 (E), and leads in 6 of 7 scored categories. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 276 leads comparisons
Which one, for what
Best for Agents that need to turn an email or phone number into a person profile, including consumer demographics and hashed-identifier matching.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public prices. Access starts with a sales conversation
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
- Schema & documentation, 58 against 50
- Agent ergonomics, 90 against 75
- Security & auth, 67 against 43
- Payments & pricing, 50 against 15
- Maintenance & community, 80 against 10
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
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 +70
FullContact 10
The newest dated change to the API is the MCP documentation of 30 April 2026, 195 days before 11 November, and a clone of the Python client stops at a commit of 1 July 2022 with version 4.0.0, its tags at v3.0.2 of 8 June 2021 (0). No dated releases or changelog entries since 13 August (0). Per the 14 October check, a support address and request IDs, with a changelog that stops in 2022 (5 of 15). The Python client hasn't changed since July 2022 and the MCP server isn't in the official registry (3 of 15, the earlier partial kept). No current package or CI to judge (2 of 10, the earlier partial kept). 0 + 0 + 5 + 3 + 2 = 10.
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.
Payments & pricing Leadsets +35
FullContact 15
Per the 14 October check, not re-read on 11 November. No x402, MPP or L402 (0). No prices published, and the pricing page asks visitors to talk to an expert (0). A free Platform account and sandbox keys for evaluation, but whether production lookups need a contract or a card wasn't stated (10 of 20). A person signs up in a browser and generates a key (0). 0 + 0 + 10 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
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.
Security & auth Leadsets +24
FullContact 43
Per the 14 October check, not re-read on 11 November. One Bearer API key per integration, revocable with a rotation procedure, scoped by product entitlement rather than by scope. No OAuth on the MCP server (20). Every call is a read and nothing writes, but there is no read-only key mode beyond entitlements (12 of 20). Responses carry bios and social data from third parties, and no prompt-injection guidance was found (3 of 15). Every MCP response carries a request_id, and no per-call log for the customer was found (3 of 15). The MCP docs say the server runs inside FullContact's SOC 2 boundary, but the security page, dated 1 January 2020, lists no certification or reporting channel, and there is no security.txt (5 of 20). OSV lists no advisory for python-fullcontact on 11 November. 20 + 12 + 3 + 3 + 5 = 43.
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.
Agent ergonomics Leadsets +15
FullContact 75
Per the 14 October check, not re-read on 11 November. One documented tool, so the context cost is small (25). No paging is needed for single lookups, the response is a normalised profile, and Insight Bundles are fixed per account rather than per call (10 of 20). Stable error codes with retryable flags, request IDs and retry_after_seconds, and not_found documented as a normal miss (20). Lookups are safe to retry and misses are billed as calls. The earlier annotation reading came from the struck server request, so the line keeps its earlier partial on the safe-retry docs alone (10 of 20). One identifier is enough, but the Python client was last changed in July 2022 (10 of 15). 25 + 10 + 20 + 10 + 10 = 75.
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 Leadsets +8
FullContact 50
No OpenAPI file for the REST API was found on 14 October, and docs.fullcontact.com/reference returned 404. The typed JSON Schema for the MCP tool came from a request to the server itself, which this benchmark no longer uses, and the docs can't be re-read while the host is paused (0 of 25). Per the 14 October check, not re-read on 11 November, llms.txt and Markdown copies of every page (10), a tool description that says what it does but not when to use it, with docs on which identifier combinations match best (13 of 20), inputs documented by type with no required fields or enums, and the rule that location needs a name only in text (8 of 15), examples for every input combination and an error table with codes, HTTP analogues and a retryable flag (14 of 15), and v3 in the path with a changelog whose newest entries date from 2022 (5 of 15). 0 + 10 + 13 + 8 + 14 + 5 = 50.
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.
Score by category
| Category | Weight | FullContact | Leadsets | Edge |
|---|---|---|---|---|
| Reliability | 16% | 42 | 40 | FullContact +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 50 | 58 | Leadsets +8 |
| Agent ergonomics | 13% | 75 | 90 | Leadsets +15 |
| Security & auth | 14% | 43 | 67 | Leadsets +24 |
| Payments & pricing | 10% | 15 | 50 | Leadsets +35 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 10 | 80 | Leadsets +70 |
| Transparency & trust | 7% | 65 | 67 | Leadsets +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 44.7/100 | B 62.9/100 |
Facts side by side
| Fact | FullContact | Leadsets |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | J2 Martech Corp. (FullContact, a Ziff Davis company) | Leadsets |
| Hosted endpoint | https://api.fullcontact.com/v3 | https://mcp.leadsets.ai |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub | none |
| Tools exposed | 1 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.leadsets/leadsets |
| Last release | 2026-04-30 | 2026-11-22 |
| Terms last updated | 2025-03-21 | 2026-11-15 |
| Privacy policy last updated | 2026-10-01 | 2026-11-19 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
How the scores have moved
Leadsets
No score change since it was listed.
Verdicts
FullContact
FullContact's person.enrich API and its one-tool hosted MCP server document an error model built for agents, with retryable flags, request IDs and retry_after_seconds, and a default limit of 6,000 queries a minute. Prices aren't published, keys have no scopes, no OpenAPI file was found, and the changelog, client libraries and security page are years old.
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
FullContact
- Treat not_found as a normal miss and move on, but note it still counts as a call
- Send email with name and postal address together for better matches
- Honour retry_after_seconds on rate_limit_exceeded and quote request_id to support
- Treat bios and social fields as untrusted text
- Use a key with person.enrich enabled, since the MCP server needs that entitlement
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, FullContact or Leadsets?
Leadsets scores 62.9 (B) on agent readiness against FullContact's 44.7 (E), and leads in 6 of 7 scored categories.
Do FullContact and Leadsets need an API key?
FullContact needs an API key. Leadsets takes an API key or an OAuth sign-in.
Can an agent call FullContact and Leadsets without installing anything?
Yes. FullContact has a hosted endpoint at https://api.fullcontact.com/v3 and Leadsets at https://mcp.leadsets.ai.
Other comparisons with FullContact or Leadsets
- Apollo API + MCP vs Leadsets
- Clay vs Leadsets
- Coresignal API + MCP vs Leadsets
- Crustdata API + MCP vs Leadsets
- Dievio vs Leadsets
- Enrich Layer API + MCP vs Leadsets
- Explorium AgentSource vs Leadsets
- FullEnrich API + MCP vs Leadsets
- 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
- Apollo API + MCP vs FullContact
- Clay vs FullContact
- Clearbit vs FullContact
- Clearbit vs Leadsets
- Coresignal API + MCP vs FullContact
- Crustdata API + MCP vs FullContact
- Databar vs FullContact
- Databar vs Leadsets
- Dievio vs FullContact
- Dropcontact API + MCP vs FullContact
- Dropcontact API + MCP vs Leadsets
- Enrich Layer API + MCP vs FullContact
- Explorium AgentSource vs FullContact
- FullContact vs FullEnrich API + MCP
- FullContact vs Fuse MCP
- FullContact vs Gojiberry
- FullContact vs Hunter API + MCP
- FullContact vs LeadMagic API + MCP
- FullContact vs Lusha API + MCP
- FullContact vs People Data Labs
- FullContact vs Prospeo API + MCP
- FullContact vs Retriever
- FullContact vs RocketReach API
- FullContact vs ZeroBounce
- FullContact vs ZoomInfo API + MCP
- Hunter API + MCP vs Leadsets
- Leadsets vs ZeroBounce
Machine-readable
- This page as Markdown
/compare/fullcontact-vs-leadsets.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fullcontact.json·/api/v1/tools/leadsets.json - From a terminal
anchor compare fullcontact leadsets(the CLI) - Over MCP
compare_tools {"a": "fullcontact", "b": "leadsets"}at/mcp, no key