# Caucasus Company Screen (Georgia · Armenia · Moldova) (`reestri/company-screen`) Actor

Screen a company name across Georgia's, Armenia's and Moldova's public registers in one call: matches with status and legal form, Armenian beneficial owners, Moldovan founders and directors, Armenian public-contract exposure. One evidence-backed screening record per query for KYC and due diligence.

- **URL**: https://apify.com/reestri/company-screen.md
- **Developed by:** [Soso Pkhakadze](https://apify.com/reestri) (community)
- **Categories:** Agents, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $100.00 / 1,000 matched company records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Caucasus Company Screen (Georgia · Armenia · Moldova)

One company name in, one evidence-backed screening record out, across every public
register in the catalog, in a single call:

- **Georgia** (NAPR public registry): matches with legal form and registration status
- **Armenia** (state register): matches with registration data, tax ID, **beneficial
  owners** from official declarations, and **public-contract exposure** (count, total
  AMD, single-source awards, latest three contracts) from the weekly contracts index
- **Moldova** (ASP open data): matches with legal form, status, **founders with shares
  and directors**

Then one `company` record per match with the full detail, and an explicit
`unavailable` record for any source that could not be read (never a silent gap).

### Who uses it

- **KYC / onboarding analysts** who need a first-pass answer in seconds: does this name
  exist in the region, where, is it active, who's behind it, does it live on state
  contracts.
- **Sanctions and due-diligence teams** mapping counterparties across the Caucasus
  corridor without three separate portals in three alphabets.
- **AI agents** doing counterparty research: one tool call instead of orchestrating three.

### Input

| Field | Type | Description |
|---|---|---|
| `query` | string | Company name, any script; partial works, exact matches best. |
| `countries` | array | Subset of `GE`, `AM`, `MD` (default `GE`,`AM`; Moldova opt-in until its open-data re-use terms are confirmed in writing). |
| `maxPerCountry` | integer | Cap on matches per register (default 3; each is a charged record). |
| `includeContracts` | boolean | Armenian public-contract exposure (default true). |

### Output

First record, the screen:

```json
{
  "resultType": "screen",
  "query": "Silknet",
  "summary": {
    "matchedCompanies": 3,
    "byCountry": { "GE": 3, "AM": 0, "MD": 0 },
    "byStatus": { "active": 3 },
    "beneficialOwnersFound": 0,
    "foundersOrShareholdersFound": 0,
    "armenianPublicContracts": { "count": 0, "totalAMD": 0 },
    "sourcesUnavailable": [],
    "verdict": "3 match(es); review status, owners and contract exposure"
  },
  "sources": { "GE": { "status": "ok", "matches": 3, "candidates": 3, "evidence": { "sourceUrl": "…", "sha256": "…" }, "ms": 2100 }, "AM": { "status": "ok", "matches": 0, "candidates": 0 }, "MD": { "status": "ok", "matches": 0, "candidates": 0 } },
  "evidence": { "retrievedAt": "…", "sourceUrls": { "GE": "…", "AM": "…", "MD": "…" } }
}
```

Followed by `company` records (same schema as the single-country tools, plus
`publicContracts` on Armenian matches).

### Pricing

Pay per event: one `screen` per query, one `company-record` per matched company.
Georgia and Armenia are read live; Moldova and Armenian contracts come from weekly
indexes (snapshot date in `evidence.registryAsOf`).

### Scope, hygiene, legality

Georgia: search-level data only (ownership views are captcha-gated and not automated).
Armenia: owners' home addresses never included. Moldova: published as the state
publishes it; no personal identification numbers exist in the source. Every source
URL and hash is in the evidence blocks.

# Actor input Schema

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

Company name in any script (Latin, Georgian, Armenian, Romanian). Partial names work; exact names match best.

## `countries` (type: `array`):

Registers to screen. Moldova (ASP open data) is opt-in until its re-use terms are confirmed in writing.

## `maxPerCountry` (type: `integer`):

Cap on matched companies per register (each matched company is one charged record).

## `includeContracts` (type: `boolean`):

For Armenian matches, count their public procurement contracts (from the weekly PPCM index).

## Actor input object example

```json
{
  "query": "Silknet",
  "countries": [
    "GE",
    "AM"
  ],
  "maxPerCountry": 3,
  "includeContracts": true
}
```

# Actor output Schema

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

First record is the `screen` summary (per-country match counts, statuses, owners found, contract exposure); followed by one `company` record per match; `unavailable` per source that could not be read.

# 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 = {
    "query": "Silknet"
};

// Run the Actor and wait for it to finish
const run = await client.actor("reestri/company-screen").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 = { "query": "Silknet" }

# Run the Actor and wait for it to finish
run = client.actor("reestri/company-screen").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 '{
  "query": "Silknet"
}' |
apify call reestri/company-screen --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,reestri/company-screen"
        }
    }
}

```

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/IM6rYIFeBFyzXdb2V/builds/ohYpfqie1aktwAbb1/openapi.json