# Arizona Contractor Complaints & Discipline Lookup (ROC) (`scrapebench/arizona-contractor-complaints-lookup`) Actor

Check any Arizona contractor's complaints, open and disciplined cases, bond and personnel from the ROC portal. One row per licence, by licence number, name or prefix.

- **URL**: https://apify.com/scrapebench/arizona-contractor-complaints-lookup.md
- **Developed by:** [ScrapeBench](https://apify.com/scrapebench) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.0025 / licence row

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Arizona Contractor Complaints & Discipline Lookup (ROC)

### Pain points

- Before hiring or insuring an Arizona contractor, the complaint history sits on the ROC portal one licence at a time, behind a search page and a detail page.
- A licence that reads Active can still carry open cases, a disciplinary suspension or a cancelled bond; the status alone does not say.
- Screening a whole list of subcontractors means opening hundreds of licence pages by hand.

### What we solve

- Type licence numbers, business names or a licence-number prefix and get one row per licence with its complaint cases, counts of open, disciplined and resolved cases, and a clear has_disciplinary_action flag.
- Filter a name or prefix search down to the contractors with open cases or discipline, and pay only for those rows.
- Each row also carries the bond (company, amount, status, payout) and the people on the licence with their roles.

### Summary

Arizona Registrar of Contractors complaint and discipline history, one row per licence. For every licence you get its status and the board's own account flag (for example Disciplinary Suspension), counts of open, disciplined and resolved cases, and each case: case number, status, type, outcome, allegations, case nature, closed and reopened dates and the jobsite city. Each row also carries the licence's bonds (type, status, company, number, amount, effective and cancellation dates, payout and available amount) and its personnel with roles, plus classification, qualifying party, entity type, phone, city, ZIP and the issue, renewal and status-change dates. Search by exact licence number, by business or person name, or by licence-number prefix, and keep only licences with any complaint, an open case or discipline. The complainant is a private person and is not delivered. A number the portal does not list, a portal that does not answer and a search that hit the portal's own limit each come back as a free note, never as a quiet zero.

### Who it's for

- General contractors and property managers screening subcontractors before they sign
- Insurance and surety underwriters checking a contractor's record
- Homeowners' advisors, real estate and remodel marketplaces verifying a contractor
- Compliance and legal teams monitoring disciplined or suspended Arizona licences

### How to use

Set the input, run the actor, and collect results from the run's dataset (export to JSON/CSV/Excel, or pull via the Apify API). Example input:

```json
{
  "licenseNumbers": [
    "336584",
    "336591",
    "333656"
  ],
  "maxResults": 10
}
```

See **Inputs** below for every available field.

### What you get

One row per record:

| Field | Description |
|---|---|
| `license_number` | ROC licence number, six digits |
| `business_name` | Licensed business name |
| `license_status` | Active, Suspended, Revoked, Expired and so on |
| `account_status` | The board's account flag, for example Disciplinary Suspension; empty when none |
| `has_complaints` | True when the ROC lists at least one case |
| `has_disciplinary_action` | True for a disciplined case or a Disciplinary account status |
| `complaint_count` | Number of cases listed |
| `open_cases` | Open cases, appeals included |
| `disciplined_cases` | Cases closed with discipline |
| `resolved_cases` | Cases resolved or settled |
| `complaints` | Each case: number, status, type, outcome, allegations, nature, closed and reopened dates, jobsite city |
| `bonds` | Each bond: type, status, number, company, amount, dates, payout, available |
| `personnel` | People and parent entities on the licence with their role |
| `classification` | ROC class code, for example CR-48 |
| `qualifying_party` | Person qualifying the licence |
| `entity_type` | LLC, Corporation and so on |
| `phone` | Business phone |
| `city` | City |
| `zip_code` | ZIP code |
| `issue_date` | Licence issue date, YYYY-MM-DD |
| `renewed_through` | Renewal date, YYYY-MM-DD |
| `source_url` | The licence page on the ROC contractor search |

Sample:

```json
{
  "state": "AZ",
  "license_number": "336591",
  "business_name": "SSE Construction LLC",
  "dba_name": null,
  "classification": "B-3",
  "classification_detail": "B-3 General Residential B-3 General Remodeling and Repair Contractor",
  "license_status": "Suspended",
  "account_status": "Disciplinary Suspension",
  "qualifying_party": "Jeffrey Lewis Blanchard",
  "entity_type": "LLC",
  "phone": "(480) 955-4744",
  "city": "Phoenix",
  "zip_code": "85040",
  "issue_date": "2022-02-09",
  "renewed_through": "2026-02-28",
  "status_changed_date": "2025-11-19",
  "has_complaints": true,
  "has_disciplinary_action": true,
  "complaint_count": 2,
  "open_cases": 0,
  "disciplined_cases": 1,
  "resolved_cases": 1,
  "complaints": [
    {
      "case_number": "2025-09954",
      "status": "Closed",
      "case_type": "Disciplined",
      "outcome": "Legal - Suspended",
      "allegations": "No-Pay for Services or Materials",
      "case_nature": "Legal",
      "closed_date": "2025-11-19",
      "reopened_date": null,
      "jobsite_city": null,
      "jobsite_state": "AZ"
    }
  ],
  "personnel": [
    {
      "name": "Jeffrey Lewis Blanchard",
      "role": "Qualifying Party"
    }
  ],
  "bonds": [
    {
      "bond_type": "Surety",
      "status": "Cancelled",
      "bond_number": "LSM1581771",
      "company": "RLI Insurance Company",
      "amount": 9000.0,
      "effective_date": "2021-12-30",
      "cancellation_date": "2026-01-29",
      "total_payout": 0.0,
      "available": 9000.0
    }
  ],
  "matched_by": "license_number",
  "source_url": "https://azroc.my.site.com/AZRoc/s/contractor-search?licenseId=a0o8y0000009r3tAAA"
}
```

### Inputs

| Field | Required | Type | Default | Description |
|---|---|---|---|---|
| `licenseNumbers` | no | array | `[]` | Exact ROC licence numbers, one per line ('336584' or 'ROC 336584'; leading zeros are handled). A number the portal does not list returns a free note, never a near match. |
| `licenseNumber` | no | string | — | One licence number. Kept for callers that send a single value; combined with the list above. |
| `queries` | no | array | `[]` | One search per line: a business name ('Arcadia Roofing'), a person's name written FIRST then LAST, or a licence-number prefix ('3365' = every licence starting 3365). Every licence on every account found is checked. The portal's search stops near 1,000 accounts; a search that reaches it says so in a free note. |
| `query` | no | string | — | One search. Kept for callers that send a single value; combined with the list above. |
| `complaintFilter` | no | string | `"all"` | Only the licences that match are returned and charged; the rest are checked and dropped. Use 'disciplined' on a name or prefix search to find the contractors with discipline. |
| `maxResults` | no | integer | `50` | A run-wide cap on the licence rows returned (and charged), after the filter above. At most 2,000 licences are checked per run. |

### Pricing (Pay Per Event)

You pay per result (`dataset-item`) — **no charge for empty runs**. Example: **100 licences** at *$0.0025/result* ≈ **$0.25**.

You pay per licence row delivered, nothing per run. With 'Keep only' set to disciplined or open, only the matching licences are returned and charged. Free notes are never charged.

### Use cases

- Subcontractor screening: run your vendor list by licence number and see open cases, discipline and bond status.
- Discipline sweep: search a name or licence-number prefix with 'Keep only' set to disciplined to list contractors with discipline.
- Underwriting: bond status, cancellation dates and payout next to the complaint count.
- Due diligence on a business: its licences, qualifying party and the people and parent entities attached.

### Why this actor

- Complaint cases, counts, discipline flag, bond and personnel in one row.
- Exact licence-number matching: a number returns that licence or a free note, never a neighbour.
- Filter to open or disciplined licences and pay only for those rows.
- No private complainant names; a portal that fails is a free note, never a clean record.

### Limitations & updates

Arizona only. Returns the cases the ROC portal lists for a licence; it does not list the full file. A name or prefix search is limited by the portal to about 1,000 accounts and at most 2,000 licences are checked per run. Cases carry the board's own case type (Open, Resolved / Settled, Disciplined); the complainant is not delivered.

### FAQ

**What counts as a disciplinary action?**

has_disciplinary_action is true when a case closed with discipline, or when the board's own account status reads Disciplinary (for example Disciplinary Suspension). Both are shown in the row so you can apply your own rule.

**Does a licence with no cases mean a clean record?**

It means the ROC portal lists no cases for that licence today. The portal decides which cases it publishes; we return what it lists.

**Why is there no complainant name?**

The complainant is a private person. The case number, allegations, outcome and dates are delivered; the person is not.

**How do I find the contractors with discipline?**

Search a name or a licence-number prefix (for example 3365) and set 'Keep only' to disciplined. Every licence found is checked and only the matching ones are returned and charged. The portal's search stops near 1,000 accounts, and a search that reaches it says so.

**What if the portal does not answer?**

You get a free note and the licence is left out, never shown as having no complaints. Run it again.

**Is there a Michigan or other state version?**

Not yet. Arizona is the one state whose board publishes structured case data through its search portal. Other boards show a licence status only, which the licence lookup actors already return.

### Which actor to choose

Part of the contractor-data suite — pick the one that fits your goal:

- **Arizona Contractor License Lookup & Leads Scraper (ROC)** — You need the licence list itself: every active Arizona contractor with phone and address, or a lookup by name.
- **US Contractor License Lookup & Verification** — You verify contractors across many states in one run.

### Guides & use cases

Written up on **[scrapebench.dev](https://scrapebench.dev)** — the bench that runs and verifies this actor against the live source every night:

- **How-to:** [How to run Arizona Contractor Complaints & Discipline Lookup (ROC)](https://scrapebench.dev/guides/how-to-arizona-contractor-complaints-lookup/)
- **Use case:** [Screen your Arizona subcontractors for complaints and discipline](https://scrapebench.dev/use-cases/screen-arizona-subcontractors-for-complaints/)

More actors, coverage and nightly verification results: **[scrapebench.dev](https://scrapebench.dev)**

### Works with AI assistants (MCP)

Callable as an MCP tool, so Claude, Cursor, VS Code Copilot and other MCP clients can run it directly. Grab the config from the [MCP tab](https://apify.com/scrapebench/arizona-contractor-complaints-lookup/api/mcp) on this page — Apify hosts the server and keeps that snippet current, and OAuth signs you in on first connect, so no API token goes in your config file.

Then just ask:

> "Check Arizona ROC licences 336584, 336591 and 333656 for complaints: run the Arizona contractor complaints lookup with those licence numbers and tell me which have open cases or discipline."

That input returned licence 336591 with a disciplined case and a Disciplinary Suspension status on 2026-11-16. Runs started this way bill exactly like any other run.

### Data & lawful use

This actor collects publicly available information that the Arizona Registrar of Contractors (ROC) publishes for public
lookup — licence records, business listings and the contact details professionals list there.
Some of it identifies individuals (sole proprietors, licence holders, agents), so treat any
names, phone numbers and emails in your results as personal data.

When you run this actor, you decide what is collected and what it is used for, so you are the
controller of that data and we act only as your processor (Apify Standard Actor Contract).
You need a lawful basis for your use, must honour opt-out and deletion requests, and must
follow the marketing rules that apply to you (CAN-SPAM, TCPA, GDPR, CCPA and similar).
Don't use the output for unsolicited bulk messaging, for screening covered by the FCRA, or
for anything the source's own terms forbid.

Your results are stored in your own Apify account. We don't keep a copy of your results and
don't sell or share them.

### Disclaimer

This is an independent tool. It is not affiliated with, endorsed by or sponsored by
the Arizona Registrar of Contractors (ROC). Names and marks are used only to describe the data source. Records are
provided as published by the source and may be out of date or incomplete. For anything
consequential (hiring, a permit, a legal decision), confirm the record with the issuing
agency. You are responsible for making sure your use complies with applicable law and the
source's terms.

### Need help?

Open an issue on this actor's **Issues** tab and we'll respond there. Bug reports, missing
fields and feature requests are all welcome. Guides and examples: [scrapebench.dev](https://scrapebench.dev).

If you are a person named in this data and want your record removed from our copy, email
apify-help@scrapebench.dev; the source agency remains the official record.

Your run may be used to improve our services. If something looks off, or you want this actor to fit your use better, please share your run data with us: [Apify Console → Settings → Security → Share run data with developers](https://console.apify.com/settings/security). It lets us see exactly what went wrong and keep improving the actor.

If this actor saved you time, a short review on its Store page helps other buyers find it.

# Actor input Schema

## `licenseNumbers` (type: `array`):

Exact ROC licence numbers, one per line ('336584' or 'ROC 336584'; leading zeros are handled). A number the portal does not list returns a free note, never a near match.

## `licenseNumber` (type: `string`):

One licence number. Kept for callers that send a single value; combined with the list above.

## `queries` (type: `array`):

One search per line: a business name ('Arcadia Roofing'), a person's name written FIRST then LAST, or a licence-number prefix ('3365' = every licence starting 3365). Every licence on every account found is checked. The portal's search stops near 1,000 accounts; a search that reaches it says so in a free note.

## `query` (type: `string`):

One search. Kept for callers that send a single value; combined with the list above.

## `complaintFilter` (type: `string`):

Only the licences that match are returned and charged; the rest are checked and dropped. Use 'disciplined' on a name or prefix search to find the contractors with discipline.

## `maxResults` (type: `integer`):

A run-wide cap on the licence rows returned (and charged), after the filter above. At most 2,000 licences are checked per run.

## Actor input object example

```json
{
  "licenseNumbers": [],
  "licenseNumber": "336584",
  "queries": [],
  "query": "Arcadia Roofing",
  "complaintFilter": "all",
  "maxResults": 50
}
```

# Actor output Schema

## `results` (type: `string`):

One row per licence: status, counts, complaint cases, bond and personnel.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapebench/arizona-contractor-complaints-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapebench/arizona-contractor-complaints-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call scrapebench/arizona-contractor-complaints-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapebench/arizona-contractor-complaints-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Vn0S6Si1qKQ1VHh5e/builds/a3RaUH6bzj7bnNX5t/openapi.json
