Poland CRBR Beneficial Owners Scraper

Extract structured beneficial ownership data from Poland's public Central Register of Beneficial Owners (CRBR). Search by company name, NIP, KRS, PESEL, or beneficiary name and export compliance-ready data for AML, KYC, KYB, due diligence, and investigations.

What does Poland CRBR Beneficial Owners Scraper do?

Poland CRBR Beneficial Owners Scraper turns public CRBR searches into structured dataset rows. It helps you collect company identity, beneficial-owner identity, control rights, filing evidence, and source metadata without manual copy-paste from the public registry.

Example input

{
  "searches": [
    { "mode": "companyName", "query": "ORLEN" },
    { "mode": "nip", "query": "7742894628" },
    { "mode": "beneficiaryPesel", "query": "73110202448" }
  ],
  "maxResults": 25
}

Example output

{
  "recordType": "beneficial_owner",
  "searchMode": "companyName",
  "sourceQuery": "ORLEN",
  "found": true,
  "companyName": "ORLEN ADMINISTRACJA SP. Z O.O.",
  "nip": "7742894628",
  "krs": "0000252883",
  "legalForm": "Spółka z ograniczoną odpowiedzialnością",
  "companyAddress": "CHEMIKÓW 7, 09-411, PŁOCK, PŁOCK, PŁOCK, MAZOWIECKIE",
  "beneficiaryFullName": "MAŁGORZATA DANUTA GOŁUCHOWSKA",
  "beneficiaryPesel": "73110202448",
  "beneficiaryCitizenships": ["PL - POLSKA"],
  "beneficiaryResidenceCountry": "PL - POLSKA",
  "controlType": "osoba fizyczna zajmująca wyższe stanowisko kierownicze, o której mowa w art. 2 ust. 2 pkt.1 lit. a tiret 5 ustawy AML",
  "controlTypeCode": "002",
  "rightsSummary": "osoba fizyczna zajmująca wyższe stanowisko kierownicze, o której mowa w art. 2 ust. 2 pkt.1 lit. a tiret 5 ustawy AML",
  "requestId": "7A7C490EFF8C49A99D544269C26675C6",
  "presentationStart": "2026-07-09",
  "presentationEnd": "2026-07-09",
  "sourceUrl": "https://crbr.podatki.gov.pl/adcrbr/#/wyszukaj",
  "retrievedAt": "2026-07-09T21:12:44.000Z"
}

Who is it for?

• AML and KYC teams checking beneficial ownership of Polish companies.
• KYB onboarding teams enriching customer files with official-source ownership data.
• Compliance, legal, and finance teams building audit evidence.
• Investigators, journalists, and data teams researching Polish corporate control.

Use cases

• Verify UBO declarations before onboarding a Polish counterparty.
• Batch-check NIP or KRS identifiers from a customer portfolio.
• Search company names to discover matching CRBR entries.
• Collect source request IDs and presentation periods for audit trails.
• Export beneficial-owner rows to CSV, Excel, JSON, webhooks, or data warehouses.

Output fields

• Company identity: name, NIP, KRS, legal form, registered address
• Beneficial owner identity: names, PESEL or birth date when returned publicly, citizenship, residence country
• Control details: control basis, AML wording, ownership amount/unit, indirect control and privileges when available
• Filing evidence: CRBR request ID, presentation dates, correction flag, discrepancy count, source URL
• Representatives who filed the declaration, with roles when returned by CRBR
• Error/not-found rows for auditable batch checks

Input settings

Field	Type	Description
searches	array	Search requests. Each request has mode and query.
searches[].mode	string	companyName, nip, krs, beneficiaryPesel, or beneficiaryName.
searches[].query	string	Company name, NIP, KRS, PESEL, or beneficiary name.
searches[].firstName / lastName	string	Optional overrides for beneficiary-name searches.
searches[].pesel	string	Optional exact PESEL override for beneficiary searches.
searches[].birthDate	string	Optional YYYY-MM-DD birth date for beneficiary-name searches.
maxResults	integer	Maximum dataset rows to save.
dateFrom, dateTo	string	CRBR presentation period. Defaults to today.
requestDelayMs	integer	Polite delay between searches.
includeRaw	boolean	Include raw CRBR fragments for audit/debug exports.

