Head to head · Lead enrichment · October 2026 research run
Databar vs Retriever
Databar scores 56 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics. Both do lead enrichment.
Best lead, contact and company data APIs for AI agents · All 253 leads comparisons
Which one, for what
Databar C
Best for Waterfall enrichment across many providers for GTM agents, close to clay and fullenrich.
Ahead on
- Security & auth, 47 against 23
- Payments & pricing, 53 against 30
- Maintenance & community, 73 against 5
- Transparency & trust, 55 against 49
Also in its favour
- Free to start without a card
- No incidents deducted, where Retriever loses 15 points for them
Watch for
API access needs a paid plan; the free plan's 150 credits don't include it
Best for A sales team that wants an agent to build qualified lead tables and run outreach from Claude, Cursor or Codex.
Ahead on
- Reliability, 45 against 28
- Agent ergonomics, 75 against 66
Watch for
Its sequences send LinkedIn invitations, messages, visits and likes from connected accounts automatically, which LinkedIn forbids, so customers' accounts can be restricted
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.
Maintenance & community Databar +68
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.
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). Support is an email address and a demo booking, with no public changelog or community channel that answers (5 of 25). Not in the official MCP registry and no official SDK (0). No package to check (0). The domain dates from 7 April 2026.
Security & auth Databar +24
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.
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 (20), less 10 because the MCP docs offer the key in the URL as ?api_key= (10 of 30). No read-only mode; destructive hints and explicit-request instructions on cancels and deletes, and the outreach toolset can be switched off (8 of 20). The tools return scraped pages, social posts and inbox replies, with no prompt-injection guidance found (0). Credit charges per run and a credits ledger by source, but no audit log documented (5 of 15). No security.txt (404), disclosure policy, bug bounty or certification found (0).
Payments & pricing Databar +23
Databar 53
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Retriever 30
No x402, MPP or L402 (0). Credits per action and the dollar price per credit ($0.0134 on Starter) are public without a login (30). No free tier or trial without a card found; the terms say only that free tiers may be offered (0). Access needs a browser signup and a subscription, so an agent can't onboard itself (0).
Reliability Retriever +17
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.
Retriever 45
No status page found, linked from neither the site nor the docs (0), so no incident history to read (5). Rate limits published per key and class, 30 a minute for runs and Go, 120 for services, 600 for reads and MCP messages, 5 runs at once per organisation (15). 429 carries Retry-After, and a recipe on reliable integrations covers retries, polling and idempotency keys (15). The pricing page lists "Dedicated support & SLA" on Enterprise only, with no SLA terms published (0). The API and MCP server aren't labelled beta (10).
Agent ergonomics Retriever +9
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.
Retriever 75
67 tools in the catalogue (5), with 5 back because the outreach tools are a toolset shown only when the organisation has a sender and switchable in settings (10 of 25). Limit, offset and cursor pagination, up to 1,000 rows a call, and the first 20 rows returned with a finished run (18 of 20). Stable error codes with the action to take (20). Idempotency-Key on run creation, and readOnlyHint, destructiveHint and idempotentHint on the tools (20). Few required parameters (a run needs only a prompt), but no official SDK, only a Node client in a recipe (7 of 15).
Transparency & trust Databar +6
Databar 55
Closed service with terms effective 1 October 2026 naming Databar, Inc. of Delaware (15 of 30). The privacy policy keeps data 'for as long as needed' with no periods; the docs give 24 hours for task results; a DPA is part of the agreement but was not read (15 of 30). The changelog flagged breaking API and SDK changes on 20 August 2026, and the terms let Databar retire any form of programmatic access; no notice period stated (8 of 20). Sub-processors are disclosed under the DPA, which was not read; data is processed in the United States (5 of 20). 15+15+8+5 = 43.
Retriever 49
Closed source with clear terms, last updated 30 August 2026 (15). The privacy policy states retention (deletion within 30 days of closing an account) and names some subprocessors, but says nothing about the LinkedIn and email accounts customers connect, the people in lead tables or the data providers named on the pricing page (12 of 30). The terms say the service may be changed or removed "with reasonable notice" and material changes to the terms get 15 days' notice; no deprecation dates found (8 of 20). Subprocessors are given as examples (Vercel, Railway, Supabase, Anthropic, OpenAI) with no data locations, beyond Standard Contractual Clauses for transfers (8 of 20).
Score by category
| Category | Weight | Databar | Retriever | Edge |
|---|---|---|---|---|
| Reliability | 16% | 28 | 45 | Retriever +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 82 | Databar +2 |
| Agent ergonomics | 13% | 66 | 75 | Retriever +9 |
| Security & auth | 14% | 47 | 23 | Databar +24 |
| Payments & pricing | 10% | 53 | 30 | Databar +23 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 73 | 5 | Databar +68 |
| Transparency & trust | 7% | 55 | 49 | Databar +6 |
| Negative events | ≤15 | 0 | -15 | |
| Total | C 56/100 | F 32/100 |
Facts side by side
| Fact | Databar | Retriever |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Databar, Inc. | Retriever |
| Hosted endpoint | https://mcp.databar.ai/mcp | https://api.retriever.run/mcp |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary, under Databar, Inc.'s terms of service | none |
| Tools exposed | 69 | 67 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | none |
| Terms last updated | 2026-10-01 | 2026-08-30 |
| Privacy policy last updated | 2026-10-01 | 2026-08-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
How the scores have moved
Retriever
No score change since it was listed.
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.
Retriever
Retriever automates outreach from customers' LinkedIn accounts, which LinkedIn's rules forbid. For agents it has an OAuth MCP server, an OpenAPI file, idempotency keys, stable error codes and published credit prices, but no status page, changelog, security contact, free tier or named company behind it.
Before you call either
Databar
- Poll GET /v1/tasks/{task_id} for async runs and collect results within 24 hours; after that the task returns gone
- When the MCP returns confirmation_required, show estimated_credits to the user and re-call with the retry_with object only after they agree
- Use upsert with a key column, and pass internal_version when editing flows, to avoid duplicates and stale-write 409s
- Check credits with GET /v1/user/me before bulk runs; 406 means the balance or plan can't cover it
- Treat AI researcher and scraped outputs as untrusted text
Retriever
- Don't enrol leads in a sequence with LinkedIn steps without the user knowing LinkedIn forbids automated activity and can restrict their account
- Send an
Idempotency-Keywith each run and replay with the same key after a timeout, so a retry doesn't start a second billed run - Run
getEmail,getPhoneNumberandwebResearchthroughservice_batch_execute, even for one person;service_executerefuses them - Check
creditsbefore a paid run, and callservice_inspectfor a service'sthingsToKnowand credit cost before executing it - On 429 wait for Retry-After; at most 5 runs execute per organisation, so a queued run starts on its own and shouldn't be created again
Questions
Which is better for AI agents, Databar or Retriever?
Databar scores 56 (C) on agent readiness against Retriever's 32 (F), and leads in 5 of 7 scored categories. Retriever leads on reliability and agent ergonomics.
Do Databar and Retriever need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Databar and Retriever without installing anything?
Yes. Databar has a hosted endpoint at https://mcp.databar.ai/mcp and Retriever at https://api.retriever.run/mcp.
Other comparisons with Databar or Retriever
- Apollo API + MCP vs Databar
- Apollo API + MCP vs Retriever
- Clay vs Databar
- Clay vs Retriever
- Coresignal API + MCP vs Databar
- Coresignal API + MCP vs Retriever
- Crustdata API + MCP vs Databar
- Crustdata API + MCP vs Retriever
- Dievio vs Retriever
- Enrich Layer API + MCP vs Retriever
- Explorium AgentSource vs Retriever
- FullEnrich API + MCP vs Retriever
- Fuse MCP vs Retriever
- Gojiberry vs Retriever
- LeadMagic API + MCP vs Retriever
- Lusha API + MCP vs Retriever
- People Data Labs vs Retriever
- Prospeo API + MCP vs Retriever
- Retriever vs RocketReach API
- Retriever vs ZoomInfo API + MCP
- Clearbit vs Databar
- Clearbit vs Retriever
- Databar vs Dievio
- Databar vs Dropcontact API + MCP
- Databar vs Enrich Layer API + MCP
- Databar vs Explorium AgentSource
- Databar vs FullContact
- Databar vs FullEnrich API + MCP
- Databar vs Fuse MCP
- Databar vs Gojiberry
- Databar vs Hunter API + MCP
- Databar vs LeadMagic API + MCP
- Databar vs Lusha API + MCP
- Databar vs People Data Labs
- Databar vs Prospeo API + MCP
- Databar vs RocketReach API
- Databar vs ZeroBounce
- Databar vs ZoomInfo API + MCP
- Dropcontact API + MCP vs Retriever
- FullContact vs Retriever
- Retriever vs ZeroBounce
- Hunter API + MCP vs Retriever
Machine-readable
- This page as Markdown
/compare/databar-vs-retriever.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/databar.json·/api/v1/tools/retriever.json - From a terminal
anchor compare databar retriever(the CLI) - Over MCP
compare_tools {"a": "databar", "b": "retriever"}at/mcp, no key