Crustdata review

Crustdata sells people and company data for sales, recruiting, and investing workflows, including workflows run by AI agents. Teams can use its data graph through a REST API or MCP, rather than treating it as a standalone CRM or sequencing tool.

The product combines four main jobs: search for people or companies, enrich records teams already have, surface live signals, and watch selected people or companies for changes. People search supports intent and specific filters; company search covers filters such as location, headcount, growth, and funding. Signals include job moves, hiring, posts, and company filings.

That makes Crustdata a data layer: it can help an agent find or update prospects and react to changes, but teams still need to decide how to use those records in their sales or recruiting process. The API and MCP expose search, enrichment, signals, and watchers to those workflows.

Crustdata’s strongest case is for teams that need current data inside an automated workflow, not just a static list to export. People and company search, enrichment, signals, and watchers sit behind the same API and MCP access, so an agent can look up a record, add details, or monitor it for changes. The listed signals include hiring, funding, job moves, posts, and company events.

The self-serve API has a low-friction entry point: the pricing page lists $20 in free credits for new accounts, with credits valid for 12 months. It lists search from 0.03 credits per result, people enrichment from 1 credit, and company enrichment from 2 credits. That gives teams a way to try usage-based access without a published monthly subscription commitment.

There is some user interest in this agent-oriented approach. In one Reddit thread, a GTM team described using Crustdata for real-time people and company data through an API as part of a stack connected with MCPs. That is an example of how teams may deploy it, not proof of data quality or savings.

The main drawback is that the total cost is hard to forecast from the published pricing. There is no standard monthly or annual subscription price listed for self-serve In-DB API access. Real-time API access and enterprise plans start at four figures per month, with credit-based tiers; enterprise per-credit rates can fall with volume, but the actual rate is not published. The published pricing details also give no fixed monthly credit allowance or usage cap to plan around.

Credits add up across fields. The pricing page lists work email enrichment at 1 credit, personal email at 2, phone at 2, and watchers from 0.5 credits per new result. Premium people-search fields add 0.1 to 2.5 credits per result. Credits expire after 12 months, so unused balances are not indefinite.

Freshness also deserves a check before a large rollout. One Reddit commenter praised Crustdata’s real-time enrichment, while a separate company-dataset discussion reported inconsistent freshness causing downstream problems. Those are user reports, not a definitive measure, but they show why teams should validate the specific data and workflow they need before committing to a four-figure plan.

Crustdata does not list a standard monthly or annual subscription price. Self-serve In-DB API access starts with $20 in free credits for new accounts; search costs from 0.03 credits per result, people enrichment starts at 1 credit, and company enrichment at 2. Credits expire after 12 months.

The step up is steep: Real-time API access starts at four figures per month, with credit-based usage tiers. Enterprise plans also start at four figures monthly; they add custom datasets and dedicated support, while per-credit rates fall with volume. The pricing page does not publish a fixed price for either tier.

Watchers start at 0.5 credits per new result. Add-ons can raise usage: work email costs 1 credit, personal email 2, and phone 2; premium people-search fields add 0.1 to 2.5 credits per result. Check the credit math against expected volume before committing: the free credits are not a predictable subscription, and the published prices do not give a monthly cost estimate for a typical workload.

Treat a move to Crustdata as an integration project, not a simple data import. Its search, enrichment, signals, and watchers are available through an API or MCP, so teams will need to connect those workflows to their existing sales, recruiting, or investing systems. The published materials do not specify migration tools, export formats, or a standard way to move saved searches and watcher configurations.

Before switching, confirm how you can export data and preserve records if you leave; those details are not published here. Keep your existing CRM or database as the system of record until export and replacement workflows are clear. Credit expiry after 12 months and the four-figure monthly starting point for real-time or enterprise access are reasons to reassess usage and budget before renewal or expansion.

The published published material includes no Reddit posts or comments, so we cannot attribute common reasons for leaving to Reddit users. Verify data freshness and any exit process directly with Crustdata before moving production workflows.