Estonian Company Data

Look up an Estonian company in the e-Business Register by its 8-digit registry code or name. Returns company details and legal representatives.

Pay by wallet (x402) AI-generated Estonia: all company records estonian-company-data

Example

Input

{
  "registry_code": "17449106"
}

Answer

{
  "status": "active",
  "address": "Harju maakond, Tallinn, Kesklinna linnaosa, Vana-Lõuna tn 15",
  "zip_code": "10134",
  "company_name": "Bolt App Services AS",
  "jurisdiction": "EE",
  "registry_url": "https://ariregister.rik.ee/est/company/17449106/Bolt-App-Services-AS",
  "business_type": "1",
  "registry_code": "17449106",
  "historical_names": []
}

Inputs

Field	Type	Required	What it is
`name`	string	No	Alias for company_name
`task`	string	No	Free-text alias — registry code or company name
`query`	string	No	Free-text alias — registry code or company name
`company_name`	string	No	Company name. Resolved against the Business Register and accepted only on a confident name match — an ambiguous name is refused rather than resolved to the wrong legal entity.
`registry_code`	string	No	Estonian registry code, 8 digits (e.g. 10238429)

Output fields

How reliably each field appears in a successful answer.

Field	Type	Appears
`status`	string	Always (present in every successful answer)
`address`	string	Always (present in every successful answer)
`company_name`	string	Always (present in every successful answer)
`jurisdiction`	string	Always (present in every successful answer)
`business_type`	string	Always (present in every successful answer)
`registry_code`	string	Always (present in every successful answer)
`tier_2_available`	boolean	Always (present in every successful answer)
`ubo_availability`	string	Always (present in every successful answer)
`legal_representatives`	array	Usually (present for most inputs)
`tier_2_available_reason`	string	Always (present in every successful answer)
`ubo_availability_reason`	string	Always (present in every successful answer)
`total_legal_representatives`	integer	Always (present in every successful answer)
`zip_code`	—	Always (present in every successful answer)
`historical_names`	—	Always (present in every successful answer)
`registry_url`	—	Always (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": "estonian-company-data",
    "inputs": {
      "registry_code": "17449106"
    },
    "max_price_cents": 5
  }'

{
  "tool": "strale_execute",
  "arguments": {
    "slug": "estonian-company-data",
    "inputs": {
      "registry_code": "17449106"
    },
    "max_price_cents": 5
  }
}

import { Strale } from "straleio";

const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
  capability_slug: "estonian-company-data",
  inputs: {
    "registry_code": "17449106"
  },
  max_price_cents: 5,
});

import os
from straleio import Strale, DoRequest

strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
    capability_slug="estonian-company-data",
    inputs={
        "registry_code": "17449106",
    },
    max_price_cents=5,
))

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i 'https://api.strale.io/x402/v2/estonian-company-data?registry_code=17449106'

Limitations

Registry access can fail from some IP ranges
Estonian e-Business Register (ariregister) may block requests from certain IP ranges
What to do instead: If lookup fails, use the registry code to search directly at ariregister.rik.ee
Officer dates of birth are always null
`date_of_birth` is always null in `legal_representatives` for Estonian companies. RIK’s open dataset omits personal identification codes and dates of birth.
What to do instead: Ask the Estonian e-Business Register about access to a certified extract when additional officer details are needed.
Officer details can be up to 24 hours old
`legal_representatives` comes from a daily snapshot rather than a live officer lookup. New appointments or resignations can take up to 24 hours to appear.
What to do instead: Request current representation details directly from the Estonian e-Business Register.
API responses are limited to 4 MiB
API response bodies above 4 MiB are refused during download rather than parsed.