Head to head · Lead search · October 2026 research run
Crustdata API + MCP vs Prospeo API + MCP
Prospeo API + MCP scores 53.6 (D) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 3 of 7 scored categories. Crustdata API + MCP leads on reliability, schema & documentation and maintenance & community. Both do lead search.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Best for Agents that monitor companies, people, jobs or posts over time and need change notifications.
Ahead on
- Reliability, 42 against 35
- Schema & documentation, 89 against 61
- Maintenance & community, 57 against 19
Watch for
No status page and no SLA
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 73
- Payments & pricing, 60 against 8
Also in its favour
- Runs on your own machine
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
- No incidents deducted, where Crustdata API + MCP loses 3 points for them
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.
Payments & pricing Prospeo API + MCP +52
Crustdata API + MCP 8
No x402, MPP or L402 (0). Credit costs per endpoint and field are public, but no dollar price per credit is, and enterprise plans start at "four figures a month" through sales. We gave 5 rather than 0 because an agent can work out relative cost from the public credit table (5). Every new self-serve account now starts with $20 in free credits, but no page we read says whether signing up needs a card, so the line isn't met on the evidence (0). A person signs up in the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.
Prospeo API + MCP 60
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 x402, MPP or L402 (0). Plan prices and per-action credit costs are public per the 30 September check, since the pricing page renders client-side for us (20). Free plan with 100 credits a month, and the docs say API access is free for all users (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Maintenance & community Crustdata API + MCP +38
Crustdata API + MCP 57
The changelog labels every entry by month only, newest "October 2026" (NAICS and SIC on company search, geo_polygon, research profiles, the Usage API), with no exact dates or feed, and Crustdata publishes no SDK, MCP package or other dated source of its own. Read as the Zoho listings read month-only entries, dated to the month, all of October lies 4 to 34 days back, within 90 days but not shown within 30 (20). Nine entries fall in September and October, months wholly inside the 90 days from 6 August (20). Detailed public changelog, and we didn't test support (12 of 15). The only registry entry found on 1 October sat under a personal GitHub namespace, and we found no official SDKs (0). Versioned specs are current. No packages to judge (5 of 10). 20 + 20 + 12 + 0 + 5 = 57.
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 Crustdata API + MCP +28
Crustdata API + MCP 89
Eight OpenAPI YAML files for version 2025-11-01, one per API group (account, batch, company, job, person, social_post, watch, web) (25). llms.txt with Markdown twins (10). Endpoint pages explain cost and when to search versus enrich (17 of 20). Typed filter trees with documented operators (12 of 15). Structured error envelope {error: {type, message, metadata}} and a usage-errors endpoint, with examples (13 of 15). Date-pinned API versions and a detailed changelog. Three changelog entries since August are flagged breaking inside the same pinned version, which undercuts the pin (12 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).
Reliability Crustdata API + MCP +7
Crustdata API + MCP 42
No status page found. status.crustdata.com still doesn't answer and the docs link none (0). No readable incident history (5). Default rate limits published per endpoint, 15 a minute on enrich, 30 on search, 10 on live lookups and watch management, 60 on the usage endpoints, 300 on autocomplete (15). 429s return a typed rate_limit_error with X-RateLimit-Limit, -Remaining and -Reset headers, Retry-After on batch concurrency limits, back-off with jitter recommended, and batch guidance to poll before resubmitting. No idempotency keys, so safe-retry guidance without keys (12). No SLA found, and the published terms cover the website only (0). The API is generally available. Natural-language person search is labelled beta, but the core endpoints aren't (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.
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).
Agent ergonomics Prospeo API + MCP +6
Crustdata API + MCP 73
Premium field groups are opt-in and billed per group, cursor pagination, and the MCP publishes its tool catalogue as a resource instead of a long tools/list (22 of 25). Cursor pagination and rich filters (20). Typed errors, credit_limit_exceeded on 402 and a usage-errors endpoint grouped by error type (18 of 20). Batch jobs have poll-before-resubmit guidance, with no idempotency keys found (8 of 20). Every call needs the x-api-version header or it gets the latest version, and we found no official SDKs (5 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).
Score by category
| Category | Weight | Crustdata API + MCP | Prospeo API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 42 | 35 | Crustdata API + MCP +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 89 | 61 | Crustdata API + MCP +28 |
| Agent ergonomics | 13% | 73 | 79 | Prospeo API + MCP +6 |
| Security & auth | 14% | 56 | 54 | Crustdata API + MCP +2 |
| Payments & pricing | 10% | 8 | 60 | Prospeo API + MCP +52 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 57 | 19 | Crustdata API + MCP +38 |
| Transparency & trust | 7% | 56 | 60 | Prospeo API + MCP +4 |
| Negative events | ≤15 | -3 | 0 | |
| Total | D 52.4/100 | D 53.6/100 |
Facts side by side
| Fact | Crustdata API + MCP | Prospeo API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Crustdata | Prospeo |
| Hosted endpoint | https://api.crustdata.com | https://api.prospeo.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | io.prospeo/prospeo-mcp-server |
| Last release | none | 2026-10-13 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2025-05-19 | 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 | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 0 stars, 641 npm/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Prospeo API + MCP higher.
| Reviewer | Crustdata API + MCP | Prospeo API + MCP |
|---|---|---|
| LedgerCost analyst | 2/5 Credits with no dollar figure attached | 4/5 $0.0245 an email, and a miss costs nothing |
| WardenSecurity auditor | 3/5 Per-key caps, no security programme | 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
Crustdata API + MCP
Per-field credit prices readable per account, X-Credits-Used on every response, per-key caps and $20 in free credits for new self-serve accounts. No status page, no SLA, no dollar price per credit, and changes that refuse earlier valid requests posted only after they shipped.
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
Crustdata API + MCP
- Always send
x-api-version: 2025-11-01. Unpinned calls get the latest version - Call
/account/endpointsfirst to see what your plan enables and what each field costs - Ask only for the premium field groups you need, since each one bills
- Poll
GET /batch/{id}before submitting more batch jobs. Active jobs count against a cap of 5 to 30 - Read the
crustdata://catalogresource before calling MCP tools
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, Crustdata API + MCP or Prospeo API + MCP?
Prospeo API + MCP scores 53.6 (D) on agent readiness against Crustdata API + MCP's 52.4 (D), and leads in 3 of 7 scored categories. Crustdata API + MCP leads on reliability, schema & documentation and maintenance & community.
Do Crustdata API + MCP and Prospeo API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Crustdata API + MCP and Prospeo API + MCP without installing anything?
Yes. Crustdata API + MCP has a hosted endpoint at https://api.crustdata.com and Prospeo API + MCP at https://api.prospeo.io.
Other comparisons with Crustdata API + MCP or Prospeo API + MCP
- Apollo API + MCP vs Crustdata API + MCP
- Apollo API + MCP vs Prospeo API + MCP
- Clay vs Crustdata API + MCP
- Clay vs Prospeo API + MCP
- Coresignal API + MCP vs Crustdata API + MCP
- Coresignal API + MCP vs Prospeo API + MCP
- Crustdata API + MCP vs Databar
- Crustdata API + MCP vs Dievio
- Crustdata API + MCP vs Enrich Layer API + MCP
- Crustdata API + MCP vs Explorium AgentSource
- Crustdata API + MCP vs FullEnrich API + MCP
- Crustdata API + MCP vs Fuse MCP
- Crustdata API + MCP vs Gojiberry
- Crustdata API + MCP vs Hunter API + MCP
- Crustdata API + MCP vs LeadMagic API + MCP
- Crustdata API + MCP vs Lusha API + MCP
- Crustdata API + MCP vs People Data Labs
- Crustdata API + MCP vs Retriever
- Crustdata API + MCP vs RocketReach API
- Crustdata API + MCP vs ZoomInfo API + MCP
- Dievio vs Prospeo API + MCP
- Enrich Layer API + MCP vs Prospeo 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 Crustdata API + MCP
- Clearbit vs Prospeo API + MCP
- Crustdata API + MCP vs Dropcontact API + MCP
- Crustdata API + MCP vs FullContact
- Crustdata API + MCP vs ZeroBounce
- Databar vs Prospeo API + MCP
- Dropcontact API + MCP vs Prospeo API + MCP
- FullContact vs Prospeo API + MCP
- Prospeo API + MCP vs ZeroBounce
- Hunter API + MCP vs Prospeo API + MCP
Machine-readable
- This page as Markdown
/compare/crustdata-vs-prospeo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/crustdata.json·/api/v1/tools/prospeo.json - From a terminal
anchor compare crustdata prospeo(the CLI) - Over MCP
compare_tools {"a": "crustdata", "b": "prospeo"}at/mcp, no key