ARES Czech Business Registry Scraper

Search the official Czech ARES business registry by company name or IČO and export clean company records from Apify.

What does ARES Czech Business Registry Scraper do?

ARES Czech Business Registry Scraper queries the Czech Ministry of Finance ARES registry API and saves normalized company data to an Apify dataset.

It supports company-name discovery and direct IČO lookup.

The actor is HTTP-only and uses the official JSON API.

It does not require a browser, login, CAPTCHA solving, or proxy configuration.

Who is it for?

KYB and KYC teams use it to verify Czech companies before onboarding.

B2B sales teams use it to enrich Czech lead lists with official identifiers and addresses.

Procurement teams use it to clean supplier master data.

Market researchers use it to find companies matching a Czech brand, sector, or name pattern.

Data engineers use it to turn ARES responses into a repeatable dataset export.

Why use this actor?

✅ Official source data from ARES.

✅ Search by company name or exact IČO.

✅ Normalized fields for addresses, legal form, registry status, and NACE codes.

✅ Source metadata included for audit trails.

✅ Conservative request delays for reliable batch runs.

✅ No browser overhead, so runs are fast and inexpensive.

What data can you extract?

The actor exports one row per Czech business entity.

Field	Description
ico	Czech company identification number
businessName	Registered business name
taxId	Czech VAT/tax identifier when available
legalForm	Legal-form code from ARES
primarySource	Primary ARES source registry
registrationDate	Company registration date
updatedAt	Last update date in the registry
addressText	Full registered address
region	Czech region
municipality	Municipality
naceCodes	CZ-NACE activity codes
registrationStatuses	Status values across ARES source registries
sourceRequestBody	Search request body used for the row

How much does it cost to scrape Czech ARES company data?

This actor uses pay-per-event pricing.

You pay a small start fee and a per-company result event.

The default input is intentionally small so first runs stay cheap.

Large batches should use maxResults and a conservative delayMillis value.

Input options

Use companyNames for discovery searches.

Use icos for exact Czech company lookup.

Use both when you want to enrich known companies and find adjacent matches in one run.

Set maxResults to cap total unique companies.

Set includeDetails to true when you want the per-IČO detail endpoint.

Set delayMillis higher for very large jobs.

Example input

{
  "companyNames": ["skoda", "alza"],
  "icos": ["00177041"],
  "maxResults": 100,
  "includeDetails": true,
  "delayMillis": 250
}

Output example

{
  "ico": "00177041",
  "businessName": "Škoda Auto a.s.",
  "taxId": "CZ00177041",
  "legalForm": "121",
  "primarySource": "ros",
  "registrationDate": "1990-11-20",
  "addressText": "tř. Václava Klementa 869, Mladá Boleslav II, 29301 Mladá Boleslav",
  "region": "Středočeský kraj",
  "municipality": "Mladá Boleslav",
  "naceCodes": ["29100", "45200"],
  "sourceType": "name_search"
}

How to scrape ARES by company name

1. Open the actor on Apify.

2. Add one or more values to companyNames.

3. Keep includeDetails enabled for richer output.

4. Set maxResults to your required limit.

5. Run the actor.

6. Export the dataset as JSON, CSV, Excel, XML, or RSS.

How to enrich a list of IČO numbers

1. Paste identifiers into icos.

2. Use values with or without spaces; the actor keeps digits and pads to 8 characters.

3. Leave companyNames empty if you only need exact lookups.

4. Run the actor.

5. Join the output back to your CRM, warehouse, or compliance workflow by ico.

Tips for reliable runs

Use short company-name terms for broad discovery.

Use exact company names or IČO values for precise enrichment.

Keep delayMillis at 250 ms or above for large recurring jobs.

Use start only when resuming name-search pagination.

Review sourceRequestBody when auditing why a row appeared in the dataset.

Integrations

Send the dataset to Google Sheets for a Czech prospecting list.

Send rows to a CRM enrichment workflow by IČO.

Use Apify webhooks to notify a compliance system when a run completes.

Load the dataset into BigQuery, Snowflake, or PostgreSQL for market analysis.

Combine this actor with company website scrapers for contact discovery.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/ares-czech-business-registry-scraper').call({
  companyNames: ['skoda'],
  maxResults: 50,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('MY-APIFY-TOKEN')
run = client.actor('automation-lab/ares-czech-business-registry-scraper').call(run_input={
    'companyNames': ['skoda'],
    'maxResults': 50,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~ares-czech-business-registry-scraper/runs?token=MY-APIFY-TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"companyNames":["skoda"],"maxResults":50}'

MCP integration

Use the actor from Claude Desktop or Claude Code through Apify MCP.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/ares-czech-business-registry-scraper

Claude Code setup:

$claude mcp add apify-ares-czech https://mcp.apify.com/?tools=automation-lab/ares-czech-business-registry-scraper

Claude Desktop JSON configuration:

{
  "mcpServers": {
    "apify-ares-czech": {
      "url": "https://mcp.apify.com/?tools=automation-lab/ares-czech-business-registry-scraper"
    }
  }
}

Example prompts:

• "Find Czech companies matching Skoda and summarize their registered addresses."

• "Enrich these IČO numbers with official ARES company names and NACE codes."

• "Create a CSV-ready Czech supplier master-data table from ARES."

Legality and compliance notes

ARES is an official public business registry.

Use exported data in accordance with applicable Czech, EU, and internal compliance rules.

Do not use registry data for spam, harassment, or unlawful profiling.

For regulated KYB/KYC use cases, keep the scrapedAt, sourceUrl, and source request metadata fields.

FAQ and troubleshooting

Why did I get fewer rows than expected?

ARES may have fewer matching companies than your maxResults, or duplicate IČO values may be removed across inputs.

Try a broader company-name term or increase start only when resuming a search.

Why is a legal form a code?

ARES returns legal-form codes. Keep the code for machine joins, or map it in your downstream system if you need localized labels.

Can I run thousands of records?

Yes, but keep the delay conservative and split very large enrichment lists into scheduled runs if needed.

Related scrapers

Explore other automation-lab actors for business enrichment workflows:

• https://apify.com/automation-lab/website-contact-finder

• https://apify.com/automation-lab/google-maps-lead-finder

• https://apify.com/automation-lab/company-domain-finder

• https://apify.com/automation-lab/linkedin-company-scraper

Data quality notes

The actor preserves ARES-provided codes and text.

It does not invent missing values.

When detail enrichment fails for one search hit, the actor keeps the search result instead of failing the full run.

Rows are de-duplicated by IČO.

Performance notes

The actor is API-based and normally runs quickly.

No proxy is required.

No browser memory is required.

The default memory is 256 MB.

Changelog

Initial version:

• Company-name search.

• Direct IČO lookup.

• Detail enrichment.

• Normalized dataset schema.

• Source metadata fields.