Head to head · Lead search · October 2026 research run
Enrich Layer API + MCP vs Prospeo API + MCP
Enrich Layer API + MCP scores 61.2 (C) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 3 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics and security & auth. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Teams migrating Proxycurl code or doing per-profile lookups at low unit cost without a subscription.
Ahead on
- Reliability, 77 against 35
- Schema & documentation, 79 against 61
- Maintenance & community, 26 against 19
Also in its favour
- Free to start without a card
Watch for
Person Profile endpoint flagged with performance issues since 24 November 2025, with 30 to 100 second responses
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 68
- Security & auth, 54 against 40
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
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 Enrich Layer API + MCP +42
Enrich Layer API + MCP 77
Cachet status page at status.enrichlayer.com with a component per endpoint under School, Company, People, Contact, Jobs, Search and Meta, plus Web (20). Its daily history, read page by page for 6 August to 4 November 2026, shows no incident on any day. The stickied notice of 24 November 2025, Person Profile answering in 30 to 100 seconds, is still open and that component still showed Performance Issues on 4 November, a partial incident on one endpoint, so minor only (20). The rate-limit guide now gives 900 requests a minute, bursts to 4,500 over 5 minutes, and 2 a minute on trial accounts until the first top-up (15). The guide documents 429 with advice to back off exponentially, and the agents page says to back off and retry on 429 and to retry the same request on 503. That is safe-retry guidance with no Retry-After or idempotency key, on an API where every call is a read (12 of 15). No SLA found (0). Generally available, with a v3 preview for two endpoints alongside (10).
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).
Schema & documentation Enrich Layer API + MCP +18
Enrich Layer API + MCP 79
OpenAPI 3.0 file at enrichlayer.com/docs/api/v2/openapi.yaml, with a JSON twin and x-credits per operation. The MCP repo vendors a 408 kB copy and its CI fails any tool that drifts from it (25). llms.txt and an agents page in Markdown (10). MCP tool descriptions state what each returns, which identifier to pass and the credit cost, but not when to pick one tool over another (14 of 20). Zod schemas with enums for include and exclude flags and cache modes (13 of 15). Examples in the spec, and the agents page lists 401, 403, 404, 429 and 503 with what each means, though no error body schema is given (12 of 15). /api/v2 paths and a v3 preview, no public changelog, MCP versions 0.2.0 and 0.3.0 tagged (5 of 15).
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).
Security & auth Prospeo API + MCP +14
Enrich Layer API + MCP 40
One secret key per user, sent as a bearer token. We found no scopes or key rotation docs. The hosted MCP server takes the same key at an OAuth consent screen (15 of 30). The API only reads, and the MCP marks all 25 tools read-only (18 of 20). Profiles carry free text written by the people they describe, and we found no prompt-injection guidance (2 of 15). A free credit-balance endpoint and nothing more for per-call visibility (5 of 15). No security.txt, disclosure policy, bug bounty or certification. The trust centre covers privacy rights and sub-processors only, and the privacy policy says SOC 2 is under consideration. OSV lists no advisory (0 of 20).
Prospeo API + MCP 54
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. Keys in the X-KEY header, several keys per account. The hosted MCP takes OAuth or the same header (22 of 30). Every tool reads, and the MCP marks them so (16 of 20). Results are structured profile and company fields with little free text (8 of 15). Rate-limit headers, an account endpoint and a free flag on responses that shows whether credits were spent. No per-call log found (8 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). No 2025 or 2026 record in the CVE list names Prospeo. 22 + 16 + 8 + 8 + 0 = 54.
Agent ergonomics Prospeo API + MCP +11
Enrich Layer API + MCP 68
25 MCP tools, all compact, no toolsets. On the API, include and exclude flags on extra fields, contact data and skills let a caller size a profile response (17 of 25). next_token pagination on person and company search and filters (17 of 20). The agents page lists five codes with the action to take (401 check the key, 403 out of credits so stop, 404 move on, 429 back off, 503 retry), and the spec declares 400 to 503 on every operation. Error bodies carry only a status and a message, with no error code of their own or field-level detail, so the line is partly met and keeps its earlier 10 of 20. Every endpoint is a read, and every MCP tool carries readOnlyHint and openWorldHint (16 of 20). Few required parameters, and the official clients found are the MCP package and the enrichlayer-cli package, both Node.js (8 of 15).
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).
Maintenance & community Enrich Layer API + MCP +7
Enrich Layer API + MCP 26
Newest MCP release 0.3.0, tagged on 12 June and published to npm on 19 June 2026 per the 1 October check, 138 days before this check (10). The last commits, on 10 and 11 August 2026, haven't been released. No release or dated changelog entry found from 6 August to 4 November (0). Release dates of the enrichlayer-cli npm package couldn't be read. Four merged pull requests since March 2026 and no public changelog. We couldn't see issue replies from git (8 of 25). Not in the official MCP registry and no official SDKs found (0). CI runs build, tests and an OpenAPI conformance check, and dependencies are recent (8 of 10).
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.
Score by category
| Category | Weight | Enrich Layer API + MCP | Prospeo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 35 | Enrich Layer API + MCP +42 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 61 | Enrich Layer API + MCP +18 |
| Agent ergonomics | 13% | 68 | 79 | Prospeo API + MCP +11 |
| Security & auth | 14% | 40 | 54 | Prospeo API + MCP +14 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 26 | 19 | Enrich Layer API + MCP +7 |
| Transparency & trust | 7% | 59 | 60 | Prospeo API + MCP +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61.2/100 | D 53.6/100 |
Facts side by side
| Fact | Enrich Layer API + MCP | Prospeo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Enrich Layer | Prospeo |
| Hosted endpoint | https://enrichlayer.com/api/v2 | https://api.prospeo.io |
| Transports | HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT | MIT |
| Tools exposed | 25 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | io.prospeo/prospeo-mcp-server |
| Last release | 2026-06-19 | 2026-10-13 |
| Terms last updated | 2025-06-09 | couldn't be read |
| Privacy policy last updated | 2025-06-09 | 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 | not found in the text | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 0 stars, 26 npm/wk | 0 stars, 641 npm/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Prospeo API + MCP higher, the other way from the total score.
| Reviewer | Enrich Layer API + MCP | Prospeo API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 $0.10 or $0.0077 a credit, depending on how you buy | 4/5 $0.0245 an email, and a miss costs nothing |
| WardenSecurity auditor | 3/5 25 read-only tools, SOC 2 under consideration | 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
Enrich Layer API + MCP
Pay-as-you-go credits from $10, non-expiring unless idle for 18 months, with an OpenAPI spec and documented error codes. The Person Profile endpoint has been flagged with 30 to 100 second responses since 24 November 2025, and no security programme or public changelog was found.
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
Enrich Layer API + MCP
- Top up once before testing. Trial keys run at 2 requests a minute
- Set the person profile timeout to at least 100 seconds
- Stop on a 403, which means the account is out of credits, and retry a 503 as is
- Ask for
extra, personal emails or phone numbers only when needed, since each adds credits - Use
callback_urlon slow lookups such as work email instead of holding the connection
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, Enrich Layer API + MCP or Prospeo API + MCP?
Enrich Layer API + MCP scores 61.2 (C) on agent readiness against Prospeo API + MCP's 53.6 (D), and leads in 3 of 7 scored categories. Prospeo API + MCP leads on agent ergonomics and security & auth.
Do Enrich Layer API + MCP and Prospeo API + MCP need an API key?
Enrich Layer API + MCP needs an API key. Prospeo API + MCP takes an API key or an OAuth sign-in.
Can an agent call Enrich Layer API + MCP and Prospeo API + MCP without installing anything?
Yes. Enrich Layer API + MCP has a hosted endpoint at https://enrichlayer.com/api/v2 and Prospeo API + MCP at https://api.prospeo.io.
Other comparisons with Enrich Layer API + MCP or Prospeo API + MCP
- Apollo API + MCP vs Enrich Layer API + MCP
- Apollo API + MCP vs Prospeo API + MCP
- Clay vs Enrich Layer API + MCP
- Clay vs Prospeo API + MCP
- Coresignal API + MCP vs Enrich Layer API + MCP
- Coresignal API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs Prospeo API + MCP
- Dievio vs Enrich Layer API + MCP
- Dievio vs Prospeo API + MCP
- Enrich Layer API + MCP vs Explorium AgentSource
- Enrich Layer API + MCP vs FullEnrich API + MCP
- Enrich Layer API + MCP vs Fuse MCP
- Enrich Layer API + MCP vs Gojiberry
- Enrich Layer API + MCP vs Hunter API + MCP
- Enrich Layer API + MCP vs LeadMagic API + MCP
- Enrich Layer API + MCP vs Lusha API + MCP
- Enrich Layer API + MCP vs People Data Labs
- Enrich Layer API + MCP vs Retriever
- Enrich Layer API + MCP vs RocketReach API
- Enrich Layer API + MCP vs ZoomInfo API + MCP
- Explorium AgentSource vs Prospeo API + MCP
- FullEnrich API + MCP vs Prospeo 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 Enrich Layer API + MCP
- Clearbit vs Prospeo API + MCP
- Databar vs Enrich Layer API + MCP
- Databar vs Prospeo API + MCP
- Dropcontact API + MCP vs Enrich Layer API + MCP
- Dropcontact API + MCP vs Prospeo API + MCP
- Enrich Layer API + MCP vs FullContact
- Enrich Layer API + MCP vs ZeroBounce
- FullContact vs Prospeo API + MCP
- Prospeo API + MCP vs ZeroBounce
- Hunter API + MCP vs Prospeo API + MCP
Machine-readable
- This page as Markdown
/compare/enrich-layer-vs-prospeo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/enrich-layer.json·/api/v1/tools/prospeo.json - From a terminal
anchor compare enrich-layer prospeo(the CLI) - Over MCP
compare_tools {"a": "enrich-layer", "b": "prospeo"}at/mcp, no key