# Markets, currencies & units

Every valuation is for one market. The market decides the vehicle data, the currency, the mileage unit and the price model, and a result applies only to its own market. This page lists the markets and their conventions.

## Supported markets

`GET /v1/catalogue/countries` returns the markets you can send as `country`, with their mileage unit and their `availability`:

**curl**

```bash
curl https://data-services.autouncle.com/v1/catalogue/countries \
  -H "Authorization: Bearer $AUTOUNCLE_API_KEY"
```

**Ruby**

```ruby
require "json"
require "net/http"

uri = URI("https://data-services.autouncle.com/v1/catalogue/countries")
request = Net::HTTP::Get.new(uri)
request["Authorization"] = "Bearer #{ENV.fetch("AUTOUNCLE_API_KEY")}"
response = Net::HTTP.start(uri.host, uri.port, use_ssl: true) { |http| http.request(request) }
puts JSON.pretty_generate(JSON.parse(response.body))
```

**Python**

```python
import json
import os

import requests

response = requests.get(
    "https://data-services.autouncle.com/v1/catalogue/countries",
    headers={
        "Authorization": f"Bearer {os.environ['AUTOUNCLE_API_KEY']}",
    },
    timeout=30,
)
print(json.dumps(response.json(), indent=2))
```

**JavaScript**

```javascript
const response = await fetch("https://data-services.autouncle.com/v1/catalogue/countries", {
  method: "GET",
  headers: {
    Authorization: `Bearer ${process.env.AUTOUNCLE_API_KEY}`,
  },
});
console.log(JSON.stringify(await response.json(), null, 2));
```

| `country` | Market | Currency | Mileage unit | Internal code | Availability |
| --- | --- | --- | --- | --- | --- |
| `DK` | Denmark | DKK | `km` | `da` | `general` |
| `SE` | Sweden | SEK | `mil` | `se` | `general` |
| `DE` | Germany | EUR | `km` | `de` | `general` |
| `IT` | Italy | EUR | `km` | `it` | `general` |
| `ES` | Spain | EUR | `km` | `es` | `general` |
| `AT` | Austria | EUR | `km` | `at` | `general` |
| `PT` | Portugal | EUR | `km` | `pt` | `general` |
| `PL` | Poland | PLN | `km` | `pl` | `general` |
| `FI` | Finland | EUR | `km` | `fi` | `general` |
| `RO` | Romania | EUR | `km` | `ro` | `general` |
| `GB` | United Kingdom | GBP | `mi` | `uk` | `general` |
| `FR` | France | EUR | `km` | `fr` | `general` |
| `CH` | Switzerland | CHF | `km` | `ch` | `general` |
| `NL` | Netherlands | EUR | `km` | `nl` | `general` |
| `BE` | Belgium | EUR | `km` | `be` | `on_request` |

Romanian results are in euros, as car prices in Romania are usually quoted in EUR.

`availability` says whether a new workspace can value the market. `general` markets are enabled for every new workspace. An `on_request` market, currently only Belgium, is listed so that you can recognise its code, but a valuation there returns `403 country_not_enabled` until AutoUncle enables it for your workspace; contact sales to ask. `GET /v1/account` shows the markets your workspace may value.

Being listed, and being enabled for your workspace, does not guarantee that a live valuation model is available for every market at every moment. Check each market you plan to serve with a live request before launch. A market without a live model fails with a `failed` result such as `engine_unavailable`, which uses no credit.

## Sending the country

Send `country` as an ISO 3166-1 alpha-2 code, such as `DK` or `GB`. The value is normalized before any data is read:

- case does not matter (`dk` works);
- the market's internet domain is also accepted, such as `dk` or `co.uk`;
- AutoUncle's internal market codes are also accepted, such as `da` for Denmark and `uk` for the United Kingdom.

Prefer the ISO code: it is what results return in `country`. An unknown value returns `400 unsupported_country`. A missing or `null` country returns `400 country_required`, with `/country` first in `errors` and any other schema problems after it. Over MCP, `country` is a required `valuate_car` argument, so a call without it is rejected as invalid tool arguments before the tool runs.

## Account market codes

`GET /v1/account` lists the markets the calling key can value in `allowed_countries`, as ISO codes such as `DK` and `GB`, the same codes you send in `country`. Results and the countries endpoint use them too. The internal codes in the table above are only accepted in requests.

## Currency

`valuation.currency` is the market's ISO 4217 currency, and every amount in the result (price, intervals, price-rating bands) uses it. `pricing.asking_price` must be in the same currency. The API does not convert between currencies; if you need another currency, convert in your own system and label it clearly as converted.

## Mileage units

Send `vehicle.mileage` in whatever unit you have, `km`, `mi` or `mil` (Scandinavian mile of 10 km). It is converted to the market's unit, and the resolved `vehicle.mileage` comes back in the market's unit. For example, a Swedish valuation with `{"value": 9000, "unit": "mil"}` means 90,000 km and comes back as `9000 mil`. `electric_range_km` is always in kilometres.

## Price basis and region

The price basis is chosen per request with `pricing.price_basis` (`dealer_retail` by default, or `private_sale`) and is available in every market. `pricing.seller_region` passes a known seller region within the market as context, when your source has one.

## A result belongs to its market

Every valued result carries a `market_specific` note: the price applies only to that market, its currency and its price basis. Do not reuse a Danish valuation for a German listing, or compare raw prices across markets without accounting for currency and market differences. To compare the same car in several markets, value it once per market. See [multiple markets](/docs/guides/multi-market).
