Contractor License Verification: Multi-State avatar

Contractor License Verification: Multi-State

Pricing

from $2.64 / 1,000 license verifications

Go to Apify Store
Contractor License Verification: Multi-State

Contractor License Verification: Multi-State

Verify contractor licenses across supported U.S. official state registries by license number or company name. Retain match evidence, source coverage, expiry fields, batch review rows, and explainable monitoring. $0.00352 per verification result.

Pricing

from $2.64 / 1,000 license verifications

Rating

0.0

(0)

Developer

GetAScraper

GetAScraper

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

βœ… Multi-state contractor license verifier

Contractor intelligence suite
Official-registry discovery and source-aware verification for U.S. contractor workflows.
πŸ—οΈ Contractor directory
Find published contractor records across supported registries.
βœ… License verifier
➀ You are here
Verify contractor license claims against published state records.
Match a license number or company name, retain official-source evidence, and review a batch through one repeatable workflow.
πŸ›οΈ Official evidence
Keep the public registry source beside each result.
🎯 Clear match basis
Separate license matches from company-name candidates.
πŸ“¦ Review-ready batch
Review up to 250 supplied checks in one run.
πŸ”” Explainable changes
See fields changed and cautious absence signals.

πŸ” What does multi-state contractor license verifier do?

Use this Actor to check a supplied license number or company name against supported public state registries. It returns a source-backed verification outcome, match basis, published contractor facts, and practical caveats.

⚑ Keep the evidence with the decision. Company-name matches are candidates, and every result keeps its public-source link and registry context.

πŸ‘₯ Who is it for?

  • Vendor-risk teams: β€œI need a consistent evidence trail before onboarding a contractor.”
  • General contractors: β€œI need to check a subcontractor list before work begins.”
  • Procurement teams: β€œI need to verify supplier claims without reviewing one registry at a time.”
  • Compliance teams: β€œI need a repeatable watchlist for records that may change.”

🧭 How it works

STEP 1
Add checks
Provide a state and a license number or company name.
STEP 2
Review evidence
Use the match basis, published facts, warnings, and source link.
STEP 3
Monitor changes
Schedule a stable batch to receive changed verified records.

βœ… Matching policy

A license-number match is stronger than a company-name candidate. Company-name searches return candidates, not identity claims. A capped or incomplete search does not make an absence claim. Review the returned warnings and source link before making a compliance decision.

πŸ—ΊοΈ Supported registry scope

StatePublished registry scope
ConnecticutHome-improvement credentials
IllinoisRoofing
OregonActive Construction Contractors Board licenses
TexasTDLR-regulated trades
WashingtonContractor registrations

🧾 Input

FieldTypeRequiredDescription
checksarray of checksNoUp to 250 named contractors or license numbers for batch verification. Every inputId must be unique.
checksCsvtextNoPasted CSV with inputId, state, licenseNumber, and companyName columns. It takes precedence over the JSON list.
stateenumNoState for one check: CT, IL, OR, TX, or WA.
licenseNumbertextNoPublished license or registration number for one check.
companyNametextNoPublished contractor name for candidate matching.
maxCandidatesPerCheckintegerNoMaximum source rows examined for each supplied contractor.
monitorModebooleanNoEmit new, field-level changed, or cautious missing-record signals after complete checks.
monitorNametextNoStable name for a saved verification batch.

Provide either checks, or a single state with a licenseNumber or companyName.

πŸ“Š Data table

FieldTypeDescription
inputIdtextYour supplied reference, copied to the result.
statetextRegistry state checked.
outcometextVerification outcome for the supplied check.
matchTypetextBasis of the returned match.
requestedLicenseNumber, requestedCompanyNametextSubmitted details retained with each review row.
candidateRank, candidateCountintegerDeterministic candidate position and total returned candidates for that input.
reviewRequired, reviewReasons, matchEvidenceboolean or array of textClear review guidance and the exact matching basis. No opaque score is used.
companyNametextContractor name published by the registry.
licenseNumbertextPublished license or registration number.
licenseStatustextPublished or inferred registry status when available.
licenseExpiresAtdatePublished expiry date when available.
tradeNamesarray of textPublished trade or specialty names when available.
sourceUrllinkOfficial-source query or record evidence.
warningsarray of textRegistry scope and result caveats.
monitoringChange, monitoringChangedFields, monitoringPreviousValues, monitoringReasontext, array, or objectExplainable monitoring result and prior published values when available.
sourceAttributesobjectAdditional published facts specific to the registry.

Empty fields are omitted. The Actor does not invent missing registry facts.

πŸ’° Pricing

Pricing is pay per result. Empty runs cost nothing, and there are no subscriptions.

⭐ Enjoying multi-state contractor license verifier?

⭐ ⭐ ⭐ ⭐ ⭐
Did this save your team from checking contractor licenses one at a time?
A rating helps procurement, compliance, and research teams find a source-backed verification workflow.
β˜…Β Β Rate this Actor on Apify

❓ FAQ

Which states can I verify at launch?

Connecticut, Illinois, Oregon, Texas, and Washington are supported. Each registry has its own published scope, shown above.

Does a company-name result prove the contractor’s identity?

No. Company-name searches return candidates. License-number matches carry stronger evidence. Use the official-source link and warnings for review.

Does no result mean a contractor is unlicensed?

No. A missing result can reflect registry scope, supplied information, or an incomplete search. The Actor avoids making that claim.

Can I monitor contractor records?

Yes. Turn on monitoring and use the same monitor name for a stable batch. Field changes include changed fields. The first complete-source absence is a review signal, and a second confirms the monitoring signal.

πŸ”— Other actors