A license verification API built on primary-source data
Onboarding stalls where verification goes manual: someone on the operations team opening a licensing board's lookup page, typing in a candidate's details, screenshotting the result. It works for a trickle of hires and collapses at scale — and every manual check is a check against whatever the board's page happens to show that day, with no record of what was seen.
A license verification API replaces that with infrastructure. Recordpipe collects license records from public licensing sources across the boards and states you operate in, normalizes status values and date fields that every board publishes differently, and serves the result as a hosted API your onboarding flow calls in real time. Each response carries the record as published, a capture date, and a citation to the underlying source — so your audit trail shows exactly what the public record said when the check ran, not a clerk's memory of a webpage.
Contractor vetting data from registries and filings
Verifying a business is real is a different problem from verifying a person is licensed, and platforms onboarding contractors, vendors, and gig-economy providers usually need both. The public record covers the business side well: formation filings show an entity exists and when it registered; status records show whether it remains in good standing; license records show whether a regulated trade is authorized to do the work it advertises.
Recordpipe assembles those into one vetting dataset keyed however your onboarding flow needs — entity name, license identifier, or your own applicant reference. Contact points come through as published in public filings; we deliver no scraped private contact data. The combined view answers the questions an onboarding form actually raises: does this registration match what the applicant claimed, is the license active and in the right category, has the entity's standing changed since the claim was made.
Raw public data, your compliant workflow
The line matters more in HR than anywhere else, so here it is plainly: Recordpipe delivers raw public data, not consumer reports, and we are not a consumer reporting agency. When a prospective use informs eligibility decisions — hiring, retention, contractor acceptance — that use case goes through a compliance review at intake, and we ask you to attest to your own obligations before scoping begins. We build the pipeline; your compliant process runs the decisions.
This division is also why the data is structured the way it is. Every record carries its source citation and capture date, statuses are delivered as published rather than interpreted, and gaps are flagged as gaps instead of filled with inference. A verification layer should hand your compliance function evidence, not conclusions. What your workflow does with an expired license or a lapsed registration is policy — yours to define, and easier to defend when the underlying record is traceable to its source.
Batch reconciliation that keeps your roster current
Point-of-onboarding checks catch problems at the door; the harder exposure is the roster you already have. Licenses expire, registrations lapse, disciplinary actions publish — and a credential verified at hire quietly stops being true. Continuous verification means re-checking the whole roster against refreshed public records on cadence, which is exactly the work nobody staffs manually.
The batch pattern handles it: your roster file in, a reconciliation report out — every credential re-verified against the current public record, with change flags on anything that moved since the last run. Cadence is set per source in scoping: daily where boards publish fast, weekly or monthly where they do not, so the promise matches the source's real rhythm. Scoping costs $500, credited to the contract, and returns feasibility plus a sample for your professions and states within 5 business days; contracts are fixed-price from $5,000.
What a delivery looks like
| Field | Description |
|---|---|
| license_identifier | The identifier exactly as issued by the licensing board. |
| licensee_name | Name as published on the license record. |
| profession_category | License type mapped to one controlled vocabulary across boards and states. |
| license_status | Active, expired, lapsed, suspended — normalized from each board's own status terms, with the as-published value retained. |
| issue_date | Original issuance date as the board publishes it. |
| expiration_date | Current expiry as published — the field most rosters silently drift on. |
| disciplinary_flag | Whether the public record shows disciplinary action, with the published detail attached. |
| issuing_jurisdiction | Board and state the record was collected from. |
| entity_registration_status | For business vetting: formation and standing as published in state filings. |
| capture_date | When this record was collected — the anchor for your audit trail. |