🔔 Poland KRS Company Registry

One record per requested KRS number — company name, legal form, REGON, NIP, address and registration dates from the official current extract. This is a lookup-by-number API: honest scope, one record per supplied number, no full-roster claim.

One structured registry_record per record from the keyless api-krs.ms.gov.pl current-extract JSON (OdpisAktualny), logged-out. Public, logged-out, robots-honoured.

Output is one krs_company_record row per result; billing is pay-per-event, the value event being one registry record (a $0.02 start fee per run, then $0.02 per registry record). Source: api-krs.ms.gov.pl.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run hPsFoZypWcpEK8oVC on build 0.1.6 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

krs_number	company_name	legal_form	nip	address	registration_date
0000006865	CD PROJEKT RED SPÓŁKA AKCYJNA	SPÓŁKA AKCYJNA	7342867148	JAGIELLOŃSKA 74 WARSZAWA 03-301	06.04.2001
0000024599	OCHOTNICZA STRAŻ POŻARNA W BIADOLINACH RADŁOWSKICH	STOWARZYSZENIE	8732897040	104 BIADOLINY RADŁOWSKIE 32-828	09.07.2001

The run finished with the status message: NORMAL: 2 unique rows (0 duplicates collapsed). billable=2

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. krs_company_record
• krs_number (string/null) — e.g. 0000006865
• register (string/null) — e.g. P
• company_name (string/null) — e.g. CD PROJEKT RED SPÓŁKA AKCYJNA
• legal_form (string/null) — e.g. SPÓŁKA AKCYJNA
• regon (string/null) — e.g. 49270733300000
• nip (string/null) — e.g. 7342867148
• address (string/null) — e.g. JAGIELLOŃSKA 74 WARSZAWA 03-301
• registration_date (string/null) — e.g. 06.04.2001
• last_entry_date (string/null) — e.g. 10.08.2026
• state_as_of (string/null) — e.g. 10.08.2026
• source (string/null) — e.g. poland-krs-company-registry
• release_date (string/null) — null in every sample row
• source_url (string/null) — e.g. https://api-krs.ms.gov.pl/api/krs/OdpisAktualny/
• observed_at (string/null) — e.g. 2026-09-18T06:16:55Z
• terminal (string/integer/null) — null in every sample row
• reported_total (string/integer/null) — null in every sample row
• raw_seen (string/integer/null) — null in every sample row
• duplicates (string/integer/null) — null in every sample row
• unique_found (string/integer/null) — null in every sample row
• delivered (string/integer/null) — null in every sample row
• scope (string/integer/null) — null in every sample row
• note (string/integer/null) — null in every sample row

What you get

One registry_record per entity, deduplicated on the source-native id. Fields the source does not publish are honest null. A run_receipt row carries the source URL, scope, and delivered/duplicate counts.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "krsNumbers": [
    "0000006865",
    "0000024599"
  ],
  "maxRecords": 50
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 2 × $0.02 registry_record = $0.06 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "krsNumbers": [
    "0000006865",
    "0000024599"
  ],
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

3. A full-size run

{
  "krsNumbers": [
    "0000006865",
    "0000024599"
  ],
  "maxRecords": 2000
}

Up to 2000 rows (the schema default for maxRecords) — about $40.02 on the Free tier ($0.02 start + 2000 × $0.02) if the source has that many.

🧾 JSON sample record

One real record from run hPsFoZypWcpEK8oVC, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "krs_company_record",
  "krs_number": "0000006865",
  "register": "P",
  "company_name": "CD PROJEKT RED SPÓŁKA AKCYJNA",
  "legal_form": "SPÓŁKA AKCYJNA",
  "regon": "49270733300000",
  "nip": "7342867148",
  "address": "JAGIELLOŃSKA 74 WARSZAWA 03-301",
  "registration_date": "06.04.2001",
  "last_entry_date": "10.08.2026",
  "state_as_of": "10.08.2026",
  "source": "poland-krs-company-registry",
  "release_date": null,
  "source_url": "https://api-krs.ms.gov.pl/api/krs/OdpisAktualny/",
  "observed_at": "2026-09-18T06:16:55Z"
}

🔧 How it works

Source. The actor reads api-krs.ms.gov.pl — endpoints: https://api-krs.ms.gov.pl/api/krs/OdpisAktualny/. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Charging. Each registry record is charged at the moment it is pushed (registry_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Supply a list of KRS numbers; each is looked up in the entrepreneurs (P) then associations (S) register. Numbers that do not resolve are simply not emitted and never billed. maxRecords caps the count. Duplicates, outages, and schema drift charge nothing.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Registry Record (registry_record)	$0.02	$0.02	$0.02	$0.01

Worked at the live Free-tier price:

• 2 registry records: $0.02 start + 2 × $0.02 = $0.06
• 25 registry records: $0.02 start + 25 × $0.02 = $0.52
• 2000 registry records: $0.02 start + 2000 × $0.02 = $40.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: NORMAL: 2 unique rows (0 duplicates collapsed). billable=2. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by api-krs.ms.gov.pl. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (api-krs.ms.gov.pl) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 2000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers api-krs.ms.gov.pl. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Latvia Annual-Report Financial Statements — Latvia Annual-Report Financial Statements
• NY OCM Licence Registry — One structured registryrecord per record from the New York Office of Cannabis Management licence dataset (keyless NY Socrata jskf-tt3q, ~2,927 rows).…
• NYC DCWP Business Licence Registry — One structured registryrecord per record from the NYC Open Data DCWP licences resource (Socrata w7w3-xahh, ~69,885 rows). Public, logged-out, robots-…
• Slovakia Public-Sector Partners Register — Slovakia Public-Sector Partners Register
• Spain AEMPS Medicines Registry (CIMA) — One structured registryrecord per record from the official public source, logged-out. Public, robots-honoured, keyless
• Spain BORME Company Acts — One structured registryrecord per record from the boe.es open-data BORME daily summary (JSON) → per-province section XML chain, logged-out. Public, l…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.