# FullContact vs Retriever (slim)

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

- Full: https://www.anchorterminal.com/compare/fullcontact-vs-retriever.md (~4,550 tokens) · this version ~1,030 tokens · JSON https://www.anchorterminal.com/compare/fullcontact-vs-retriever.json · canonical https://www.anchorterminal.com/compare/fullcontact-vs-retriever
- 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-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

FullContact scores 44.7 (E) on agent readiness against Retriever's 32 (F), and leads in 3 of 7 scored categories. Retriever leads on schema & documentation and payments & pricing. Both do lead enrichment.

- FullContact: E 44.7, rank #1294 of 1557 · https://www.anchorterminal.com/tools/fullcontact.min.md
- Retriever: F 32, rank #1455 of 1557 · https://www.anchorterminal.com/tools/retriever.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. Ahead on Security & auth, 43 against 23; Maintenance & community, 10 against 5; Transparency & trust, 65 against 49. Also No incidents deducted, where Retriever loses 15 points for them.
- Retriever, good for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex. Ahead on Schema & documentation, 82 against 50; Payments & pricing, 30 against 15.

| Category | FullContact | Retriever |
| --- | --- | --- |
| Reliability (16%) | 42 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 50 | 82 |
| Agent ergonomics (13%) | 75 | 75 |
| Security & auth (14%) | 43 | 23 |
| Payments & pricing (10%) | 15 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 5 |
| Transparency & trust (7%) | 65 | 49 |

| Fact (where they differ) | FullContact | Retriever |
| --- | --- | --- |
| Vendor | J2 Martech Corp. (FullContact, a Ziff Davis company) | Retriever |
| Hosted endpoint | `https://api.fullcontact.com/v3` | `https://api.retriever.run/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Licence | Proprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub | none |
| Tools exposed | 1 | 67 |
| Read-only variant documented | no | yes |
| Last release | 2026-04-30 | none |
| Terms last updated | 2025-03-21 | 2026-08-30 |
| Privacy policy last updated | 2026-10-01 | 2026-08-30 |
| 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:
- Schema & documentation, Retriever +32: 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…); Retriever 82 (OpenAPI 3.1 file, version 1.0.0, about 51 paths, linked from llms.txt (25).)
- Security & auth, FullContact +20: FullContact 43 (Per the 14 October check, not re-read on 11 November.); Retriever 23 (The MCP server's OAuth 2.1 issues an ordinary API key, and keys have no scopes or expiry and work as their creator in that organisation: plain revocable keys (2…)
- Transparency & trust, FullContact +16: FullContact 65 (Closed service under Website Terms of Use last updated 21 March 2025 that name J2 Martech Corp., re-read on 11 November (15).); Retriever 49 (Closed source with clear terms, last updated 30 August 2026 (15).)
- Payments & pricing, Retriever +15: FullContact 15 (Per the 14 October check, not re-read on 11 November.); Retriever 30 (No x402, MPP or L402 (0).)
- Maintenance & community, FullContact +5: 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…); Retriever 5 (No changelog, release notes or dated API change found, and the docs carry no dates; the blog's posts are marketing articles, not release notes (0 and 0).)
