# FullContact vs Leadsets (slim)

> Leadsets scores 62.9 (B) to FullContact's 44.7 (E) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.md (~4,850 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/fullcontact-vs-leadsets.json · canonical https://www.anchorterminal.com/compare/fullcontact-vs-leadsets
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-22
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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.

- FullContact: E 44.7, rank #1305 of 1571 · https://www.anchorterminal.com/tools/fullcontact.min.md
- Leadsets: B 62.9, rank #661 of 1571 · https://www.anchorterminal.com/tools/leadsets.min.md
- FullContact, good for Agents that need to turn an email or phone number into a person profile, including consumer demographics and hashed-identifier matching.
- Leadsets, 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 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 Free to start without a card.

| Category | FullContact | Leadsets |
| --- | --- | --- |
| Reliability (16%) | 42 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 58 |
| Agent ergonomics (13%) | 75 | 90 |
| Security & auth (14%) | 43 | 67 |
| Payments & pricing (10%) | 15 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 80 |
| Transparency & trust (7%) | 65 | 67 |

| Fact (where they differ) | FullContact | Leadsets |
| --- | --- | --- |
| 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 |
| Licence | Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub | none |
| Tools exposed | 1 | 8 |
| 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 |
| 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 |

Why the edge:
- 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…); Leadsets 80 (The product is about two weeks old.)
- Payments & pricing, Leadsets +35: FullContact 15 (Per the 14 October check, not re-read on 11 November.); Leadsets 50 (No x402, MPP or L402. An exhausted Free meter answers 402 `free_records_exhausted` with no payment requirements (0).)
- Security & auth, Leadsets +24: FullContact 43 (Per the 14 October check, not re-read on 11 November.); 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…)
- Agent ergonomics, Leadsets +15: FullContact 75 (Per the 14 October check, not re-read on 11 November.); 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 f…)
- 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 re…); 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 sc…)
