# Lithuanian Company Check: Business Register, Tax Debts (`deriverge/lithuanian-company-check`) Actor

Check Lithuanian companies in bulk against the state registers. Add legal entity codes and get name, legal status including liquidation and bankruptcy, VAT registration history, VIES confirmation, and the exact tax debt the company owes. Rows that cannot be matched are free.

- **URL**: https://apify.com/deriverge/lithuanian-company-check.md
- **Developed by:** [deriverge s.r.o.](https://apify.com/deriverge) (community)
- **Categories:** Business, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 company records

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?

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

## Lithuanian Company Checker

### What does Lithuanian Company Checker do?

**Lithuanian Company Checker** verifies Lithuanian companies in bulk against four official state sources at once. Give it a list of 9-digit legal entity codes and for each one you get back the legal name, legal form, legal status, VAT registration with its full history, an independent VIES confirmation, and the exact amount the company owes the tax authority.

The combination is the point. Each of the four sources answers a question the others cannot:

| Source | The question only it answers |
|---|---|
| **JAR** (Register of Legal Entities) | Is the company in liquidation, bankruptcy or restructuring? Was it deregistered, and when? |
| **VMI tax register** | What is its VAT number, since when, and was the registration ever cancelled? |
| **VMI debtor list** | How much does it owe the tax authority right now, and how much of that is past due? |
| **EU VIES** | Does the EU confirm the VAT number is valid for cross-border trade? |

A supplier can look perfectly alive in the tax register while the business register already lists it as *Likviduojamas dėl bankroto*. A name-and-address lookup will not tell you that. This actor will.

### Verified zero is not a missing check

The debtor list only contains debtors, so an empty answer means **verified: no tax debt**, and the output says `taxDebtEur: 0` rather than `null`. A `null` appears only when the check itself could not be performed, and the provenance row says why. The same honesty applies everywhere: when a source is down, the affected fields are `null` and flagged, never silently guessed.

### Typos never reach the register

Lithuanian legal entity codes carry a checksum digit. Every code is validated locally first; a code that fails the checksum is reported as a typo, costs nothing, and never generates a request. A code that passes the checksum but does not exist is reported as such, free of charge, after checking **both** the register of active entities and the register of deregistered ones, because "it existed and was dissolved in 2019" is a different answer than "it never existed".

### Input

```json
{
  "companies": [
    "121215434",
    { "code": "123033512", "reference": "supplier-42" }
  ],
  "checkTaxDebts": true,
  "includeVies": true
}
```

Strings and objects can be mixed freely. The optional `reference` is returned unchanged so you can join results back to your own system.

### Output

One row per submitted company:

```json
{
  "input": "121215434",
  "matched": true,
  "code": "121215434",
  "name": "Telia Lietuva, AB",
  "legalForm": "Akcinė bendrovė",
  "registeredOn": "1992-02-06",
  "companyActive": true,
  "legalStatus": null,
  "vatNumber": "LT212154314",
  "vatRegisteredOn": "1994-05-01",
  "vatValidVies": true,
  "taxDebtEur": 0,
  "overdueTaxDebtEur": 0,
  "riskFlags": [],
  "provenance": [
    { "source": "JAR (Registrų centras)", "ok": true },
    { "source": "VMI daňový registr", "ok": true },
    { "source": "VMI nedoplatky", "ok": true },
    { "source": "EU VIES", "ok": true }
  ]
}
```

### Watch a list for changes

Checking a supplier once is useful. Checking the same list every morning and reading only what changed is what keeps you out of trouble. Give the run a watch name (or save it as a task and schedule it) and every later run compares its results with the previous one: a company that turned inactive, a new risk flag, a VAT registration cancelled, a published account that disappeared. The differences are stored in the `CHANGES` record of the run, ready for an integration or an email. The comparison itself is free.

### Pricing

| Event | Price |
|---|---|
| Run fee, charged once per run that resolves at least one company | $0.03 |
| Company resolved | $0.008 |
| Each additional source that returned an answer | $0.003 |
| Company not found | **free** |

### What it does not do

The register's address data sits behind a chain of separate registers and is not included yet; the `address` field is always `null` for now. If you need addresses, say so in a review and it moves up the list.

### Frequently asked questions

**What does an unmatched row cost?** Nothing. Rows that fail the checksum or that no register knows are returned with an explanation and are never charged.

**Is a zero tax debt a real answer?** Yes. The debtor list contains only debtors, so an empty result is a verified zero, reported as 0. A null appears only when the check itself could not run.

**Why does the answer distinguish deregistered from never existed?** Because they mean different things when you vet a counterparty. A code found among deregistered entities returns the company with its removal date; a code no register knows is reported as non-existent.

**Where does the data come from?** The Lithuanian Register of Legal Entities and the State Tax Inspectorate (VMI), both through the national open data portal, plus EU VIES. Every value carries its source and timestamp.

### Where the data comes from

All four sources are official, public and free of charge: both the Register of Legal Entities and the tax authority publish their data through the national open data portal. No scraping of web pages, no proxies, no headless browser, which keeps runs cheap and the data authoritative.

This is the Lithuanian sibling of our [Czech & Slovak](https://apify.com/deriverge/czech-company-check) and [Romanian](https://apify.com/deriverge/romanian-company-check) company checkers. All three share the same validation engine and the same billing rule: unmatched rows are free.

# Actor input Schema

## `companies` (type: `array`):

One entry per company: a 9-digit legal entity code (121215434) or an object with code and an optional reference that is returned unchanged. Typos that fail the checksum are reported and never charged.

## `checkTaxDebts` (type: `boolean`):

Look each company up in the tax authority's debtor list. An empty result is a verified zero debt, not a missing check.

## `includeVies` (type: `boolean`):

Cross-check every VAT number against the EU VIES system as a second, independent source. A disagreement between the registers is reported as a risk flag.

## `watchKey` (type: `string`):

Give the run a name such as "suppliers" and schedule it. Every later run with the same name compares its results with the previous one and stores the differences (status changes, new risk flags, removed accounts) in the CHANGES record. Comparison is free. Runs from a saved task are compared automatically even without a name.

## Actor input object example

```json
{
  "companies": [
    "121215434",
    {
      "code": "123033512",
      "reference": "supplier-42"
    }
  ],
  "checkTaxDebts": true,
  "includeVies": true
}
```

# Actor output Schema

## `companies` (type: `string`):

One row per submitted company, with identity, legal status, VAT history, verified tax debt and risk flags.

## `summary` (type: `string`):

How many entities were resolved, how many were not found and therefore not charged, and how many carry a risk flag.

# 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 = {
    "companies": [
        "121215434",
        {
            "code": "123033512",
            "reference": "supplier-42"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("deriverge/lithuanian-company-check").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 = { "companies": [
        "121215434",
        {
            "code": "123033512",
            "reference": "supplier-42",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("deriverge/lithuanian-company-check").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 '{
  "companies": [
    "121215434",
    {
      "code": "123033512",
      "reference": "supplier-42"
    }
  ]
}' |
apify call deriverge/lithuanian-company-check --silent --output-dataset

```

## MCP server setup

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

```

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/k3AbrskMBbx5Vvu1C/builds/3H8NnKfyMYNMRBnSQ/openapi.json