# Firmy.cz Scraper — Czech Business Directory | from $2/1K (`bovi/firmy-cz-scraper`) Actor

Scrape Firmy.cz Czech business directory by keyword, category and region. Returns name, address, phone, email, website, rating, opening hours and more. Pay per result.

- **URL**: https://apify.com/bovi/firmy-cz-scraper.md
- **Developed by:** [Vitalii Bondarev](https://apify.com/bovi) (community)
- **Categories:** Lead generation, Business, Automation
- **Features:** Limited permissions
- **Stats:** 21 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.94 / 1,000 business-items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Firmy.cz Scraper — Czech Business Directory, Contacts

Extract Czech business listings from [Firmy.cz](https://www.firmy.cz) (the leading Czech business directory, operated by Seznam.cz).

### What you get

| Field | Description |
|-------|-------------|
| `id` | Firmy.cz premise ID |
| `name` | Business name |
| `category` | Primary business category (Czech) |
| `phone` | Phone number |
| `email` | Email address |
| `website` | Business website (clean, no UTM params) |
| `street` | Street address |
| `city` | City / district |
| `postalCode` | 5-digit Czech postal code |
| `lat` / `lng` | GPS coordinates |
| `rating` | Rating score 0–100 (Firmy.cz scale) |
| `reviewCount` | Number of reviews |
| `openingHours` | Opening hours string |
| `description` | Business description |
| `businessUrl` | Canonical Firmy.cz listing URL |

### Use cases

- **B2B lead generation** in Czechia — phone + email lists by category and city
- **Market research** — find competitors, suppliers, service providers
- **Sales prospecting** — restaurants, contractors, dentists, law firms, etc.

### Input

```json
{
  "query": "restaurace",
  "locality": "Praha",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "CZ"
  }
}
```

| Parameter | Required | Default | Description |
|-----------|----------|---------|-------------|
| `query` | Yes | — | Czech keyword (e.g. `restaurace`, `instalatér`, `zubař`) |
| `locality` | No | — | City or region (e.g. `Praha`, `Brno`). Leave empty for nationwide. |
| `maxItems` | No | 100 | Max results. `0` = all available. |
| `proxyConfiguration` | No | RESIDENTIAL/CZ | Apify proxy settings. |

### Output sample

```json
{
  "id": "12345678",
  "name": "Restaurace U Zlatého Kohouta",
  "category": "Restaurace",
  "phone": "+420 222 111 000",
  "email": "info@kohoutu.cz",
  "website": "https://www.kohoutu.cz",
  "street": "Václavské náměstí 15",
  "city": "Praha 1",
  "postalCode": "11000",
  "lat": 50.0808,
  "lng": 14.4259,
  "rating": 84,
  "reviewCount": 312,
  "openingHours": "Po–Pá 11:00–23:00, So–Ne 12:00–23:00",
  "description": "Tradiční česká kuchyně v centru Prahy.",
  "businessUrl": "https://www.firmy.cz/detail/12345678-restaurace-u-zlateho-kohouta-praha.html",
  "parse_confidence": 0.97
}
```

### Pricing

Pay-per-result: **$2 per 1 000 businesses** extracted.

### Technical notes

- Scrapes Firmy.cz search results (SSR HTML with embedded JSON-LD) + detail pages
- Access: lightweight HTTP requests — no heavy browser needed; handles the CMP consent gate automatically
- Polite 1.2s delay between requests
- RESIDENTIAL CZ proxy recommended for cloud runs

### More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

- [Gelbeseiten Directory](https://apify.com/bovi/gelbeseiten-directory)
- [Google Maps Leads](https://apify.com/bovi/google-maps-leads)
- [Google Maps Scraper](https://apify.com/bovi/google-maps-scraper)
- [Hiring Signal Monitor](https://apify.com/bovi/hiring-signal-monitor)
- [Linkedin Profile Scraper](https://apify.com/bovi/linkedin-profile-scraper)
- [PagesJaunes Directory Scraper](https://apify.com/bovi/pagesjaunes-directory)

Chain any of them together from the **Integrations** tab (the *Run succeeded* trigger) to build a multi-step workflow — one actor's output feeds the next.

### Rate this Actor

If Firmy.cz Scraper saved you time, please rate it on the Apify Store. A rating takes a few seconds and helps other people find a working scraper. If something did not work, open an issue on the Actor page and we will fix it.

### Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as `USAGE_STATS` in your own Apify key-value store, so you can see the exact record created for your run.

Set `disableUsageStats` to `true` in the input to opt out. Nothing is sent then; your `USAGE_STATS` record only says that statistics were disabled.

Only these fields are recorded:

- schema version, Actor name and build number;
- UTC start and finish hour (not a precise timestamp);
- run duration, number of results and time to the first result, each as a coarse range;
- whether the result was empty, the end status, and an error type from a fixed list;
- memory setting and counts of charged events;
- names of the input fields you set, never their values;
- the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

#### Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same `disableUsageStats: true` input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

#### Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

- the result limit you asked for (a range, when the input has one) and what share of it was delivered;
- results delivered per input item you listed (a range);
- output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
- how the run was started (console, API, schedule, webhook, another Actor);
- how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
- if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
- a short code made from the names of the input fields you set, never their values.

#### Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and `disableUsageStats: true` turns it off.

# Actor input Schema

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

Business keyword to search for (Czech, e.g. restaurace, instalatér, zubař, advokát). This is the 'what' search term.

## `locality` (type: `string`):

City or region to search in (e.g. Praha, Brno, Ostrava). Leave empty to search nationwide.

## `maxItems` (type: `integer`):

Maximum number of business listings to return. Each result = one PPE charge ($2/1K). Set 0 for all available results. Default: 100.

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

Apify proxy settings. RESIDENTIAL group recommended for best reliability. CZ country code preferred.

## `disableUsageStats` (type: `boolean`):

See the README Usage statistics section for details.

## Actor input object example

```json
{
  "query": "instalatér",
  "locality": "Brno",
  "maxItems": 200,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CZ"
  },
  "disableUsageStats": false
}
```

# Actor output Schema

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

Dataset containing Firmy Cz Scraper records (name, category, phone, email, website, street, city, postalCode, rating, reviewCount, businessUrl, parse_confidence).

# 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 = {
    "query": "restaurace",
    "locality": "Praha",
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "CZ"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("bovi/firmy-cz-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 = {
    "query": "restaurace",
    "locality": "Praha",
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "CZ",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("bovi/firmy-cz-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 '{
  "query": "restaurace",
  "locality": "Praha",
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CZ"
  }
}' |
apify call bovi/firmy-cz-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bovi/firmy-cz-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/1n8cdRohQYrKzblj1/builds/vIxdnAfL5DRfRNwK1/openapi.json