> For the complete documentation index, see [llms.txt](https://langtech-bsc.gitbook.io/applied-intelligence/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://langtech-bsc.gitbook.io/applied-intelligence/models/text-models/prelude-9b.md).

# Prelude-9b

A 9B reasoning model for function calling and multi-turn agentic tool use, post-trained at BSC on the OpenEuroLLM Prelude base. Coming soon.

{% hint style="warning" %}
**Coming soon.** This is a preview. Download links, usage instructions and evaluation results will be added when the model is released.
{% endhint %}

**Prelude-9b** is a post-trained version of [Prelude](https://huggingface.co/openeurollm/prelude-base), the 9B base model pre-trained from scratch by the [OpenEuroLLM](https://openeurollm.eu/) consortium. At BSC we are turning it into a model for **function calling and multi-turn agentic tool use with explicit reasoning**, small enough to run on a single GPU.

## What it's for

* **Agents** that chain several tool calls and need to plan before acting.
* Function calling over **long inputs**, such as documents and long conversations.
* Deployments where a 40B model is too large but tool-use quality still matters.


---

# 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://langtech-bsc.gitbook.io/applied-intelligence/models/text-models/prelude-9b.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.
