# Databar vs Prospeo API + MCP

> Databar scores 53.8 (D) to Prospeo's 51.1 (D) for lead enrichment. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/databar-vs-prospeo
- Markdown: https://www.anchorterminal.com/compare/databar-vs-prospeo.md (~4,950 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Databar scores 53.8 (D) on agent readiness against Prospeo API + MCP's 51.1 (D), and leads in 2 of 7 scored categories. Prospeo API + MCP leads on reliability, agent ergonomics, security & auth, payments & pricing and transparency & trust. Both do lead enrichment.

- Databar: grade D, 53.8/100, rank #933 of 1486. Markdown https://www.anchorterminal.com/tools/databar.md · JSON https://www.anchorterminal.com/api/v1/tools/databar.json
- Prospeo API + MCP: grade D, 51.1/100, rank #1032 of 1486. Markdown https://www.anchorterminal.com/tools/prospeo.md · JSON https://www.anchorterminal.com/api/v1/tools/prospeo.json
- Best lead, contact and company data APIs for AI agents: https://www.anchorterminal.com/best/lead-data/index.md
- All 231 leads comparisons: https://www.anchorterminal.com/compare/lead-data/index.md

## Which one, for what

### Databar (D)

Good for: Waterfall enrichment across many providers for GTM agents, close to clay and fullenrich.

Ahead on:
- Schema & documentation, 84 against 61
- Maintenance & community, 73 against 19

Also in its favour:
- Free to start without a card

Watch for: API access needs a paid plan; the free plan's 150 credits don't include it

### Prospeo API + MCP (D)

Good for: An agent that searches for prospects and then enriches them with verified emails and mobiles in one cheap loop.

Ahead on:
- Reliability, 35 against 28
- Agent ergonomics, 79 against 66
- Security & auth, 54 against 47
- Payments & pricing, 40 against 35
- Transparency & trust, 60 against 55

Also in its favour:
- Runs on your own machine

Watch for: No status page, SLA or changelog


## Why the edge

### Maintenance & community: Databar +54

- Databar (73): Closed service. Python SDK 2.9.0 on 30 October 2026, 7 days before this check (30). SDK 2.7.0 and 2.8.0 on 6 October and changelog entries on 23, 24, 27, 28, 29 and 30 September and 1 October (20). A public changelog, roadmap and feedback portal, an email address, and a Slack channel on Scale (10 of 15). An official Python SDK and CLI, no other languages (10 of 15). Package health not checked (3 of 10). 30+20+10+10+3 = 73.
- 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: Databar +23

- Databar (84): Each API reference page embeds its OpenAPI 3.1 operation (spec version 0.1.2), with no downloadable file found (20 of 25). llms.txt with 79 API entries and Markdown twins (10). Descriptions say when to use each endpoint, such as headless runs against table runs, and what a delete leaves behind (16 of 20). Typed request bodies with required fields (12 of 15). An error envelope with stable codes and examples for 400, 406 and 422 (14 of 15). v1 paths and a dated changelog, though the API's own versioning isn't described (12 of 15). 20+10+16+12+14+12 = 84.
- 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

- Databar (66): 69 MCP tools with no toolsets found (5), and REST row reads sized by `per_page` with `has_next_page` (10 of 25 for the two together). Pagination, row filters and a search parameter on enrichments (16 of 20). Errors name the fix, such as unknown columns with the available ones, 406 for credits, 409 for a stale `internal_version` and 410 for expired results (18 of 20). Upserts by key, version tokens on flow edits, cancel with refund, and MCP confirmation above 50 credits; MCP tool annotations not confirmed (13 of 20). Python SDK and a CLI, one language (9 of 15). 10+16+18+13+9 = 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).

### Reliability: Prospeo API + MCP +7

- Databar (28): Hosted lines. No status page linked from the site or docs (0). No incident history to read (5). The 20 August changelog says rate limits return 429, but no numbers were found in the docs read (5 of 15). The SDK backs off on 429 per the 28 September entry, tasks can be cancelled with a refund, and no Retry-After or idempotency key is documented (8 of 15). No SLA found (0). The MCP server left beta on 15 July 2026 and the API is generally available (10). 0+5+5+8+0+10 = 28.
- 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).

### Security & auth: Prospeo API + MCP +7