Input recipes

Search by company name

{
  "searches": [{ "mode": "companyName", "query": "ORLEN" }],
  "maxResults": 25
}

Exact company check by NIP or KRS

{
  "searches": [
    { "mode": "nip", "query": "7742894628" },
    { "mode": "krs", "query": "0000252883" }
  ],
  "maxResults": 10
}

Beneficiary check by PESEL

{
  "searches": [{ "mode": "beneficiaryPesel", "query": "73110202448" }],
  "maxResults": 10
}

Pricing

This actor uses pay-per-event pricing:

• Actor start: $0.005 per run
• CRBR result row: tiered by Apify public usage plans. The Starter / Bronze reference price is $0.0001 per saved dataset row (about $0.10 per 1,000 rows).

Tier	Result row price
Free	$0.000115
Starter / Bronze	$0.0001
Scale / Silver	$0.000078
Business / Gold	$0.00006
Custom / Platinum	$0.00004
Custom / Diamond	$0.000028

Use maxResults to control cost for broad company-name searches.

Tips and limits

• Use NIP, KRS, or PESEL for exact checks.
• Use company-name searches for discovery, then re-run exact identifiers for audit files.
• Beneficiary-name searches may require birth-date context depending on CRBR validation rules.
• Empty, invalid, or no-match searches are saved as not_found or error rows so batch audits remain traceable.

Legality and responsible use

Poland's CRBR is a public beneficial-ownership register, but results can include personal data such as names, citizenship, residence country, birth dates, or PESEL values when the public service returns them. Use this actor only for lawful purposes such as AML/KYC/KYB checks, due diligence, compliance audits, journalism, public-interest research, or other legitimate uses. You are responsible for having an appropriate legal basis, following applicable data-protection rules, limiting retention and sharing, and respecting CRBR portal terms and Polish/EU law.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/poland-crbr-beneficial-owners-scraper').call({
  searches: [{ mode: 'companyName', query: 'ORLEN' }],
  maxResults: 20,
});

console.log(`Dataset: https://api.apify.com/v2/datasets/${run.defaultDatasetId}/items`);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('fetch_cat/poland-crbr-beneficial-owners-scraper').call(run_input={
    'searches': [{'mode': 'companyName', 'query': 'ORLEN'}],
    'maxResults': 20,
})

print(f"Dataset: https://api.apify.com/v2/datasets/{run['defaultDatasetId']}/items")

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~poland-crbr-beneficial-owners-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"searches":[{"mode":"companyName","query":"ORLEN"}],"maxResults":20}'

MCP and agent usage

Connect AI agents through Apify MCP using:

https://mcp.apify.com/?tools=fetch_cat/poland-crbr-beneficial-owners-scraper

Claude CLI

$claude mcp add apify-crbr --url "https://mcp.apify.com/?tools=fetch_cat/poland-crbr-beneficial-owners-scraper"

JSON config

{
  "mcpServers": {
    "apify-crbr": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/poland-crbr-beneficial-owners-scraper"
    }
  }
}

Example prompts

• "Search CRBR for ORLEN and summarize the beneficial-owner rows."
• "Check this list of KRS numbers and return companies with missing CRBR matches."
• "Prepare a KYB evidence table with request IDs and presentation dates."

Useful agent tasks include company onboarding checks, UBO enrichment, batch KYB preparation, and audit evidence collection.

Related actors

• Poland KRS Company Registry Scraper - company registry records from KRS
• Google Maps Reviews Scraper - local business review extraction

FAQ

Does this require a login?

No. It reads Poland's public CRBR register.

Does it return full PESEL values?

The actor returns values present in the public CRBR response. Handle personal data responsibly and in line with applicable law.

Can I run batches?

Yes. Add multiple objects to searches and set maxResults to your desired export size.

What happens when a query is invalid?

The actor saves an error row with the CRBR validation message instead of crashing the whole batch.

Support

Questions, feature requests, or run issues? Open an issue from the actor page on Apify and include:

• Run ID or reproducible public URL
• Input JSON (remove private batch data if needed)
• Expected output
• Actual output or error message
• Whether the same query works in the public CRBR portal