Poe

AISDK provides first-class support for Poe 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 Poe provider feature:

cargo add aisdk --features poe

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

Create a Provider Instance

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

use aisdk::providers::Poe;

let poe = Poe::anthropic_claude_haiku_3();

This initializes the provider with:

Model: "anthropic/claude-haiku-3"
API key from environment (if set with POE_API_KEY)
Poe's default base URL (https://api.poe.com/v1)

Basic Text Generation

Example using LanguageModelRequest for text generation.

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

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

    let poe = Poe::anthropic_claude_haiku_3();

    let response = LanguageModelRequest::builder()
        .model(poe)
        .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 Poe::builder()

API Key

let poe = Poe::<AnthropicClaudeHaiku3>::builder()
    .api_key("your-api-key")
    .build()?;

If not specified, AISDK uses the POE_API_KEY environment variable.

Base URL

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

let poe = Poe::<AnthropicClaudeHaiku3>::builder()
    .base_url("https://api.poe.com/v1")
    .build()?;

Path (Full URL Override)

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

let poe = Poe::<AnthropicClaudeHaiku3>::builder()
    .path("https://full-url.example/v1/chat/completions")
    .build()?;

Provider Name

For logging, analytics, and observability.

let poe = Poe::<AnthropicClaudeHaiku3>::builder()
    .provider_name("Poe")
    .build()?;

Full Custom Configuration Example

let poe = Poe::<AnthropicClaudeHaiku3>::builder()
    .api_key("your-api-key")
    .base_url("https://api.poe.com/v1")
    .path("https://full-url.example/v1/chat/completions")
    .provider_name("Poe")
    .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::Poe;

// Specify model as a string at runtime
let poe = Poe::model_name("anthropic/claude-haiku-3");

Using Builder Pattern with Custom Settings

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

let poe = Poe::<DynamicModel>::builder()
	.model_name("anthropic/claude-haiku-3")
	.api_key("your-api-key")
	.base_url("https://api.poe.com/v1")
	.path("https://full-url.example/v1/chat/completions")
	.provider_name("Poe")
	.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 Poe::anthropic_claude_haiku_3().

Next Steps

Take a deeper look at text generation features Generating Text / Streaming Text
Explore Structured Output for reliable agent data.
Learn how to create Custom Tools.
Learn more about Agents.

Poe

On this page