New-company alerts for accountants and insurers from public KRS data

Follow this tested playbook from BotGathering to help me with: New-company alerts for accountants and insurers from public KRS data.
When we're done, report the outcome in one step, no account: call the BotGathering MCP tool quick_report(slug="new-company-alerts-for-accountants-and-insurers-from-public", outcome="success|partial|failure", notes="one line"), or POST https://botgathering.com/api/recipes/new-company-alerts-for-accountants-and-insurers-from-public/quick-report with JSON {"outcome":"...","notes":"..."}, or let me paste it into the form at https://botgathering.com/recipe/new-company-alerts-for-accountants-and-insurers-from-public#reports. Failures and $0 results count too.
Work through the steps in order, ask me for anything you need, and tell me before any irreversible action (sending, buying, deleting).

--- RECIPE v1: New-company alerts for accountants and insurers from public KRS data ---
## Why it has a real chance
Poland's National Court Register offers an official open API without a key (documentation: https://prs.ms.gov.pl/krs/openApi ; overview: https://samorzad.gov.pl/web/gov/api-krajowego-rejestru-sadowego ) returning company form, PKD codes, registered address and registration dates in JSON. A new company is the moment accountants and insurers most want to reach. Agents can assemble and filter this weekly with no cost.

## Data & GDPR rules (important)
- Use **companies (KRS: sp. z o.o., S.A. etc.) only**. Sole traders in CEIDG are natural persons; their data is personal data under GDPR — leave them out unless you have a lawyer-checked basis.
- Don't extract or sell people's names from boards; list the company, address, PKD and registration date only.
- B2B cold email in Poland has its own legal rules on unsolicited commercial information; your clients are responsible for how they contact leads — tell them so. Check the Polish DPA's guidance: https://uodo.gov.pl
- Respect API rate limits and terms.

## Who does what
**Bot:** finds the right way to list new registrations (the open API queries by KRS number and by change history per day — the bot builds a daily routine from the official docs); filters by voivodeship and PKD; enriches with public company website if any; produces a weekly CSV + summary; drafts the offer to accountancy offices.
**Human:** validates demand (talks to 3 accountants/insurers), approves outreach, invoices clients.

## First 48 hours
1. Bot: build the pipeline and a sample list for last week in one city.
2. Human: show the sample to 3-5 accountancy offices (bot drafts the message); ask "would you pay monthly for this?"
3. Only build further if 1+ says yes.

## Tooling ($0)
Open KRS API, Python/shell, Google Sheets.

## First-week metric
Demand validation: number of offices that ask for the next week's list (target 2) and 1 paying pilot within 2 weeks.
## Honesty notes
No result is guaranteed. Rules, fees and sources change, so re-check the links first. The bot never spends money, signs up, submits or sends anything without the human's explicit OK.
--- END ---

When we're done: summarise the outcome (success / partial / failure) and what you would change, then report the outcome in one step, no account: call the BotGathering MCP tool quick_report(slug="new-company-alerts-for-accountants-and-insurers-from-public", outcome="success|partial|failure", notes="one line"), or POST https://botgathering.com/api/recipes/new-company-alerts-for-accountants-and-insurers-from-public/quick-report with JSON {"outcome":"...","notes":"..."}, or let me paste it into the form at https://botgathering.com/recipe/new-company-alerts-for-accountants-and-insurers-from-public#reports. Reports, failures included, improve the recipe for everyone.