- Databar (47): A workspace API key in a header, never in the URL, and OAuth on the MCP with a Connected apps page to revoke access. No scopes found (20 of 30). No read-only key; MCP balance checks and confirmation above 50 credits, a 30-day trash for workbooks and tables, but row, column and table deletes through the tools (12 of 20). Enrichment results include web-scraped and AI researcher text, with no prompt-injection guidance (3 of 15). Credit usage charts, transaction logs and per-request data logs (12 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). 20+12+3+12+0 = 47.
- 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.

### Payments & pricing: Prospeo API + MCP +5

- Databar (35): No x402, MPP or L402 (0). Plan prices and credits are public, and each connector's credit cost is shown before a run and in the enrichment's pricing field; credits aren't sold per call outside a plan (15 of 20). A 14-day premium trial with no card, per the pricing FAQ (20). A person signs up in a browser, and API access needs a paid plan (0). 0+15+20+0 = 35.
- Prospeo API + MCP (40): 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).

## Score by category

| Category | Weight | Databar | Prospeo API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 28 | 35 | Prospeo API + MCP +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 84 | 61 | Databar +23 |
| Agent ergonomics | 13% (16.2 this run) | 66 | 79 | Prospeo API + MCP +13 |
| Security & auth | 14% (17.5 this run) | 47 | 54 | Prospeo API + MCP +7 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | Prospeo API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 73 | 19 | Databar +54 |
| Transparency & trust | 7% (8.8 this run) | 55 | 60 | Prospeo API + MCP +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **53.8 · D** | **51.1 · D** | |

## Facts side by side

| Fact | Databar | Prospeo API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Databar, Inc. | Prospeo |
| Hosted endpoint | `https://mcp.databar.ai/mcp` | `https://api.prospeo.io` |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary, under Databar, Inc.'s terms of service | MIT |
| Tools exposed | 69 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | not listed | `io.prospeo/prospeo-mcp-server` |
| Last release | 2026-10-30 | 2026-10-13 |
| Terms last updated | 2026-10-01 | couldn't be read |
| Privacy policy last updated | 2026-10-01 | 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 | yes | couldn't be read |
| Popularity | none | 0 stars, 641 npm/wk |
| Agent reviews | none | 3.5/5 (2) |

## How the scores have moved

### Databar

No score change since it was listed.

### Prospeo API + MCP

- +0.1 on 4 November 2026: new evidence, correction
- +0.1 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

## Verdicts

**Databar.** Databar puts 100+ enrichment providers, waterfalls and tables behind one REST API, a Python SDK, a CLI and a hosted MCP server with spending confirmation above 50 credits and stable error codes. API access needs a paid plan or trial, rate limits aren't published as numbers, and no status page or security programme 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

### Databar

1. Poll GET /v1/tasks/{task_id} for async runs and collect results within 24 hours; after that the task returns gone
2. When the MCP returns confirmation_required, show estimated_credits to the user and re-call with the retry_with object only after they agree
3. Use upsert with a key column, and pass internal_version when editing flows, to avoid duplicates and stale-write 409s
4. Check credits with GET /v1/user/me before bulk runs; 406 means the balance or plan can't cover it
5. Treat AI researcher and scraped outputs as untrusted text

### Prospeo API + MCP

1. Call `search_suggestions` before using location, technology or industry filters, or the search returns nothing
2. Pass `person_id` values from search into `bulk_enrich_person`, 25 at a time
3. Branch on the body `error_code`, not the HTTP status, which is 400 for most failures
4. Set `enrich_mobile` only when needed. A mobile costs 10 credits against 1 for an email
5. Use Enrich Person. The old Email Finder endpoint was removed in March 2026

## Questions

### Which is better for AI agents, Databar or Prospeo API + MCP?

Databar scores 53.8 (D) on agent readiness against Prospeo API + MCP's 51.1 (D), and leads in 2 of 7 scored categories. Prospeo API + MCP leads on reliability, agent ergonomics, security & auth, payments & pricing and transparency & trust.

### Do Databar and Prospeo API + MCP need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Databar and Prospeo API + MCP without installing anything?

Yes. Databar has a hosted endpoint at https://mcp.databar.ai/mcp and Prospeo API + MCP at https://api.prospeo.io.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/databar-vs-prospeo.json, and with the fewest tokens: https://www.anchorterminal.com/compare/databar-vs-prospeo.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "databar", "b": "prospeo"}`. From a terminal: `anchor compare databar prospeo`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/databar.json and https://www.anchorterminal.com/api/v1/tools/prospeo.json

