Use Case

Start With Manifests, Checksums, and Quality Gates

1,578,155 reviewed rows in the current published product

Use the product as a reference implementation for ingestion, normalization, evidence, object storage, and catalog publication.

Agent Database

One-time purchase

not yet pricednot yet pricedper state

Pick the states you need

not yet pricednot yet pricedall 50 states

1,578,155 visible catalog rows

Explore the implementation

Instant CSV delivery · No subscription

Problems You're Probably Running Into

Large replacement files
Long-running jobs
Weak retry semantics
Catalog and artifact drift

How Data Teams Use Our Data

Pipeline architecture
Release automation
Catalog modeling
Object-storage evidence

What's in the Database

Every record includes verified contact information sourced from state licensing authorities:

  • Full Namethe agent's registered legal name
  • Email Addressverified professional email
  • Phone Numberdirect phone when available
  • Stateall 50 US states covered

Frequently Asked Questions

Is the current public catalog an official NPPES release?

Yes. The first reviewed NPPES-derived catalog product is published with aggregate coverage and release evidence. Provider rows are not publicly browsable; secure Stripe checkout provides controlled access to the purchased snapshot.

What evidence accompanies a release?

The release contract includes source identifiers, checksums, schema and transform versions, row counts, quality results, artifact paths, and publication timestamps.

Related Guides

Other Use Cases