> For the complete documentation index, see [llms.txt](https://docs.kontinent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kontinent.ai/models-and-routing/models.md).

# Models & sovereignty

Models are identified in `provider/model` form, e.g. `mistral/mistral-large-latest`. List everything available to your organization with `GET /v1/models`:

```json
{
  "object": "list",
  "data": [
    {
      "id": "mistral/mistral-large-latest",
      "object": "model",
      "owned_by": "mistral",
      "kind": "chat",
      "context_length": 128000,
      "sovereignty": "strict",
      "pricing": {
        "input_micro_eur_per_mtok": 1800000,
        "output_micro_eur_per_mtok": 5400000
      }
    }
  ]
}
```

## Sovereignty tiers

Each model declares a `sovereignty` tier so you can choose how strict your data residency requirements are:

| Tier        | Meaning                                                                  |
| ----------- | ------------------------------------------------------------------------ |
| `strict`    | Served by an **EU-owned** provider.                                      |
| `pragmatic` | Served from an **EU region** of a provider with a non-EU parent company. |

{% hint style="info" %}
The tier is returned on every model, so you can require `strict` where the use case demands an EU-owned provider and allow `pragmatic` elsewhere. See [Maximum privacy](/privacy/data-privacy.md).
{% endhint %}

## Model kinds

| Kind        | Endpoint                    |
| ----------- | --------------------------- |
| `chat`      | `POST /v1/chat/completions` |
| `embedding` | `POST /v1/embeddings`       |

Sending an embeddings model to the chat endpoint (or vice versa) is rejected; an unknown or disabled id returns `404 model_not_found`.

## Pricing and the money unit

Money everywhere in Kontinent is **integer micro-EUR**, so there is no floating-point rounding in billing:

> 1 EUR = 1,000,000 µEUR

Prices are quoted **per million tokens**, split into input and output rates, and returned on every model so you always know the cost before you send. In the example above, input costs `1,800,000` µEUR/Mtok, which is **€1.80 per million input tokens**, and output costs **€5.40 per million output tokens**. You pay only for the tokens a request actually uses.

See [Rate limits & credits](/features/rate-limits.md) for how spend is metered.

## Related

{% content-ref url="/pages/gJyUCtzhTvMq5MNXJfuc" %}
[API reference](/reference/api-reference.md)
{% endcontent-ref %}

{% content-ref url="/pages/QESs3zvtebNO6KUdpRpD" %}
[Price & performance](/models-and-routing/price-performance.md)
{% endcontent-ref %}

{% content-ref url="/pages/S87kmqk1v7J693l2ZOBs" %}
[Maximum privacy](/privacy/data-privacy.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kontinent.ai/models-and-routing/models.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.