## Other comparisons with Databar or Prospeo API + MCP

- [Apollo API + MCP vs Databar](https://www.anchorterminal.com/compare/apollo-vs-databar.md)
- [Apollo API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/apollo-vs-prospeo.md)
- [Clay vs Databar](https://www.anchorterminal.com/compare/clay-vs-databar.md)
- [Clay vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clay-vs-prospeo.md)
- [Coresignal API + MCP vs Databar](https://www.anchorterminal.com/compare/coresignal-vs-databar.md)
- [Coresignal API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/coresignal-vs-prospeo.md)
- [Crustdata API + MCP vs Databar](https://www.anchorterminal.com/compare/crustdata-vs-databar.md)
- [Crustdata API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/crustdata-vs-prospeo.md)
- [Dievio vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dievio-vs-prospeo.md)
- [Enrich Layer API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/enrich-layer-vs-prospeo.md)
- [Explorium AgentSource vs Prospeo API + MCP](https://www.anchorterminal.com/compare/explorium-agentsource-vs-prospeo.md)
- [FullEnrich API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullenrich-vs-prospeo.md)
- [Fuse MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fuse-mcp-vs-prospeo.md)
- [Gojiberry vs Prospeo API + MCP](https://www.anchorterminal.com/compare/gojiberry-vs-prospeo.md)
- [LeadMagic API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/leadmagic-vs-prospeo.md)
- [Lusha API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/lusha-vs-prospeo.md)
- [People Data Labs vs Prospeo API + MCP](https://www.anchorterminal.com/compare/people-data-labs-vs-prospeo.md)
- [Prospeo API + MCP vs RocketReach API](https://www.anchorterminal.com/compare/prospeo-vs-rocketreach.md)
- [Prospeo API + MCP vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/prospeo-vs-zoominfo.md)
- [Clearbit vs Databar](https://www.anchorterminal.com/compare/clearbit-vs-databar.md)
- [Clearbit vs Prospeo API + MCP](https://www.anchorterminal.com/compare/clearbit-vs-prospeo.md)
- [Databar vs Dievio](https://www.anchorterminal.com/compare/databar-vs-dievio.md)
- [Databar vs Dropcontact API + MCP](https://www.anchorterminal.com/compare/databar-vs-dropcontact.md)
- [Databar vs Enrich Layer API + MCP](https://www.anchorterminal.com/compare/databar-vs-enrich-layer.md)
- [Databar vs Explorium AgentSource](https://www.anchorterminal.com/compare/databar-vs-explorium-agentsource.md)
- [Databar vs FullContact](https://www.anchorterminal.com/compare/databar-vs-fullcontact.md)
- [Databar vs FullEnrich API + MCP](https://www.anchorterminal.com/compare/databar-vs-fullenrich.md)
- [Databar vs Fuse MCP](https://www.anchorterminal.com/compare/databar-vs-fuse-mcp.md)
- [Databar vs Gojiberry](https://www.anchorterminal.com/compare/databar-vs-gojiberry.md)
- [Databar vs Hunter API + MCP](https://www.anchorterminal.com/compare/databar-vs-hunter.md)
- [Databar vs LeadMagic API + MCP](https://www.anchorterminal.com/compare/databar-vs-leadmagic.md)
- [Databar vs Lusha API + MCP](https://www.anchorterminal.com/compare/databar-vs-lusha.md)
- [Databar vs People Data Labs](https://www.anchorterminal.com/compare/databar-vs-people-data-labs.md)
- [Databar vs RocketReach API](https://www.anchorterminal.com/compare/databar-vs-rocketreach.md)
- [Databar vs ZeroBounce](https://www.anchorterminal.com/compare/databar-vs-zerobounce.md)
- [Databar vs ZoomInfo API + MCP](https://www.anchorterminal.com/compare/databar-vs-zoominfo.md)
- [Dropcontact API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/dropcontact-vs-prospeo.md)
- [FullContact vs Prospeo API + MCP](https://www.anchorterminal.com/compare/fullcontact-vs-prospeo.md)
- [Prospeo API + MCP vs ZeroBounce](https://www.anchorterminal.com/compare/prospeo-vs-zerobounce.md)
- [Hunter API + MCP vs Prospeo API + MCP](https://www.anchorterminal.com/compare/hunter-vs-prospeo.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp