# Databar vs Explorium AgentSource (slim)

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

- Full: https://www.anchorterminal.com/compare/databar-vs-explorium-agentsource.md (~5,300 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/databar-vs-explorium-agentsource.json · canonical https://www.anchorterminal.com/compare/databar-vs-explorium-agentsource
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Databar scores 53.8 (D) on agent readiness against Explorium AgentSource's 41.5 (E), and leads in 4 of 7 scored categories. Explorium AgentSource leads on reliability, payments & pricing and transparency & trust. Both do lead enrichment.

- Databar: D 53.8, rank #933 of 1486 · https://www.anchorterminal.com/tools/databar.min.md
- Explorium AgentSource: E 41.5, rank #1281 of 1486 · https://www.anchorterminal.com/tools/explorium-agentsource.min.md
- Databar, good for Waterfall enrichment across many providers for GTM agents, close to clay and fullenrich. Ahead on Schema & documentation, 84 against 40; Security & auth, 47 against 32; Maintenance & community, 73 against 28. Also Free to start without a card.
- Explorium AgentSource, good for Agents that build prospect lists by filter and then enrich them, or that watch companies for events such as funding and role changes. Ahead on Reliability, 42 against 28; Payments & pricing, 40 against 35; Transparency & trust, 61 against 55.

| Category | Databar | Explorium AgentSource |
| --- | --- | --- |
| Reliability (16%) | 28 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 40 |
| Agent ergonomics (13%) | 66 | 63 |
| Security & auth (14%) | 47 | 32 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 73 | 28 |
| Transparency & trust (7%) | 55 | 61 |

| Fact (where they differ) | Databar | Explorium AgentSource |
| --- | --- | --- |
| Vendor | Databar, Inc. | Explorium Ltd. |
| Hosted endpoint | `https://mcp.databar.ai/mcp` | `https://api.explorium.ai` |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| Price for lead enrichment | not published | $0.15 per record |
| Licence | Proprietary, under Databar, Inc.'s terms of service | Proprietary service under the Explorium Terms of Use. The `mcp-explorium` repository of connection files is MIT |
| Tools exposed | 69 | 11 |
| Last release | 2026-10-30 | 2026-09-02 |
| Terms last updated | 2026-10-01 | 2026-06-14 |
| Privacy policy last updated | 2026-10-01 | 2026-06-28 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |

Why the edge:
- Maintenance & community, Databar +45: 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.); Explorium AgentSource 28 (Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The last dated API change found is v2 general availability on 2 September 2026, 63 days before 4 November (20 of 30). No dated changelog, so three entries in 90 days could not be shown (0). Support by email and by a shared Slack channel for customers that have one, with no public changelog or forum (5 of 15). No official REST SDK found. The repository's `server.json` names `ai.explorium/mcp-explorium`, but no registry page could be read (0). The `mcp-explorium` repository is MIT, with its last commit on 22 January 2026 and only a publishing workflow, no CI (3 of 10). 20+0+5+0+3 = 28.)
- Schema & documentation, Databar +44: 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.); Explorium AgentSource 40 (Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The OpenAPI 3.1 file read on 9 October has no recorded visible link from a docs page, and the host can't be re-read to find one, so it no longer counts as a published contract (0 of 25). llms.txt and a Markdown twin of every docs page (10). The docs pages and the 11 MCP tool descriptions say what each call is for and what to call first (12 of 20). The typed schemas, enums and item limits were read from that file, so they no longer count (0 of 15). Docs pages have request and response examples, and the error guide lists Partner ID header messages that don't match the `api_key` scheme (10 of 15). Versions live in the path with a migration guide and a full v2 change list. No dated changelog was found (8 of 15). 0+10+12+0+10+8 = 40.)
- Security & auth, Databar +15: 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.); Explorium AgentSource 32 (Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. The docs say each company gets a single API key shared by all its users, sent in a header. The site's `auth.md` says a key can be deleted in the console, and the key page says to ask an administrator for a reset. No scopes (12 of 30). No read-only mode or per-key limits. The API mostly reads, writes are limited to webhooks and event enrolments, and auto-refill has an optional cap (5 of 20). Research scrapes web pages and the LinkedIn post enrichments return third-party text. No prompt-injection guidance was found in the docs (2 of 15). Balance and aggregation endpoints, per-call credit reporting, correlation IDs and last-active times for users. No per-call log was found (8 of 15). The privacy policy states SOC 2, ISO 27001 and ISO 27701, with no report, security.txt, disclosure policy or bug bounty found. A certification claim with no report or reporting route takes 5, as settled in this run (5 of 20). No GitHub-reviewed advisory names Explorium in the 12 months to 4 November. 12+5+2+8+5 = 32.)
- Reliability, Explorium AgentSource +14: 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.); Explorium AgentSource 42 (Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. Hosted lines. No status page found. The docs tell users to subscribe to status updates and link no page, and status.explorium.ai did not answer (0). No readable incident history (5). Rate limit published, 200 queries a minute per key over a 60-second sliding window, with each batch entity counted as a query (15). 429s carry `Retry-After` and `X-RateLimit-*` headers and the docs ask for exponential backoff. No idempotency keys were found for the webhook and enrolment writes, so safe-retry guidance without keys takes 12 (12). No SLA is published. The migration guide implies one exists by saying v1 loses its SLA at end of support (0). v2 reached general availability on 2 September 2026, though the conventions page still says request and response schemas are being finalised (10). 0+5+15+12+0+10 = 42.)
- Transparency & trust, Explorium AgentSource +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.); Explorium AgentSource 61 (Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. Closed service. The Explorium Terms of Use (updated 14 June 2026, re-read) cover the Platform, API and data, and let Explorium change or end the service without notice (14 of 30). The privacy policy (updated 28 June 2026) sets out controller and processor roles, publishes 2025 request counts and links an opt-out page. Retention has no periods, and no DPA was found on the pages read (16 of 30). The v1 timeline gives end of support about six months and retirement about twelve months after 2 September 2026, marked indicative, and website traffic enrichment is slated for removal with no date. Dated notices take 15 as settled in this run (15 of 20). Processing in Israel, the United States and the EU is stated. No sub-processor list was found (6 of 20). 14+16+15+6 = 51.)
- Payments & pricing, Explorium AgentSource +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.); Explorium AgentSource 40 (Explorium's terms bar robots and automated collection on its website, so only the terms were re-read on 4 November and other readings are per the 9 October check. No x402, MPP or L402 (0). Credit pack prices and per-operation credit costs are public without a login (20). The pricing page and the site's own `pricing.md` disagree on two packs, which is recorded as a deduction and not here. Free trial of 100 credits for 90 days. No page read asks for a card at sign-up, and the auto-refill guide treats a payment method as something added later (20). The vendor's `auth.md` says registration needs a person and there is no client-registration endpoint (0). Total 40.)