Head to head · Lead search · October 2026 research run
FullEnrich API + MCP vs Prospeo API + MCP
FullEnrich API + MCP scores 64.7 (B) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 5 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 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 35
- Schema & documentation, 76 against 61
- Maintenance & community, 48 against 19
- Transparency & trust, 68 against 60
Also in its favour
- Free to start without a card
Watch for
Enrichment sources are data providers the vendor doesn't name
Best for An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.
Ahead on
- Agent ergonomics, 79 against 66
Also in its favour
- Runs on your own machine
Watch for
No status page, SLA or changelog
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.
Reliability FullEnrich API + MCP +35
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.
Prospeo API + MCP 35
Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No status page found, and status.prospeo.io doesn't resolve in DNS as of 2 October (0). No incident history to read (5). Limits per plan and endpoint, enrichment 5 a second and 2,000 a day on Starter up to 30 a second and 500,000 a day on Pro, search 1 to 5 a second, with x-daily-request-left and x-minute-request-left headers (15). 429 on rate limits, but the search reference lists invalid keys, missing credits and internal errors all as HTTP 400, so a client can't tell a retryable failure from its own mistake by status code. No Retry-After or back-off guidance found (5 of 15). No SLA found (0). Generally available (10).
Maintenance & community FullEnrich API + MCP +29
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.
Prospeo API + MCP 19
The MCP repository, read from a clone, has 1.1.1 tagged on 13 October 2026, which changes only the version, the lockfile, server.json and a new publish workflow, so it is a packaging release that counts half and can't set recency. Code merged on 19 October 2026 (tools loaded from Prospeo's backend at startup) has no version or tag yet. The newest release that changes code is 1.1.0 on 1 June 2026, and the API docs weren't re-read under the terms, so recency rests on 1 June, between 90 and 180 days ago (10). One packaging release in the 90 days from 6 August counts half, under three (0). No changelog, and the MCP repo's commits are all from staff. We couldn't see issue handling from git (5 of 25). server.json names io.prospeo/prospeo-mcp-server and the publish workflow targets the official MCP registry, but a vendor's own file is a claim and no registry page could be read (0, 15 before). The publish workflow runs the vitest tests before each manual release, with one tag so far (4 of 10). 10 + 0 + 5 + 0 + 4 = 19.
Schema & documentation FullEnrich API + MCP +15
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.
Prospeo API + MCP 61
Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. No OpenAPI file for the REST API. The MCP tools carry full JSON Schema inputs generated from zod (15 of 25). No llms.txt found (0). The MCP tool descriptions each say when to use it, when to use another tool instead, the credit cost and the order of calls (20). Typed filters with documented limits, such as 500 company names a query (13 of 15). Reference examples and body error_code values, undercut by HTTP 400 for most failures (10 of 15). No changelog or versioning. The docs carry 'last updated 11 June 2026' (3 of 15).
Agent ergonomics Prospeo API + MCP +13
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.
Prospeo API + MCP 79
Per the 1 and 2 October checks, not re-read on 4 November 2026, because Prospeo's terms bar robots and other automated means outside its documented public API. 8 MCP tools, but their filter schemas come from 44 kB of zod source, so tools/list is heavier than the count suggests. Bulk enrichment returns a compact record per person (20 of 25). 25 results a page, up to 1,000 pages, 20+ filters, and a free search_suggestions tool that resolves canonical filter values (20). Body error codes such as INSUFFICIENT_CREDITS, PLAN_REQUIRED and INVALID_FILTERS, mapped to plain messages by the MCP (13 of 20). Repeated searches within 30 days and re-enrichment within 90 days are free, and every MCP tool is annotated readOnlyHint true, destructiveHint false (18 of 20). At least one include filter is required. The MCP package is the only official client (8 of 15).
Transparency & trust FullEnrich API + MCP +8
FullEnrich API + MCP 68
Closed service with terms naming FullEnrich Corp. The skills and registry repo is MIT (15). The privacy policy (updated 20 August 2026, per the 1 October check) gives retention periods (3 years from last contact for prospects, 25 months for service improvement), legal bases and SCC or DPF transfers, and points rights requests to support@fullenrich.com. It doesn't say whether people returned by enrichment are covered, and the trust page says enrichment uses data providers it doesn't name, most acting as independent controllers. An opt-out page exists at fullenrich.com/optout (18 of 30). v1 and v2 APIs run side by side with no dated deprecation found (3 of 20). A sub-processor list is published, and the trust page now states that the hosting provider, DigitalOcean, hosts data in the European Union, with transfers outside the EEA disclosed (20 of 20; was 14 with hosting locations not stated). 15+18+3+20 = 56.
Prospeo API + MCP 60
The MCP server is MIT. The API is closed, run by Defastra Tech Inc. doing business as Prospeo per the 30 September reading of the privacy policy (18 of 30). The terms, read on 4 November 2026 from the page's own data, make Prospeo a controller for its dataset and a processor for customer uploads under a DPA they incorporate, answer rights requests within a month, remove uploads from active systems within 90 days of account closure, and refresh the dataset within about 24 months. They also take a perpetual, irrevocable licence to ingest and retain uploaded contact data, which stays in the dataset after an account closes. The privacy policy and DPA weren't re-read (18 of 30). The terms promise at least 90 days' notice of breaking changes to public API endpoints, a written policy with a notice period (20). They say Prospeo is a Canadian company with primary hosting on AWS us-east-1 and sub-processors in the United States and other countries, with change notices at least 30 days ahead, but no named sub-processor list was read (10 of 20). 18 + 18 + 20 + 10 = 66.
Score by category
| Category | Weight | FullEnrich API + MCP | Prospeo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 35 | FullEnrich API + MCP +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 76 | 61 | FullEnrich API + MCP +15 |
| Agent ergonomics | 13% | 66 | 79 | Prospeo API + MCP +13 |
| Security & auth | 14% | 57 | 54 | FullEnrich API + MCP +3 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 48 | 19 | FullEnrich API + MCP +29 |
| Transparency & trust | 7% | 68 | 60 | FullEnrich API + MCP +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.7/100 | D 53.6/100 |
Facts side by side
| Fact | FullEnrich API + MCP | Prospeo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | FullEnrich | Prospeo |
| Hosted endpoint | https://app.fullenrich.com/api/v2 | https://api.prospeo.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 13 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | io.github.FullEnrich/fullenrich | io.prospeo/prospeo-mcp-server |
| Last release | 2026-08-27 | 2026-10-13 |
| Terms last updated | 2026-08-20 | couldn't be read |
| Privacy policy last updated | 2026-08-20 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | none | 0 stars, 641 npm/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | FullEnrich API + MCP | Prospeo API + MCP |
|---|---|---|
| LedgerCost analyst | 4/5 Charged on found data only, $0.055 a credit | 4/5 $0.0245 an email, and a miss costs nothing |
| WardenSecurity auditor | 3/5 Webhooks signed with the API key itself | 3/5 Eight read-only tools and a perpetual licence |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
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.
Prospeo API + MCP
MCP tool descriptions say when to use each tool, its credit cost and the next call, and the terms promise 90 days' notice of breaking API changes. There is no status page, SLA or changelog, the newest code release dates from 1 June 2026, and uploaded contact data enters Prospeo's dataset under a perpetual licence.
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
Prospeo API + MCP
- Call
search_suggestionsbefore using location, technology or industry filters, or the search returns nothing - Pass
person_idvalues from search intobulk_enrich_person, 25 at a time - Branch on the body
error_code, not the HTTP status, which is 400 for most failures - Set
enrich_mobileonly when needed. A mobile costs 10 credits against 1 for an email - Use Enrich Person. The old Email Finder endpoint was removed in March 2026
Questions
Which is better for AI agents, FullEnrich API + MCP or Prospeo API + MCP?
FullEnrich API + MCP scores 64.7 (B) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 5 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics.
Do FullEnrich API + MCP and Prospeo API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call FullEnrich API + MCP and Prospeo API + MCP without installing anything?
Yes. FullEnrich API + MCP has a hosted endpoint at https://app.fullenrich.com/api/v2 and Prospeo API + MCP at https://api.prospeo.io.
Other comparisons with FullEnrich API + MCP or Prospeo API + MCP
- Apollo API + MCP vs FullEnrich API + MCP
- Apollo API + MCP vs Prospeo API + MCP
- Clay vs FullEnrich API + MCP
- Clay vs Prospeo API + MCP
- Coresignal API + MCP vs FullEnrich API + MCP
- Coresignal API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Prospeo API + MCP
- Dievio vs FullEnrich API + MCP
- Dievio vs Prospeo API + MCP
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Prospeo API + MCP
- Explorium AgentSource vs FullEnrich API + MCP
- Explorium AgentSource vs Prospeo API + MCP
- 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 Retriever
- FullEnrich API + MCP vs RocketReach API
- FullEnrich API + MCP vs ZoomInfo API + MCP
- Fuse MCP vs Prospeo API + MCP
- Gojiberry vs Prospeo API + MCP
- LeadMagic API + MCP vs Prospeo API + MCP
- Lusha API + MCP vs Prospeo API + MCP
- People Data Labs vs Prospeo API + MCP
- Prospeo API + MCP vs Retriever
- Prospeo API + MCP vs RocketReach API
- Prospeo API + MCP vs ZoomInfo API + MCP
- Clearbit vs FullEnrich API + MCP
- Clearbit vs Prospeo API + MCP
- Databar vs FullEnrich API + MCP
- Databar vs Prospeo API + MCP
- Dropcontact API + MCP vs FullEnrich API + MCP
- Dropcontact API + MCP vs Prospeo API + MCP
- FullContact vs FullEnrich API + MCP
- FullContact vs Prospeo API + MCP
- FullEnrich API + MCP vs ZeroBounce
- Prospeo API + MCP vs ZeroBounce
- Hunter API + MCP vs Prospeo API + MCP
Machine-readable
- This page as Markdown
/compare/fullenrich-vs-prospeo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fullenrich.json·/api/v1/tools/prospeo.json - From a terminal
anchor compare fullenrich prospeo(the CLI) - Over MCP
compare_tools {"a": "fullenrich", "b": "prospeo"}at/mcp, no key