liter-llm-calling-llms
Use when sending chat completions through liter-llm and routing to a specific provider via the `provider/model` prefix. Covers the chat call shape, provider routing, model_hint, message roles, and error categories.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 265
- Forks
- 27
01 前言 Front Matter
- name
- liter-llm-calling-llms
- description
- Use when sending chat completions through liter-llm and routing to a specific provider via the `provider/model` prefix. Covers the chat call shape, provider routing, model_hint, message roles, and error categories.
02 资源文件 1
- 参考文档index.md499 B
03 SKILL.md 正文
<!-- AI-RULEZ :: GENERATED FILE — DO NOT EDIT Content-Hash: blake3:d45c8ad7f731f0e0bc91646e677fd7c89b6af31e38944bff4302e7e242a12906 Source-Hash: blake3:725e6663621cbc5ffbaf9dbb2141fe5f9b95aee234fe9f7ece2d2b6e63dc5a66 Schema-Version: v1 -->
Calling LLMs
Build a ChatCompletionRequest and send it with client.chat(request). Create
the client with create_client(...). The model string is provider/model; the
prefix selects the backend.
import asyncio, json, os
from liter_llm import create_client
from liter_llm._internal_bindings import ChatCompletionRequest
async def main() -> None:
client = create_client(api_key=os.environ["OPENAI_API_KEY"])
request = ChatCompletionRequest.from_json(json.dumps({
"model": "openai/gpt-4o",
"messages": [
{"role": "system", "content": "You are concise."},
{"role": "user", "content": "Name three Rust crates for HTTP."},
],
}))
response = await client.chat(request)
print(response.choices[0].message.content)
asyncio.run(main())
Provider routing
The model string's prefix selects the provider; build a request per backend:
ChatCompletionRequest.from_json('{"model":"anthropic/claude-sonnet-4-20250514","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"gemini/gemini-2.0-flash","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"groq/llama3-70b","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"mistral/mistral-large-latest","messages":[...]}')
ChatCompletionRequest.from_json('{"model":"bedrock/anthropic.claude-v2","messages":[...]}')
Set a full provider/model as model_hint at construction to select the client
provider and credential source. Requests without a recognized prefix fall back to
that client provider:
client = create_client(api_key=os.environ["OPENAI_API_KEY"], model_hint="openai/gpt-4o")
# the request model can now omit the provider prefix:
request = ChatCompletionRequest.from_json('{"model":"gpt-4o","messages":[...]}')
await client.chat(request) # routes to OpenAI
Notes
- Keys come from env vars (
OPENAI_API_KEY,ANTHROPIC_API_KEY, …); never hardcode them. - Without a recognized prefix, requests fall back to the client's configured provider;
a client without
model_hintdefaults to OpenAI. - Environment credentials are selected when constructing the client, not independently
for every request. Use a separate client with matching
model_hintand credentials for each provider. A prefix changes routing but does not switch the client's API key. - Python errors are typed exceptions exported from
liter_llm:AuthenticationError,RateLimitedError,BadRequestError,ContextWindowExceededError,ContentPolicyError,NotFoundError,ServerError,ServiceUnavailableError,LiterLlmTimeoutError,BudgetExceededError— all subclasses ofLiterLlmError.
04 同仓库更多 Skills
liter-llm
Universal LLM API client for 174 providers with native bindings for 14 languages. Use when writing code that calls LLM APIs via liter-llm in Python, TypeScript, Rust, Go, Java, C#, Ruby, PHP, Elixir, WASM, or C, when running the OpenAI-compatible proxy, or when calling LLMs through the MCP server. Covers chat, streaming, tool calling, embeddings, image generation, speech, transcription, moderation, web search, OCR, reranking, provider routing, middleware, and configuration.
liter-llm-using-the-mcp-server
Use when calling LLM APIs through the liter-llm MCP server's 22 tools, and to decide when MCP beats the CLI or SDK. Covers the tool surface, the auto-installing launcher, and authentication.
liter-llm-tool-calling
Use when defining functions/tools for an LLM to call through liter-llm, or requesting structured JSON outputs. Covers tool schemas, tool_calls handling, and response formats.
liter-llm-streaming-responses
Use when streaming tokens incrementally from an LLM via liter-llm over SSE or async iterators. Covers chat_stream, delta handling, and null-content chunks.
liter-llm-running-the-proxy
Use when running the `liter-llm api` OpenAI-compatible gateway — virtual keys, per-key rate limits, budgets, cost tracking, and model routing. Covers the TOML config and the 22 REST endpoints.
liter-llm-embeddings-and-search
Use when generating embeddings, calling the 12 web-search providers, or running OCR over documents with the 4 OCR providers through liter-llm. Covers embed, search, and ocr methods plus reranking.