# Clutch Agencies Scraper (`dami_studio/clutch-agencies-scraper`) Actor

Turn any public Clutch directory page into B2B lead rows: agency name, profile URL, website, city and country, hourly rate band, minimum project size, team size, star rating, review count and the service lines the agency lists.

- **URL**: https://apify.com/dami\_studio/clutch-agencies-scraper.md
- **Developed by:** [Dami's Studio](https://apify.com/dami_studio) (community)
- **Categories:** Lead generation, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 agency profiles

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Clutch Agencies Scraper

Extract public Clutch directory listings into structured agency lead rows. Each genuine agency row can include its name, public profile URL, visible location, rating, review count, displayed project minimum, hourly rate, team size, and visible service links.

### Input example

```json
{
  "directoryUrls": ["https://clutch.co/ca/web-developers/toronto"],
  "maxAgenciesPerDirectory": 25,
  "enableResidentialFallback": false
}
```

Use public category and location directory pages copied from Clutch. This actor does not scrape authenticated pages, bypass access controls, or claim hidden contact data.

### Cost and proxy policy

The actor tries direct HTTP first. If and only if one directory returns a block or rate-limit response, `enableResidentialFallback` permits one bounded proxy HTTP retry for the whole run. The retry goes out over rotating datacenter addresses. Metered Apify groups (Residential, Google SERP) are not offered by this actor and are replaced with datacenter automatically; your own servers passed in `proxyUrls` are used exactly as given.

Only rows parsed as real agency records trigger the `agency` event. Invalid input, no results, blocked pages, errors, and the empty-input sample are never charged.

### Empty input

Running with no `directoryUrls` returns one labeled `_sample: true` row. It is illustrative only and uncharged.

### Output

Every real row includes the source `directoryUrl`, `profileUrl`, and `transport` (`direct_http`, `datacenter_http`, or `customer_http`). Fields that Clutch does not visibly provide are `null`; the actor does not guess values.

### Local validation

```powershell
npm install --omit=dev --no-audit --no-fund
npm test
npm run check
```

### Billing

`$0.003` to start a run, then `$0.0008` per agency — `$0.80` per 1,000 agencies.

Only rows parsed as a real agency profile are charged. Invalid input, directories that return nothing, blocked pages, errors and the empty-input sample row are all free.

# Actor input Schema

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

Public Clutch directory URLs such as https://clutch.co/ca/web-developers/toronto. Empty input returns one uncharged sample row.

## `maxAgenciesPerDirectory` (type: `integer`):

Maximum public agency rows to return from each directory URL. The limit keeps compute and optional proxy exposure bounded.

## `enableResidentialFallback` (type: `boolean`):

After a direct 403 or rate limit, retry at most one directory through a proxy. The retry uses rotating datacenter addresses; metered groups (Residential, Google SERP) are not offered by this actor.

## `proxyConfiguration` (type: `object`):

Used only for the single blocked-directory retry. This actor uses rotating datacenter addresses; metered groups (Residential, Google SERP) are not offered and are replaced with datacenter automatically. Your own proxy servers listed in proxyUrls are used exactly as given.

## Actor input object example

```json
{
  "directoryUrls": [],
  "maxAgenciesPerDirectory": 25,
  "enableResidentialFallback": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "BUYPROXIES94952"
    ]
  }
}
```

# Actor output Schema

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

One dataset row per public Clutch directory agency. Empty, invalid, blocked, and no-result runs return only uncharged sample or diagnostic rows.

# 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("dami_studio/clutch-agencies-scraper").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("dami_studio/clutch-agencies-scraper").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 dami_studio/clutch-agencies-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dami_studio/clutch-agencies-scraper"
        }
    }
}

```

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/raAMPBCScI52m245E/builds/JHXzQTAZRHQomEhvQ/openapi.json