Runner
Sign in
A tool you may already use

Crustdata and Runner

Crustdata is a real-time B2B data API: company and people records, job listings and change alerts, delivered to developers and AI agents on a credit-based key.

Runner is where that data lands and gets acted on — the record, the gate it passed, the fit reading against your ICP and the one next step, with a person approving what matters.

What it is usually bought for

Research an account before anyone works it

The job, on its own page: Research an account before anyone works it

Built into Runner

  • Runner reads a company's own website and keeps what it says, with the source
  • Every claim lands with its source and the time it was read
  • A fit scorecard your team fills in, with the evidence behind each score

Worth knowing

Runner does the reading on a research account you connect yourself, then files the evidence for your team to review. What comes back is evidence for a decision — never permission to contact anyone.

When to keep Crustdata

  • Keep Crustdata if you are building your own agent or platform on a data feed. Runner connects to the same key rather than asking you to leave it.
  • Runner reads Crustdata's company and person records through its enrichment order. It does not read Crustdata's Watcher alerts today; the signals Runner acts on without a vendor are the ones from your own site, forms and inbox.

Using Crustdata with Runner

Steps re-read against the application on 2026-10-10.

Connect your own Crustdata key and it becomes one source in Runner's enrichment order, tried after the free registries, with every value landing as a suggestion your team reviews.

  1. Connect your Crustdata API key under Settings, Integrations, Enrichment providers. Runner checks it with Crustdata's free balance call and stores it encrypted for your workspace.
  2. Open a company record and choose Look up this company. Runner tries its free registry sources first and Crustdata after them, and stops at the first answer it is sure enough of.
  3. Read what it tried. Every field shows its source, the time it was read and the confidence, and a value lands as a suggestion for a person to accept.
  4. On a contact, Enrich fills the name and title from the profile already on file, behind the person-level gate, then reads fit against your ICP and proposes one next step.
  5. Set the order per field in the project's enrichment settings, with a confidence floor and a spend ceiling, so a paid source is spent only where a free one could not answer.

Use what already works

Connect your own research account to supply the public-page reads. Runner turns those reads into cited evidence and a review queue; your team keeps the final decision.

Apply for accessSee the whole stack

Trademarks of their owners. No affiliation or endorsement.