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

# Quantisation

Quantisation is deployment metadata. It can change when TensorX updates a model's weights or serving configuration, so the API is the source of truth for the current value.

## Check the current value

Call `GET /v1/model/info` and read `model_info.quantization`:

```bash
curl -sS https://api.tensorx.ai/v1/model/info \
  -H "Authorization: Bearer $TENSORX_API_KEY" \
  | jq '.data[] | {
      model: .model_name,
      quantization: .model_info.quantization
    }'
```

To inspect one model:

```bash
MODEL_ID="your-model-id"

curl -sS https://api.tensorx.ai/v1/model/info \
  -H "Authorization: Bearer $TENSORX_API_KEY" \
  | jq --arg model "$MODEL_ID" \
      '.data[] | select(.model_name == $model) | {
        model: .model_name,
        quantization: .model_info.quantization
      }'
```

The value identifies the weight format reported for the current deployment, such as `fp8`, `int4`, `mxfp4` or `nvfp4`. A `null` or absent value means that no quantisation value is published for that model.

## Interpreting the field

Quantisation reduces the memory and compute required to serve a model. The format is part of the deployed model configuration; it is not a request parameter and cannot be selected per call.

TensorX exposes one deployment configuration for each public model ID. If a workload requires a different precision or a dedicated deployment, contact <support@tensorx.ai>.

## See also

* [Models](/api-reference/models.md)
* [Chat Completions](/api-reference/chat-completions.md)
* [API Examples](/api-reference/api-examples.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tensorx.ai/api-reference/quantisation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.