US Contractor License Search - Multi-State

Search public California and Oregon contractor-license records by business or person name. Export status, license number, type, location, and source URL. Results are returned as clean, typed dataset rows suitable for CSV, JSON, automation, and AI-agent workflows.

What data can I extract?

Key output fields include source, business_name, license_number, status, location, name_type. The dataset schema documents every field before a run starts.

All 45 columns

Identity — associated_individuals, assumed_business_names, bond_number, business_name, contractor_name, legal_name, license_number, name_type, residential_bond_amount, residential_bond_company, unpaid_civil_penalties, unpaid_claims

Status — additional_status, classifications, endorsement_type, entity_type, license_status_detail, status, workers_comp_status

Dates — date_first_licensed, expiration_date, expire_date, issue_date, reissue_date

Location — address, business_address, city

Money — bond_amount, bond_surety, bonding_information, commercial_bond_amount, commercial_bond_company, liability_amount

Contact — business_phone, phone

Other detail — administrative_suspensions, business_entity, complaint_history, disciplinary_history, lbpr_certified, liability_expiration, liability_insurer, miscellaneous_information, source, workers_comp_policy

Input example

{
  "search_terms": [
    "SMITH"
  ],
  "sources": [
    "california",
    "oregon"
  ],
  "max_items": 10
}

max_items is a hard output and billing ceiling. Source fields may be null when the upstream public record does not provide them.

Output example

Each dataset item is one normalized result. The field names shown under What data can I extract are emitted as typed JSON properties and can be exported as CSV, Excel, XML, or RSS.

Common use cases

• Lead, market, compliance, and competitive research
• Scheduled monitoring and change detection
• CSV/JSON enrichment pipelines
• AI-agent retrieval and workflow automation

Pricing and cost control

Output is billed per result at $0.003 per result (about $3.00 per 1,000 results), plus a $0.0005 Actor-start charge billed once per gigabyte of memory at run start. Use max_items to cap both output volume and charges. The price shown on the Apify Store listing is authoritative.

Use with AI agents and MCP

Apify's MCP server can discover and call this Actor. Example intent:

Verify public California and Oregon contractor-license records for a company name.

Use the JSON input above as the tool arguments, changing filters and max_items as needed. The strict input schema rejects unknown properties, and the typed dataset schema describes the returned tool data.

Reliability

Runs use bounded retries, deduplication, hard result limits, and explicit failure handling. Browser-based sources are monitored by contract canaries and staged selector repair; official-API sources use deterministic contract canaries rather than DOM repair.

Limitations and responsible use

• Publicly available source data only; coverage and field availability depend on the upstream source.
• A successful search can legitimately return no matching records.
• Point-in-time fields can change after collection.
• Use the data in accordance with applicable law and source terms.
• Do not use results for prohibited eligibility, discrimination, or sensitive-person profiling decisions.

FAQ

What search phrases does this Actor support?

The input schema lists exact accepted fields and examples. Primary discovery terms: contractor license lookup, CSLB scraper, Oregon CCB search, contractor verification API.

Can I control cost?

Yes. Set max_items; it is enforced as the maximum number of output records.

Can an AI agent call it?

Yes. Use Apify MCP search-actors, inspect this Actor's schema, then call it with the same JSON accepted in Console.

Does it require an external API key?

No external API key is required. Searches query official state licensing registries directly.

Changes

See ./CHANGELOG.md for contract and maintenance updates.