Czech Company Data

Look up a Czech company in ARES, the Ministry of Finance register, by IČO or company name.

Pay by wallet (x402) Czechia: all company records cz-company-data

Example

Example input
{
  "ico": "00177041"
}

The fields it answers with are listed under Output fields.

Inputs

FieldTypeRequiredWhat it is
icostringYesCzech IČO (8 digits) or company name for fuzzy lookup

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
icostringAlways (present in every successful answer)
statusone of active, dissolved, liquidation, insolvency, unknownAlways (present in every successful answer)
addressstringAlways (present in every successful answer)
nace_codesarrayAlways (present in every successful answer)
vat_numberstringAlways (present in every successful answer)
company_namestringAlways (present in every successful answer)
jurisdictionstringAlways (present in every successful answer)
last_updatedstringAlways (present in every successful answer)
primary_sourcestringAlways (present in every successful answer)
legal_form_codestringAlways (present in every successful answer)
tier_2_availablebooleanAlways (present in every successful answer)
ubo_availabilitystringAlways (present in every successful answer)
registration_datestringAlways (present in every successful answer)
signing_authoritystring or nullUsually (present for most inputs)
legal_representativesarrayUsually (present for most inputs)
tier_2_available_reasonstringAlways (present in every successful answer)
ubo_availability_reasonstringAlways (present in every successful answer)
total_legal_representativesintegerAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "cz-company-data",
    "inputs": {
      "ico": "00177041"
    },
    "max_price_cents": 5
  }'

Limitations

  • Official registry data access

    Data comes from the Czech Ministry of Finance's ARES public API, reused under the ARES operating conditions and Czech open-data law (https://ares.gov.cz/stranky/open-data). Results name ARES as their source. ARES data is informative only and is not an official document.

  • Registry status interpretation

    Liquidation reflects a current VR liquidator appointment, while insolvency reflects an active IR registration rather than a bankruptcy ruling. Status is unknown when an expected VR record is unavailable; ROS active status alone cannot exclude liquidation.

  • Natural persons' DIČ not derivable

    DIČ is returned verbatim when ARES has it. For natural persons registered as entrepreneurs, the DIČ may be CZ + rodné číslo and cannot be derived from IČO alone.

  • Fuzzy name search returns first match only

    Name search returns only the first ARES match. Ambiguous names can resolve to the wrong entity.

    What to do instead: Pass IČO directly when known.

  • Sole proprietors with only trade licence may be outside ROS

    Entities registered solely in RŽP (Živnostenský rejstřík) without ROS record may return limited data. ARES still returns basic identification.