# Finland Companies & New Business Monitor: PRH YTJ (MCP) (`amygraphics/finland-companies-monitor`) Actor

Every Finnish company from the official PRH/YTJ register: name or business-ID search (legal form, TOL2008 industry, address, situations), or monitor NEW registrations daily with industry/city filters. Fresh B2B leads, zero hallucination. MCP-ready.

- **URL**: https://apify.com/amygraphics/finland-companies-monitor.md
- **Developed by:** [Zakaria el bouami](https://apify.com/amygraphics) (community)
- **Categories:** Lead generation, Automation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Finland Companies & New Business Monitor: PRH YTJ (MCP)

Every Finnish company — **fresh from the official source**. Search the Finnish Business Register (PRH / YTJ v3) by name or business ID, or monitor **newly registered companies daily** with industry and city filters. No key, no login, MCP-compatible, agent-ready.

### Why this data is hard (and useful)

- Finland's official register (`avoindata.prh.fi`, open-data YTJ v3) returns deeply nested JSON: versioned name histories, trilingual descriptions (Finnish/Swedish/English), TOL2008 industry codes, address objects with municipality codes, and register-entry types that need decoding. This actor collapses all of it into **one clean row per company**.
- Companies register at ~**35 per day** — a constant stream of fresh B2B leads that no search engine catches quickly.
- Name-history versioning is the classic trap: companies rebrand, and the register keeps every historical name. We select the *current official* name (with fallbacks for renamed/closed entities) so you always match the right entity.

### What you get per company

| field | meaning |
|---|---|
| `businessId` | Finnish Y-tunnus (e.g. `0194099-3`) — permanent unique ID, our dedupe key |
| `companyName` | current official name |
| `legalForm` / `legalFormCode` | e.g. `Limited company` (EN preferred, FI/SV fallback) |
| `industryCode` / `industryText` | TOL2008 code + description (e.g. `86950` physiotherapy) |
| `street`, `postCode`, `city`, `municipalityCode` | registered address (city name in Finnish when available) |
| `registryStatus`, `registeredAt`, `endedAt` | status + lifecycle dates |
| `registeredEntries`, `situations` | register entries (e.g. `Registered`) + special situations (liquidation, bankruptcy…) |
| `website`, `phone`, `email` | contact details **when the company published them** (often unset — we never invent values) |
| `lastModifiedAt` | register-side change timestamp |

### Mode `search`

```json
{ "mode": "search", "query": "Nokia", "maxResults": 10 }
```

- Free-text name search (handles the register's fuzzy matching) or exact business ID `0112038-9`.
- Charged **$0.001 per company row**.

### Mode `monitor` — new Finnish companies, daily

```json
{ "mode": "monitor", "industryPrefix": "62", "cityContains": "Helsinki", "maxResults": 40 }
```

- **Run 1 = free baseline** (info row only): saves a date cursor.
- **Run 2+**: only companies **registered since the cursor**, deduped by business ID. Optional filters: TOL2008 prefix (`62` IT, `47` retail, `86` health…) and city (`"Helsinki"`, `"Tampere"`…).
- Schedule daily; a no-news run costs **$0.001 total**. Feed Slack / Google Sheets / your CRM via webhook.

### Three ready recipes

1. **Sales-agent daily fuel** — as an MCP tool, your agent asks "any new IT companies in Finland this week?" and gets official, deduped rows with industry and city — a lead list no one else has yet.
2. **Counterparty/ KYB check** — agent receives a Finnish business ID, pulls the official row (legal form, status, situations incl. bankruptcy, address) before a deal.
3. **Market radar** — daily monitor of a niche (e.g. `industryPrefix: "56"` restaurants in Tampere) to watch local competition appear in real time.

### Data honesty & limits

- The register only contains what companies declare: `website/phone/email` are often empty and are reported exactly as published (empty = not provided, not hidden).
- `situations` reflects register entries; absence does not guarantee a company is healthy — for credit decisions use an authorized credit agency.
- The actor reads the public open-data API only (no login areas, no personal data beyond what the register itself publishes).

### Source (official, anonymous, no key)

- Finnish Patent and Registration Office (PRH) — Open Data YTJ v3: <https://avoindata.prh.fi> (companies endpoint)

### Price

| event | price |
|---|---|
| Actor start | $0.001 |
| Company row extracted (search match or new registration) | $0.001 / row |

Typical runs: 10-company search ≈ **$0.011** · daily new-companies radar with 8 matches ≈ **$0.009**.

### MCP / AI-agent usage

Add the actor to your agent's tools, or call:

```
https://api.apify.com/v2/acts/YOUR_HANDLE~finland-companies-monitor/run-sync-get-dataset-items?token=YOUR_TOKEN
```

Input = the JSON examples above. Output = the dataset rows described in the table. Compatible with per-request agentic payments.

Questions / feedback: see the actor's **Issues** tab on Apify Store.

# Actor input Schema

## `mode` (type: `string`):

search = look up companies by name or business ID. monitor = NEW registrations since the last run (first run = free baseline).

## `query` (type: `string`):

Company name (e.g. 'Nokia', 'Kone') or exact business ID (e.g. '0112038-9').

## `industryPrefix` (type: `string`):

TOL2008 industry code prefix, e.g. '62' for IT, '47' for retail, '86' for health. Empty = all industries.

## `cityContains` (type: `string`):

Only new companies whose city contains this text (e.g. 'Helsinki', 'Tampere'). Empty = all Finland.

## `maxResults` (type: `integer`):

Maximum company rows returned/charged per run.

## `requestDelaySecs` (type: `number`):

Politeness pacing between calls to the official PRH API.

## `proxyConfiguration` (type: `object`):

Optional. The official PRH endpoint does not require proxies.

## Actor input object example

```json
{
  "mode": "search",
  "query": "Nokia",
  "industryPrefix": "",
  "cityContains": "",
  "maxResults": 10,
  "requestDelaySecs": 0.5
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("amygraphics/finland-companies-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("amygraphics/finland-companies-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call amygraphics/finland-companies-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,amygraphics/finland-companies-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/AE4nG08xHm7cF47SF/builds/HTjzdJuJYrLGsAv7G/openapi.json