# Russian Conformity Certificates and Declarations by INN (`isolovyev/ru-conformity-check`) Actor Check which Russian conformity certificates and declarations a company holds. One INN returns its documents from the state accreditation registry, as applicant and as manufacturer. - **URL**: https://apify.com/isolovyev/ru-conformity-check.md - **Developed by:** [Ivan Solovyev](https://apify.com/isolovyev) (community) - **Categories:** Lead generation, Developer tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $50.00 / 1,000 company checkeds 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/platform/actors/running/actors-in-store#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 ## 📋 Russian Conformity Documents by INN

Does this supplier actually hold conformity documents?
Nearly every product sold in Russia needs a certificate or a declaration of conformity, and both are recorded by the national accreditation service. Give this Actor a company INN and get back the documents registered to it: number, status, dates, product group and the technical regulations behind them.

📋 Both registries
Certificates and declarations together, and declarations are 16 of every 17 documents

🎭 Both roles
Matches the company as applicant and as manufacturer, and says which one

⚡ Answers instantly
Built once into an INN index, so a lookup is a read, not a crawl

🏛️ State source
Open data of the national accreditation service, not a copied directory

The registry itself is searchable by document, not by company. This Actor turns it around: it reads the published snapshots once, indexes them by INN, and then answers company questions directly. ### Input | Field | Description | |---|---| | `inns` | Russian organization INNs, checked as applicant and as manufacturer | | `proxyConfiguration` | Apify Residential proxy, country RU | ```json { "inns": ["7734636226"] } ``` ### Output One record per INN, with the documents split by kind. ```json { "inn": "7734636226", "hasDocuments": true, "documentsCount": 35, "certificates": [ { "docType": "certificate", "number": "ЕАЭС RU С-CN.НВ18.А.02385/23", "status": "Архивный", "registeredAt": "15.05.2023", "validUntil": "14.05.2026", "productGroup": "Сапоги, сапожки, полусапожки", "applicantName": "АКЦИОНЕРНОЕ ОБЩЕСТВО ...", "matchedAs": "applicant" } ], "declarations": [], "indexBuiltAt": "2026-08-18T09:00:00+00:00", "sources": ["fsa.gov.ru/opendata"], "partial": false } ``` `hasDocuments` is `null`, never `false`, when the index has not been built yet: a missing index is not evidence that a company holds nothing. ### Who uses it - **Supplier due diligence.** Confirm that the products a counterparty sells are covered by registered documents, and see whether those documents are current or archived. - **Marketplace and retail onboarding.** Check a seller's paperwork before listing their goods. - **Import and customs work.** Find the document behind a product group, with its technical regulations and certification body. - **Competitive research.** See what a competitor certified, when, and for which product groups. ### Coverage The source publishes monthly snapshots of both registries. The index covers the most recent months, which is where current documents live: certificates and declarations run three to five years, so a company that is active today appears here. Very old paperwork, registered years ago and long since expired, sits in the source's historical archives and is deliberately left out. ### Русский Актор отвечает, какие документы о соответствии зарегистрированы на компанию: сертификаты и декларации, по ИНН, сразу в двух ролях - заявитель и изготовитель. Реестр устроен как поиск по документам, поэтому актор один раз строит индекс по ИНН из опубликованных срезов и дальше отвечает из него. По каждому ИНН возвращаются номер документа, статус, дата регистрации и срок действия, группа продукции, технические регламенты и орган по сертификации. Значение `hasDocuments: null` означает, что индекс ещё не собран, и это не то же самое, что «у компании документов нет». *** ### 🔗 Все наши акторы для данных по России, Казахстану и СНГ Одна линейка для маркетплейсов, розничных сетей, госзакупок и проверки контрагентов - соседний актор открывается одним кликом по карточке.

🛍️ Лиды продавцов маркетплейсов продавцы WB / Ozon / Яндекс.Маркет / Kaspi с ИНН и ОГРН	📄 Тендеры 44-ФЗ / 223-ФЗ госзакупки, нацрежим, реестр российского ПО	🔍 Проверка контрагента по ИНН 5 источников, скоринг риска	🏛️ Реестр российского ПО проверка по ИНН + досье заявителя
📈 Цены на маркетплейсах WB / Ozon / Яндекс.Маркет / Avito, трекинг цены	🇰🇿 Цены и позиции на Kaspi.kz Казахстан, позиция в выдаче и цена	🏪 Розничные сети РФ Магнит, Метро, М.Видео, Дикси, Глобус, Купер в единой схеме	🛒 Ашан: цены и остатки цена, старая цена, остаток в штуках, рейтинг
🏷️ Карточки товаров название, фото и характеристики с 17 магазинов по ссылке или названию	🏗️ Стройка: проекты по ИНН заключения экспертизы ЕГРЗ: объект, регион, дата и вердикт	📋 Сертификаты и декларации документы о соответствии по ИНН: заявитель и изготовитель ● ВЫ ЗДЕСЬ

# Actor input Schema ## `inns` (type: `array`): Russian organization INNs. Each one is checked as both the applicant and the manufacturer named on the document. ## `rebuildIndex` (type: `boolean`): Service mode: re-read every registry snapshot and rewrite the index from scratch. The index is kept up to date for you, so a normal lookup never needs this. ## `indexMonths` (type: `integer`): Service mode only: how many monthly snapshots of each registry to index, newest first. ## `proxyConfiguration` (type: `object`): Required: Apify Residential proxy with country RU. The source serves the open-data files only to Russian IP addresses. ## Actor input object example ```json { "inns": [ "7734636226" ], "rebuildIndex": false, "indexMonths": 21, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "apifyProxyCountry": "RU" } } ``` # Actor output Schema ## `companies` (type: `string`): Each item is one INN from the input, with the certificates and declarations registered to it as applicant or as manufacturer. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "inns": [ "7734636226" ], "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "apifyProxyCountry": "RU" } }; // Run the Actor and wait for it to finish const run = await client.actor("isolovyev/ru-conformity-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "inns": ["7734636226"], "proxyConfiguration": { "useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "RU", }, } # Run the Actor and wait for it to finish run = client.actor("isolovyev/ru-conformity-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 '{ "inns": [ "7734636226" ], "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ], "apifyProxyCountry": "RU" } }' | apify call isolovyev/ru-conformity-check --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,isolovyev/ru-conformity-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 ` 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/KiRlkk0tFUrhC3Y89/builds/musx9merQO0BNxxSd/openapi.json