# Houzz Local Service Supply | Market Benchmarks (`jpmarketdata/houzz-local-service-supply-benchmark`) Actor

Benchmark Houzz local-service directory samples by trade and city. Compare review-count and rating distributions with explicit coverage and ranking bias. Aggregate-only output, no leads or contacts. $0.05 per completed directory report.

- **URL**: https://apify.com/jpmarketdata/houzz-local-service-supply-benchmark.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Real estate, Marketing, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$50.00 / 1,000 market report completeds

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

## Houzz Local Service Supply Benchmarks

Compare bounded first-page Houzz directory samples by trade and city. These reports measure observed directory representation and review signals, not total local supply, lead lists, business quality or customer demand.

**Price:** $0.05 per successful market report (`market-analyzed`).

### Input

Provide `directoryUrls`: one to three unique canonical US trade/city URLs containing `-us-probr0-bo~t_<tradeId>~r_<regionId>`. Use HTTPS on `www.houzz.com`. Profile, query/search, sort, pagination, fragment, API, template and cross-host URLs are rejected. Each accepted URL fetches one directory page and produces one report.

### Output

A `local_service_supply_market` row contains source URL, UTC observation time, market, trade, sampled/rated profile counts, known review-count count and zero-review count. `zeroReviewShare` is optional and uses only profiles with known review counts as denominator. Optional source `reportedTotalProfiles` describes Houzz's directory result, not a census or our sample. Optional `reviewCount` and `rating` objects contain count, min, p25, median, p75 and max; fields are omitted when no valid observations exist. Quartiles use linear interpolation at index `(n-1)*p`. Missing review counts or ratings are never coerced to zero. Optional `sponsoredProfiles` and `sponsorshipKnownProfiles` appear only when explicit source sponsorship status is consistently understood. `coverage=first-directory-page-sample` and `warnings` disclose organic ranking, paid placement, limited geographic coverage and missing values. Only profiles belonging to the main directory results count; recommendations/navigation do not. Dataset examples are synthetic, not live evidence.

### Pricing

Each successfully emitted directory benchmark triggers one `market-analyzed` event at $0.05. One to three unique directories cost up to $0.15 in actor events; source profiles are not individual billable results. Blocked/failed requests are not completed reports and are not charged. No actor-specific free trial is promised. Apify platform credits may apply; respect the maximum charge budget before starting another billable directory. Partial failure is reported explicitly and never replaced with an empty report.

### Limits

At most 3 source requests with no retries and a 180-second run budget. Requests are sequential with at least 3 seconds between them, a 30-second request timeout and 3 MB decoded response cap. No pagination or detail fetching. HTTP/JSON only, target 256 MB. Redirects are rejected. Empty or unrecognized results fail as a structure-change error; 403/auth/challenges, 429/rate limits and timeouts are distinct failures. A first page is neither random nor exhaustive; compare identical trade/geography and explain ranking bias. Source totals cannot be divided by population to infer density without separate validated denominators. Source review ratings use integer tenths of a star and are normalized to the 0–5 scale in output. Professionals present in both paid and organic placements are counted once, with sponsored status true.

### Privacy

Aggregate output only. No profile URLs, professional/person names, phone numbers, emails, street addresses, coordinates, photos, descriptions, review text, visitor IDs or session tokens are stored or logged. Process directory payloads transiently, allowlist numeric fields, and discard raw HTML/JSON. No contact enrichment or lead export.

# Actor input Schema

## `directoryUrls` (type: `array`):

1–3 canonical trade/city probr0 directory URLs. No profile, search, query, sort, pagination or API URLs.

## Actor input object example

```json
{
  "directoryUrls": [
    "https://www.houzz.com/professionals/interior-designer/new-york-city-ny-us-probr0-bo~t_11785~r_5128581"
  ]
}
```

# Actor output Schema

## `reports` (type: `string`):

No description

# 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("jpmarketdata/houzz-local-service-supply-benchmark").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("jpmarketdata/houzz-local-service-supply-benchmark").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 jpmarketdata/houzz-local-service-supply-benchmark --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/houzz-local-service-supply-benchmark"
        }
    }
}
```

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/ZSlb73EPyLatK0FJ7/builds/Mf3zySc464mJ1BqMX/openapi.json