Providers

Berget

AISDK provides first-class support for Berget with fully typed model APIs. Model capabilities are enforced at compile time using Rust's type system. This prevents model capability mismatches and guarantees the selected model is valid for the task (e.g. tool calling).

Installation

Enable the Berget provider feature:

cargo add aisdk --features berget

This installs AISDK with the Berget provider enabled. Once you have enabled the Berget provider, you can use all aisdk features with it.

Create a Provider Instance

To create a provider instance, call Berget::model_name(), where model_name is the Berget model you want to use. Model names are exposed as snake-case methods.

use aisdk::providers::Berget;

let berget = Berget::baai_bge_reranker_v2_m3();

This initializes the provider with:

  • Model: "BAAI/bge-reranker-v2-m3"
  • API key from environment (if set with BERGET_API_KEY)
  • Berget's default base URL (https://api.berget.ai/v1)

Basic Text Generation

Example using LanguageModelRequest for text generation.

use aisdk::{
    core::LanguageModelRequest,
    providers::Berget,
};

#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {

    let berget = Berget::baai_bge_reranker_v2_m3();

    let response = LanguageModelRequest::builder()
        .model(berget)
        .prompt("Write a short poem about Rust.")
        .build()
        .generate_text()
        .await?;

    println!("Response text: {:?}", response.text());
    Ok(())
}

Provider Settings

You can customize provider configuration using Berget::builder()

API Key

let berget = Berget::<BaaiBgeRerankerV2M3>::builder()
    .api_key("your-api-key")
    .build()?;

If not specified, AISDK uses the BERGET_API_KEY environment variable.

Base URL

Useful when routing through a proxy, gateway, or self-hosted compatible endpoint.

let berget = Berget::<BaaiBgeRerankerV2M3>::builder()
    .base_url("https://api.berget.ai/v1")
    .build()?;

Path (Full URL Override)

Use .path(...) to override the full request URL instead of only the base URL.

let berget = Berget::<BaaiBgeRerankerV2M3>::builder()
    .path("https://full-url.example/v1/chat/completions")
    .build()?;

Provider Name

For logging, analytics, and observability.

let berget = Berget::<BaaiBgeRerankerV2M3>::builder()
    .provider_name("Berget")
    .build()?;

Full Custom Configuration Example

let berget = Berget::<BaaiBgeRerankerV2M3>::builder()
    .api_key("your-api-key")
    .base_url("https://api.berget.ai/v1")
    .path("https://full-url.example/v1/chat/completions")
    .provider_name("Berget")
    .build()?;

Dynamic Model Selection

For runtime model selection (e.g., loading models from config files), use DynamicModel:

Using model_name() Method with Default Settings

use aisdk::providers::Berget;

// Specify model as a string at runtime
let berget = Berget::model_name("BAAI/bge-reranker-v2-m3");

Using Builder Pattern with Custom Settings

use aisdk::{
    core::DynamicModel,
    providers::Berget,
};

let berget = Berget::<DynamicModel>::builder()
	.model_name("BAAI/bge-reranker-v2-m3")
	.api_key("your-api-key")
	.base_url("https://api.berget.ai/v1")
	.path("https://full-url.example/v1/chat/completions")
	.provider_name("Berget")
	.build()?;

Warning: When using DynamicModel, model capabilities are not validated at compile time. This means there's no guarantee the model supports requested features (e.g., tool calls, structured output). For compile-time safety, use the typed methods like Berget::baai_bge_reranker_v2_m3().

Next Steps