Expand description
Raw, provider-specific request/response types.
Each sub-module maps directly to a provider’s JSON schema and is used
internally by the Request dispatch layer.
The shared module contains types common across providers (e.g.
ToolDefinition).
Most users should interact through Request and never
need to touch these types directly.
Re-exports§
pub use shared::FunctionDefinition;pub use shared::FunctionName;pub use shared::JsonSchemaBody;pub use shared::ResponseFormat;pub use shared::ToolChoice;pub use shared::ToolChoiceFunction;pub use shared::ToolChoiceMode;pub use shared::ToolDefinition;pub use shared::ToolKind;
Modules§
- anthropic
- deepseek
- gemini
- Gemini provider — supports
generationConfig.thinkingConfigandthoughtSignatureround-trip. - glm
- grok
- kimi
- mimo
- Mimo (xiaomimimo) provider — Anthropic-compatible API at
https://api.xiaomimimo.com/anthropic/v1/messages. - openai
- OpenAI provider — targets the Responses API (
POST /v1/responses) exclusively. Chat Completions is no longer reachable viaProvider::OpenAI; route toProvider::OpenRouter(with a custombase_url) for OpenAI-compatible servers that don’t implement/responses. - openrouter
- OpenRouter provider — OpenAI-Chat-compatible proxy with a unified reasoning abstraction across underlying models.
- shared
- Shared wire-format types used across all provider modules.