Poland Company Data — KRS Court Registry 🇵🇱

foXLabs European company-registry series: UK · France · Estonia · Latvia · Czechia · Slovakia · Slovenia · Denmark · Norway · Finland

🎉 Turn the Polish court register into clean, structured company data — no login, no API key, one row per entity, with share capital, the management board, REGON and the registering court. Built for B2B sales, lead generation, KYB / compliance and market-research teams.

🔍 What is the Poland Company Data — and when should you use it?

Give this actor company names or KRS / REGON / NIP numbers and it returns matching companies from the Polish National Court Register (KRS) open API — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run queries the source live, so the data is as fresh as the registry itself.

Use it when you need: a Poland company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.

Use something else when: you need firmographics the registry doesn’t hold (revenue, headcount, website, email) — pair this with an enrichment actor from Fox Labs.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/poland-company-data.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull Poland company records using the Apify Actor `foxlabs/poland-company-data`.
Input: `queries` is a list of company names or KRS / REGON / NIP numbers. `maxResultsPerQuery` caps rows per query.
Start with: {"queries":["0000006865","0000106678"],"maxResultsPerQuery":50}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/poland-company-data.md.

📋 Overview

Everything you need to turn the Polish National Court Register (KRS) open API into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole registry, one call — name or ID in, matching companies out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable join key — registrationNumber ties rows across runs and to other Fox Labs actors.
• 💰 Pay only for results — per-row pricing, empty/failed lookups never billed.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~poland-company-data/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["0000006865","0000106678"],"maxResultsPerQuery":50}'

🚀 Getting Started (3 steps)

1. Choose your targets — company names or KRS / REGON / NIP numbers.
2. Set the cap — maxResultsPerQuery limits rows per query.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"queries":["0000006865","0000106678"],"maxResultsPerQuery":50}

Field	Type	Description
queries	array	Company names or KRS / REGON / NIP numbers.
maxResultsPerQuery	integer	Caps rows per query.
maxConcurrency	integer	How many queries to fetch at once.
includeRaw	boolean	Attach the source’s untouched record under raw.

📤 Output

One row per company, saved to the dataset. Every row also carries query, scrapedAt, and — when a lookup fails — an error explaining why (never silently dropped, never billed).

Field	Description
country	Country
registry	Registry
companyName	Company / entity name
registrationNumber	Registry ID — the join key
taxNumber	Tax identifier
status	active / inactive / dissolved
statusRaw	Status exactly as the registry words it
legalForm	Legal form / entity type
incorporatedOn	Formation / registration date (ISO)
dissolvedOn	Dissolution date where applicable (ISO)
address	Principal address
city	City
postalCode	Postal code
countryName	Country
industry	Primary industry (NACE)
industryCode	Primary industry code (NACE)
capital	Registered share capital
website	Website
email	Email
officers	Officers
sourceUrl	Public registry URL for the record
regon	Regon
region	Region
shareCount	Share Count
representationRule	Representation Rule
registerSection	Register Section
lastEntryDate	Last Entry Date
court	Court

💼 Use cases

1. Poland B2B lead lists — territory lists of active Polish entities with the board and capital. Input: name searches. Output: entities + officers + capital. Use: a ready sales list.

2. Ownership & governance — read the management board and representation rules. Input: KRS numbers. Output: officers + representation rule. Use: map decision-makers.

3. KYB / due diligence — verify a Polish entity by KRS / REGON / NIP. Input: the number or exact name. Output: the canonical registry record. Use: confirm existence, capital and board.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/poland-company-data').call({"queries":["0000006865","0000106678"],"maxResultsPerQuery":50});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/poland-company-data').call(run_input={"queries":["0000006865","0000106678"],"maxResultsPerQuery":50})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your queries → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads the Polish National Court Register (KRS) open API.

What do I search by? Company names or KRS / REGON / NIP numbers.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

Why are firmographics like revenue or website missing? A public business registry doesn’t hold them; we don’t ship empty columns. Pair with an enrichment actor from Fox Labs.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResultsPerQuery, or refine the name.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads a public government business registry published as open data. Results can still contain personal data (e.g. a registered agent’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1 — 2026-09-07

• Dropped empty-promise columns. Removed employees, phone — Polish National Court Register (KRS) open API does not carry them, so they were shipped as always-null columns. Only fields this registry actually fills are now emitted.
• README rebuilt to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.1.0

• Initial release: company lookup from the Polish National Court Register (KRS) open API by name or registry ID.