Can you trust the numbers in Crustdata?

Crustdata is a provider of people and company data that AI agents can pull through an API or MCP. Its own help pages give 3 reasons its numbers can look different from what you expect. The first to rule out: One website address can bring back several companies, as Crustdata's developer docs explain, so a count of matched companies can run higher than the companies you meant.

What does Crustdata keep track of?

  • Crustdata keeps a last refreshed time on every person and company record it returns.

    In Crustdata's own words: Each record carries an `updated_at` timestamp showing its last refresh. Data updates, read 2026-11-12.

  • Crustdata keeps a deliverability status on each email address it finds, so you can tell stronger contacts from weaker ones.

    In Crustdata's own words: Every business and personal email comes back with a `status` that tells you how deliverable the address is. Contact Enrichment API, read 2026-11-12.

What can make Crustdata's numbers look wrong?

  1. One website address can bring back several companies, as Crustdata's developer docs explain, so a count of matched companies can run higher than the companies you meant.

    In Crustdata's own words: Domain lookups may return multiple matches if the domain is ambiguous. Company Enrichment API, read 2026-11-12.

  2. A Crustdata record can be up to about a month old, as its developer docs say, so a job title or headcount may have changed since it was read.

    In Crustdata's own words: Crustdata refreshes every indexed person and company profile at least once every 30 days Data updates, read 2026-11-12.

  3. A company record can look empty in places only because that part was not asked for, as Crustdata's developer docs explain, so a blank field is not proof the data is missing.

    In Crustdata's own words: Omitted sections come back as `null` placeholders, so list each section you want. Company Enrichment API, read 2026-11-12.

How do I check Crustdata's numbers myself?

  1. When a lookup returns more than one company, checking each one's main website in Crustdata shows which match is the right one.

    In Crustdata's own words: Use `primary_domain` to verify. Company Enrichment API, read 2026-11-12.

  2. If a Crustdata record looks stale, its last refreshed time tells you, and a fresh live lookup of that one record gives a current reading.

    In Crustdata's own words: If a record is older than your workflow allows, call the live endpoint for that one record. Data updates, read 2026-11-12.

How does Crustdata work with Feder?

Connect Crustdata to Feder and it joins your Interest apps. Feder only reads. It never changes anything in Crustdata.

When you connect Crustdata, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Other apps that feed Interest

Questions owners ask about Crustdata

See every connection.

Where do these answers come from?

Everything this page says about Crustdata comes from Crustdata's own pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.