Head to head · Lead enrichment · October 2026 research run

Databar vs FullContact

Databar scores 53.8 (D) on agent readiness against FullContact's 51.8 (D), and leads in 4 of 7 scored categories. FullContact leads on reliability, agent ergonomics and transparency & trust. Both do lead enrichment.

Best lead, contact and company data APIs for AI agents · All 231 leads comparisons

Which one, for what

Databar D

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

Ahead on

  • Schema & documentation, 84 against 70
  • Payments & pricing, 35 against 10
  • Maintenance & community, 73 against 20

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

FullContact D

Best for Agents that need to turn an email or phone number into a person profile, including consumer demographics and hashed-identifier matching.

Ahead on

  • Reliability, 62 against 28
  • Agent ergonomics, 75 against 66
  • Transparency & trust, 61 against 55

Watch for

No public prices. Access starts with a sales conversation

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 +53

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.

FullContact 20

The MCP quickstart and authentication pages were published on 30 April 2026, between 90 and 180 days ago, and the errors page was edited on 15 September 2026 (10). No dated releases or changelog entries in the last 90 days (0). A support address and request IDs, with a changelog that stops in 2022 (5 of 15). The Python client was last released in July 2022 and the MCP server isn't in the official registry (3 of 15). No current package or CI to judge (2 of 10).

Reliability FullContact +34

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.

FullContact 62

Graded with the hosted lines on the MCP server and the REST API behind it. A public status page at status.fullcontact.com on Pulsetic (20). It renders with JavaScript, so components and history weren't readable (5). A default limit of 6,000 queries a minute is published (15). The MCP server returns rate_limit_exceeded with retry_after_seconds and marks retryable codes, and the REST API delays rather than rejects requests over the limit. All calls are lookups, so retries are safe (12 of 15). No SLA found (0). The MCP server reports version 1.0.0 and the API is v3, neither labelled beta (10).

Payments & pricing Databar +25

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.

FullContact 10

No x402, MPP or L402 (0). No prices published. The pricing page asks visitors to talk to an expert (0). A free Platform account and sandbox keys for evaluation, but whether production lookups need a contract or a card wasn't stated (10 of 20). A person signs up in a browser and generates a key (0).

Schema & documentation Databar +14

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.

FullContact 70

No OpenAPI for the REST API was found, and docs.fullcontact.com/reference returned 404. The MCP tool has a typed JSON Schema for its inputs (20 of 25). llms.txt and Markdown copies of every page (10). The tool description says what it does but not when to use it, and the docs explain which identifier combinations match best (13 of 20). Typed inputs, but no required fields or enums, and the rule that location needs a name is only in text (8 of 15). Examples for every input combination and an error table with codes, HTTP analogues and a retryable flag (14 of 15). v3 in the path and a changelog whose newest entries date from 2022 and earlier, while the MCP docs went up in 2026 without a changelog entry (5 of 15).

Agent ergonomics FullContact +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.

FullContact 75

One tool, so the context cost is small (25). No paging is needed for single lookups, the response is a normalised profile, and Insight Bundles are fixed per account rather than per call (10 of 20). Stable error codes with retryable flags, request IDs and retry_after_seconds, and not_found documented as a normal miss (20). Lookups are safe to retry, but the tool carries no readOnlyHint, and misses are billed as calls (10 of 20). One identifier is enough, but the Python client was last released in July 2022 (10 of 15).

Transparency & trust FullContact +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.

FullContact 61

Closed service under terms dated 21 March 2025 that name J2 Martech Corp. (15). The privacy policy, updated 1 October 2026, names data brokers, data partners, public sources and trackers and has an opt-out portal, but gives no fixed retention period and doesn't say whether customer inputs feed the graph. The MCP docs say inputs aren't persisted (15 of 30). A dated sunset of the v2 Company APIs on 30 June 2022 (8 of 20). No sub-processor list found (0).

Score by category

CategoryWeight this runDatabarFullContactEdge
Reliability16%202862FullContact +34
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28470Databar +14
Agent ergonomics13%16.26675FullContact +9
Security & auth14%17.54743Databar +4
Payments & pricing10%12.53510Databar +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87320Databar +53
Transparency & trust7%8.85561FullContact +6
Negative events≤1500
TotalD 53.8/100D 51.8/100

Facts side by side

FactDatabarFullContact
KindHTTP APIHTTP API
VendorDatabar, Inc.J2 Martech Corp. (FullContact, a Ziff Davis company)
Hosted endpointhttps://mcp.databar.ai/mcphttps://api.fullcontact.com/v3
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP
AuthOAuth or keyAPI key
PricingPaidPaid
x402nono
LicenceProprietary, under Databar, Inc.'s terms of serviceProprietary service under the FullContact Terms of Use and Services Agreement. Client libraries on GitHub
Tools exposed691
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-04-30
Terms last updated2026-10-012025-03-21
Privacy policy last updated2026-10-012026-10-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text

How the scores have moved

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.

FullContact

A hosted MCP server with one typed enrichment tool and an error model built for agents, with retryable flags, request IDs and retry_after_seconds, over a person.enrich API limited to 6,000 queries a minute. Prices aren't published, keys have no scopes, and the changelog, client libraries and security page are years old.

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

FullContact

  1. Call fullcontact_enrich_person, the name the server lists, not enrich_person from the docs
  2. Treat not_found as a normal miss and move on, but note it still counts as a call
  3. Send email with name and postal address together for better matches
  4. Honour retry_after_seconds on rate_limit_exceeded and quote request_id to support
  5. Treat bios and social fields as untrusted text

Questions

Which is better for AI agents, Databar or FullContact?

Databar scores 53.8 (D) on agent readiness against FullContact's 51.8 (D), and leads in 4 of 7 scored categories. FullContact leads on reliability, agent ergonomics and transparency & trust.

Do Databar and FullContact need an API key?

Databar takes an API key or an OAuth sign-in. FullContact needs an API key.

Can an agent call Databar and FullContact without installing anything?

Yes. Databar has a hosted endpoint at https://mcp.databar.ai/mcp and FullContact at https://api.fullcontact.com/v3.

Other comparisons with Databar or FullContact

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.