Armenia Supplier Public Contracts

The public procurement contracts an Armenian company has won, from the official contracts registry (PPCM, Ministry of Finance / armeps.am): the buying authority with its tax ID, contract value and savings against estimate, signing date and deadline, procedure type, number of bidders, appeals. Search by the supplier's 8-digit tax ID (ՀՎՀՀ) or by name. Indexed weekly from the public registry; evidence on every record.

What you can do with it

• Due diligence and KYB: see whether a counterparty lives on state contracts, with whom, for how much, and how often it wins single-source awards.
• Sanctions and integrity screening: state-contract exposure is a standard risk factor; appeals and unlawful-act notes are included as published.
• Market and competitor intelligence: a supplier's award history in the index in one call.
• Joins with the register: supplierTaxId is the same ՀՎՀՀ as the "Tax id" in our Armenia Company Registry tool, so ownership and contracts link cleanly.
• AI agents: available as an MCP tool.

Input

Field	Type	Description
taxId	string	8-digit supplier tax ID; takes precedence over query.
query	string	Full or partial supplier name (as registered, Armenian or Latin). Also finds suppliers the registry lists without a tax ID (see below).
maxSuppliers	integer	For name search, how many matching suppliers to expand, most contracts first (default 3).
maxContracts	integer	Max contract records to return and charge for, newest first (default 50).

Output

One contract record per contract. Real record from a tax ID search for 00024873 (UCOM), run on 2026-09-12, title shortened and quotes straightened:

{
  "resultType": "contract",
  "country": "AM",
  "contractId": "bda8538a-031d-4bd4-bb58-aed916aed38b",
  "number": "A9049520879",
  "state": "ACTIVE",
  "supplierName": "ՅՈՒՔՈՄ ՓԲԸ",
  "supplierTaxId": "00024873",
  "buyerName": "«Կրթական ծրագրերի կենտրոն» ԾԻԳ",
  "buyerNameEn": "\"Center for Education Projects\" PIU",
  "buyerTaxId": "02550991",
  "buyerType": "GOVERNMENTAL",
  "title": "…ինտերնետային և հեռուստատեսության ծառայությունների ձեռքբերման…",
  "procedure": "single source",
  "procurementType": "SERVICES",
  "contractValueTotal": 22500,
  "contractSaving": 0,
  "currency": "AMD",
  "dateSigned": "2026-08-12",
  "deadline": "2026-12-24",
  "bidders": 1,
  "appeals": null,
  "unlawfulActs": null,
  "match": { "method": "tax_id_exact", "score": 1, "normalized": "00024873", "ambiguous": false, "candidates": 1 },
  "evidence": { "sourceUrl": "https://armeps.am/ppcm/public/contracts/contract", "retrievedAt": "2026-09-12T21:16:31.403Z", "registryAsOf": "2026-09-06", "contractId": "bda8538a-031d-4bd4-bb58-aed916aed38b", "sha256": null }
}

Fields the registry leaves empty come back as null or are omitted. Plus not_found (no contracts for that supplier in the registry index) and unavailable (index could not be read; the run also fails, never a negative).

Suppliers without an Armenian tax ID: a few suppliers appear in the registry with no tax ID (13 in the 2026-09-06 index). Name search finds them; their records carry supplierTaxId: null and a notes field saying so. They are indexed under the name as registered, so a filing under another spelling is not included, and the same company can show up twice for one name search, once under its tax ID and once without. Suppliers whose tax ID field holds something other than a plain number (mostly personal document numbers of individuals) are not returned.

Scope and hygiene

• Source: the public contracts registry's own JSON service, read weekly into an index; registryAsOf is the index date. The 2026-09-06 index held 235,570 of the 238,624 contracts the registry reported, so a very recent or unreadable contract can be missing. Line items (CPV codes, quantities) are not included in v1.
• The registry publishes supplier emails, bank account numbers and internal staff identifiers; we strip all of them at ingest and never store them. Individual entrepreneurs appear as registered (their business name).
• Armenia has announced a new procurement platform for 2027; this tool will migrate when it launches.

Pricing

Pay per event: one lookup per query the index answered (including not_found), one contract-record per contract returned. A query that ends unavailable because the index could not be read is not charged the lookup event and returns no records, so it costs nothing beyond Apify's run start fee of $0.00005 that every run carries.