Poland KRS Company Registry Scraper

Look up public Polish KRS company registry records by KRS number and export company identity, NIP, REGON, addresses, representatives, business activities and share capital. Use known registration numbers for company-list enrichment and registry checks. This Actor does not search by company name or discover all companies.

Quick start

1. Paste KRS numbers into KRS numbers or KRS numbers as text.
2. Choose register P for entrepreneurs or S for associations and foundations.
3. Start the Actor and open its dataset. Download JSON, CSV or Excel from Apify.

{
  "krsNumbers": ["0000123456"],
  "register": "P"
}

Available fields depend on the public registry extract. A successful lookup is not a legal assessment of whether a business is operating, solvent or safe to trade with.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

What you get

One lookup-outcome row for each unique requested KRS number, with a returned public extract or not_found/error status. Successful extracts can include registry identity, addresses, representatives, activities and capital. Active means an extract was returned rather than certified operating or legal status, while missing fields remain null or empty.

Who is it for?

• Company-data teams enriching known Polish registration numbers.
• Registry researchers inspecting published identities and representatives.
• Business analysts reviewing available PKD activities and capital fields.
• Data developers reconciling structured lookup outcomes in their own records.

How you can use the data

• Inspect one known entrepreneur-register number. Use the existing 0000123456 example with register P. Retain KRS, NIP, REGON and source URL where returned, without treating active as proof of solvency, operating status or safe trading.
• Reconcile a small spreadsheet list. Use the existing text input 123456 and 247804 with register P and raw extracts off. Numbers are normalized to ten digits and duplicates queried once. Keep not_found and error outcomes separate rather than assuming every row is a successful company.
• Choose a register before collection. Supply a known association or foundation KRS with S, in a separate appropriately scoped input. The selected register applies to the whole run and does not search both registers automatically.
• Review source details in your own system. Enable rawOdpis when the official returned object is needed beside normalized representatives, activities and capital. Preserve source dates and inspect registry-masked names rather than filling gaps. Historical comparison, legal assessment and monitoring remain separate work.

Input settings

Paste several numbers from a spreadsheet:

{
  "krsNumbersText": "123456\n247804",
  "register": "P",
  "includeRawOdpis": false
}

For an association or foundation, provide its KRS number and set register to S. The selected register applies to every number in that run. The Actor does not search both registers automatically.

More input

Setting	API key	Purpose
KRS numbers	krsNumbers	List of registration numbers. Leading zeros are optional.
KRS numbers as text	krsNumbersText	Paste numbers separated by whitespace, commas or semicolons.
KRS register	register	P for entrepreneurs (default), or S for associations/foundations.
Include raw KRS response	includeRawOdpis	Add the official odpis object to successful records. Off by default.
Maximum concurrency	maxConcurrency	Parallel lookups, from 1 to 5. Default 2.
Delay before lookup	delayMs	Wait before each lookup. Default 250 milliseconds.

At least one number is required across the list and text fields. The Actor combines them, normalizes numbers to ten digits and looks up duplicates once. Input-field help explains individual settings and limits.

Output data

Each unique requested number produces a dataset row with status equal to active, not_found or error. Here, active means that a registry extract was returned, not a verified legal or operating status. Unavailable fields are null or empty lists.

This abbreviated, shape-only example illustrates field types, not a live company record:

{
  "krsNumber": "0000123456",
  "register": "P",
  "legalName": null,
  "nip": null,
  "regon": null,
  "address": null,
  "status": "not_found",
  "representatives": [],
  "shareholdersOrPartners": [],
  "businessActivities": [],
  "shareCapital": null,
  "errorMessage": "KRS number was not found in the selected register."
}

Fields	Contents
krsNumber, register	Normalized number and the selected register.
legalName, legalForm, nip, regon	Company identity and identifiers where published.
address	Country, region, county, municipality, city, street, building/apartment, postal code and post office.
snapshotDate, registrationDate, lastEntryDate, court	Registry dates and court information. Source date strings are preserved.
representatives	Published names, roles and suspension flags where available.
shareholdersOrPartners	Published people/entities, holdings and ownership fields where available.
businessActivities, shareCapital	PKD codes/descriptions and capital amount/currency.
rawOdpis	Optional official odpis object, only on successful records.
status, errorMessage	Lookup outcome and explanation for a missing or failed lookup.
sourceUrl, scrapedAt	Registry source URL and UTC collection timestamp.

