# Crustdata API + MCP vs Databar (slim)

> Databar scores 53.8 (D) to Crustdata's 52 (D) for lead search. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/crustdata-vs-databar.md (~4,750 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/crustdata-vs-databar.json · canonical https://www.anchorterminal.com/compare/crustdata-vs-databar
- 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 Crustdata API + MCP's 52 (D), and leads in 2 of 7 scored categories. Crustdata API + MCP leads on reliability, schema & documentation, agent ergonomics and security & auth. Both do lead search.

- Crustdata API + MCP: D 52, rank #1003 of 1510 · https://www.anchorterminal.com/tools/crustdata.min.md
- Databar: D 53.8, rank #939 of 1510 · https://www.anchorterminal.com/tools/databar.min.md
- Crustdata API + MCP, good for Agents that monitor companies, people, jobs or posts over time and need change notifications. Ahead on Reliability, 42 against 28; Schema & documentation, 89 against 84; Agent ergonomics, 73 against 66; Security & auth, 56 against 47.
- Databar, good for Waterfall enrichment across many providers for GTM agents, close to clay and fullenrich. Ahead on Payments & pricing, 35 against 5; Maintenance & community, 73 against 57. Also Free to start without a card; No incidents deducted, where Crustdata API + MCP loses 3 points for them.

| Category | Crustdata API + MCP | Databar |
| --- | --- | --- |
| Reliability (16%) | 42 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 84 |
| Agent ergonomics (13%) | 73 | 66 |
| Security & auth (14%) | 56 | 47 |
| Payments & pricing (10%) | 5 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 73 |
| Transparency & trust (7%) | 56 | 55 |

| Fact (where they differ) | Crustdata API + MCP | Databar |
| --- | --- | --- |
| Vendor | Crustdata | Databar, Inc. |
| Hosted endpoint | `https://api.crustdata.com` | `https://mcp.databar.ai/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, SSE (legacy) |
| Pricing | Pay per use | Paid |
| Licence | none | Proprietary, under Databar, Inc.'s terms of service |
| Tools exposed | none | 69 |
| Last release | none | 2026-10-30 |
| Terms last updated | no date given | 2026-10-01 |
| Privacy policy last updated | 2025-05-19 | 2026-10-01 |
| Arbitration or class-action waiver | not found in the text | yes |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Payments & pricing, Databar +30: Crustdata API + MCP 5 (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).); 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.)
- Maintenance & community, Databar +16: 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.); 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.)
- Reliability, Crustdata API + MCP +14: 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.); 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.)
- Security & auth, Crustdata API + MCP +9: Crustdata API + MCP 56 (Bearer keys, several named keys per account with active, inactive and deleted states, per-key endpoint restrictions and monthly credit caps since July 2026. OAuth for the MCP (28 of 30). Per-key endpoint limits give least privilege. Watchers create standing jobs, and the MCP docs don't separate read and write tools or ask for confirmation (12 of 20). Live web fetch, web search and social posts return untrusted text, and we found no prompt-injection guidance (2 of 15). Usage and logs filterable by key, a usage events API from October 2026, and `X-Credits-Used` on every response (14 of 15). No security.txt, bug bounty, disclosure policy or certification found (0 of 20).); 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.)
- Agent ergonomics, Crustdata API + MCP +7: 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).); 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.)
- Schema & documentation, Crustdata API + MCP +5: 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).); 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.)