The key-value store contains RUN_SUMMARY with counts and an overall outcome, and PENDING_WORK with progress and retryable numbers. There is no selectable sorting mode. Records follow normalized input order, with the list field before the text field.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once per run. The result event applies to each successful registry extract saved to the dataset. Not-found and error rows are not charged as successful extracts, while the start event still applies.

Begin with a small list. See the live Pricing tab for current rates.

Tips for best results

• Use known KRS numbers rather than company names. This Actor does not discover or resolve registration IDs.
• Select the correct register for the batch. P and S are separate choices, not an automatic combined search.
• Keep status and source links with each record. Active describes returned data rather than legal health.
• Retain original registry date strings. Review them alongside the official extract for important decisions.
• Inspect pending or retryable numbers before expanding. Large lists can finish partially within a run deadline.

Limits and caveats

Only current public KRS extracts for known registration numbers are supported without a registry login. Company-name, NIP or REGON discovery, historical extracts, financial filings and beneficial-ownership verification are outside scope. This Actor is not affiliated with the Ministry of Justice and does not certify legal, operating or financial status.

The list and pasted text inputs combine, with list entries first in normalized input order. Numbers are normalized to ten digits and duplicates looked up once. One register choice applies to the entire run: P for entrepreneurs or S for associations and foundations. No automatic both-register lookup or selectable sorting is provided.

Each unique number yields active, not_found or error status. Active only indicates a returned extract. Names can be masked and some fields or lists can be absent for the legal form. Source date strings are preserved, and optional rawOdpis is included only for successful records.

Outages or restrictions can produce error rows, while a missing record does not establish deletion. Check the number and selected register. Missing-record rows alone do not fail the run, but every lookup encountering an error does. Larger batches can stop with partial results: RUN_SUMMARY gives counts and overall outcome, and PENDING_WORK records progress and retryable numbers. Review them rather than treating all requested lookups as complete. Repeated-export comparisons or alerts are your own workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~poland-krs-company-registry-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "krsNumbers": [
    "0000123456"
  ],
  "register": "P"
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/poland-krs-company-registry-scraper').call({
  "krsNumbers": [
    "0000123456"
  ],
  "register": "P"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/poland-krs-company-registry-scraper').call(run_input={'krsNumbers': ['0000123456'], 'register': 'P'})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Poland KRS Company Registry Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Poland KRS Company Registry Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/poland-krs-company-registry-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Poland KRS Company Registry Scraper by Fetch Cat, or give it the identifier fetch_cat/poland-krs-company-registry-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Poland KRS Company Registry Scraper to retrieve KRS 0000123456 from register P with raw extract off. Keep source identity and lookup status without treating active as verified legal or financial health.”
• “Collect registry outcomes for KRS numbers 123456 and 247804 from register P with raw extracts off. Keep normalized numbers, names and source links, distinguishing not-found and error rows from returned extracts.”
• “Retrieve KRS 0000123456 from register P with the raw official extract enabled. Keep available representatives, business activities and source date strings without inferring masked names or checking historical or beneficial ownership.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I search Poland's company register by name?

No. Supply KRS numbers you already have. This Actor does not resolve company names, NIP or REGON into KRS numbers.

Does it need a Polish registry login?

No. It reads public extracts without a registry account. Apify API and MCP access still require Apify authentication.

Can I export the results to CSV or Excel?

Yes. Use the dataset export controls or Apify's dataset API. JSON preserves nested representatives, addresses and activity lists most directly.

Is this an alternative to calling the KRS API myself?

It provides normalized fields, batch input and Apify datasets around current public registry extracts. It does not expand what the registry publishes or certify legal status. There is no built-in change-comparison or monitoring mode.

Related Actors

• UK Companies House Scraper — company research in the UK registry.
• NPI Registry Scraper — collect public US healthcare-provider identifiers, names, practice addresses and available taxonomy fields.
• BuiltWith Domain Tech Stack Scraper — research technology used by known company domains.
• WHOIS RDAP Domain Lookup — look up domain registration information.
• Email MX Deliverability Verifier — inspect email-domain delivery configuration.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