thinwrap-llm (Python)
Unified, SDK-free, zero-runtime-dependency Python wrapper for chat
completions (with streaming) and embeddings across 18 LLM providers. Switch
vendor by changing the provider id + model; the input and output shapes stay
identical. Synchronous, stateless, standard-library-only — bring your own HTTP
transport if you want httpx/requests.
pip install thinwrap-llm
Requires Python ≥ 3.10. No runtime dependencies — Bedrock's SigV4 is hmac-based
and SSE is parsed on the stdlib.
Two-minute chat
from thinwrap.llm import Chat, ChatInput, ChatMessage, OpenAICompatConfig, ProviderID, ConnectorError
chat = Chat(ProviderID.OPENAI, OpenAICompatConfig(api_key="..."))
try:
res = chat.complete(ChatInput(
model="gpt-4o-mini",
messages=[ChatMessage(role="user", content="Say hi in one word.")],
))
print(res.message.content, res.usage.total_tokens)
except ConnectorError as e:
print(e.provider_code.value, e.provider_message)
Streaming
for delta in chat.stream(ChatInput(model="gpt-4o-mini", messages=msgs)):
print(delta.content_delta, end="", flush=True)
A stream that is cut off before the provider's terminal event, or a 2xx answer
that is not text/event-stream, raises ConnectorError (provider_unavailable)
rather than ending as if it were complete.
Usage
res.usage counts every billed token: input_tokens includes cache reads and
writes (Anthropic, Bedrock), output_tokens includes thinking tokens (Gemini), and
total_tokens is the vendor's total, or input + output when it reports none. When
streaming, usage arrives once, on the terminal delta.
Tool loops and provider_metadata
Some providers need opaque state from a response sent back on the next turn:
Gemini 3 rejects a replayed function call without its thought signature, and
Anthropic keeps its thinking blocks only if they are replayed verbatim.
ToolCall.provider_metadata and AssistantMessage.provider_metadata carry that
state, keyed by provider id ({"gemini": {...}}, {"anthropic": {...}}). Treat it
as opaque and copy it into the next request together with content and
tool_calls:
res = chat.complete(ChatInput(model=model, messages=msgs, tools=tools))
msgs.append(ChatMessage(role="assistant", content=res.message.content,
tool_calls=res.message.tool_calls,
provider_metadata=res.message.provider_metadata))
When streaming, the state rides on tool_call_delta.provider_metadata (copy it
onto the ToolCall you assemble) and on the terminal delta's provider_metadata.
A connector reads only its own key, so a history survives a provider switch. If the
state is lost, Gemini falls back to Google's documented signature bypass, and
Anthropic rebuilds that turn and every later one without their thinking (Anthropic
invalidates thinking after a stripped turn), so the earlier reasoning is lost.
Providers
The provider id selects the connector; ChatInput / ChatResult are
identical across all of them.
Chat (18): the 15 first-class OpenAI-compatible providers —
ProviderID.OPENAI, AZURE_OPENAI, OPENROUTER, GROQ, TOGETHER,
FIREWORKS, DEEPSEEK, XAI, MISTRAL, PERPLEXITY, DEEPINFRA,
CLOUDFLARE, VLLM, OLLAMA, LMSTUDIO — all take OpenAICompatConfig; plus 3
natives: ANTHROPIC (AnthropicConfig), BEDROCK (BedrockConfig), GEMINI
(GeminiConfig).
Embeddings (11): the OpenAI-float subset — OPENAI, AZURE_OPENAI,
OPENROUTER, TOGETHER, FIREWORKS, MISTRAL, DEEPINFRA, CLOUDFLARE,
VLLM, OLLAMA, LMSTUDIO.
from thinwrap.llm import Embeddings, EmbeddingsInput, OpenAICompatConfig, ProviderID
emb = Embeddings(ProviderID.OPENAI, OpenAICompatConfig(api_key="..."))
out = emb.create(EmbeddingsInput(model="text-embedding-3-small", input=["hello", "world"]))
# out.embeddings is list[list[float]] in input order
Per-provider details live in docs/providers/.
The ≥90% baseline & passthrough
Only fields ≥90% of providers support normalizably are first-class on
ChatInput / ChatResult; everything else rides through Passthrough (request)
/ raw (response) and is never emulated:
from thinwrap.llm import Passthrough
res = chat.complete(ChatInput(model="...", messages=msgs,
passthrough=Passthrough(body={"logprobs": True})))
_ = res.raw # verbatim vendor body — reasoning CoT, cached-token counts, cost, ...
Errors
Every failure raises ConnectorError: provider_code is one of rate_limited,
auth_failed, provider_unavailable, invalid_request,
context_length_exceeded, content_filtered, unknown. The raw Retry-After
rides in cause["retryAfter"] (+ parsed cause["retryAfterSeconds"]) — there is
no top-level retry attribute. retryAfterSeconds is set only for an integer delay
or an HTTP-date (0 when the date has passed).
By HTTP status: 401/403 → auth_failed; 402 (out of credit) / 429 →
rate_limited; 408 / 5xx → provider_unavailable; every other 4xx →
invalid_request, unless the vendor's context-overflow or content-filter signal
matches. An error delivered inside a 2xx body or mid-stream keeps the HTTP status it
arrived with and is classified by its own code or type (unknown without one).
Bring your own transport
chat = Chat(ProviderID.OPENAI, OpenAICompatConfig(api_key="..."), transport=my_transport)
my_transport implements Transport (send(HttpRequest) -> HttpResponse); add
an open_stream method for true incremental streaming (otherwise a buffered
fallback is used). The default stdlib urllib transport does both, never
follows redirects, and is HTTPS-only: the http:// defaults of the local servers
(vLLM, Ollama, LM Studio) get an invalid_request telling you to bring your own
transport. Its socket timeout is 600 s per blocking read, so a long non-streaming
reasoning call is not cut off; pass UrllibTransport(timeout=...) for a different
budget. The wrapper is stateless — no caching, retries, or conversation memory.
Relationship to the siblings
One of four thinwrap llm libraries sharing a normalized surface and
byte-identical provider ids / error codes: TypeScript (@thinwrap/llm), PHP
(thinwrap/llm), Go (thinwrap/llm-go), Python (this package).
Security
Report vulnerabilities privately — please do not open a public issue. Preferred: a private security advisory on this repository. Alternatively, email security@thinwrap.dev. Include the affected versions and a minimal reproduction if you have one.
A vulnerability in a provider's own API or service belongs to that vendor rather than to this wrapper — please report those upstream.
License
MIT © Dmitry Polyanovsky & contributors
Metadata
Release files for thinwrap-llm 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| thinwrap_llm-1.1.0.tar.gz | 71.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| thinwrap_llm-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 127.4 kB
Release files / thinwrap_llm-1.1.0.tar.gz
| Download URL | thinwrap_llm-1.1.0.tar.gz |
|---|---|
| Size | 71.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f15fe2a2021c84560d9af37830612132e191c7316eb29a26af01b4cf4dc368c
|
|
BLAKE2b-256 checksum How to use checksums |
3f633b35f0bcc727f582469c59af4f08bc0261386130556caef8bfe66e77612d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / thinwrap_llm-1.1.0-py3-none-any.whl
| Download URL | thinwrap_llm-1.1.0-py3-none-any.whl |
|---|---|
| Size | 56.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
194dd5c7c11fa790cb0515188b76bbced322901ca8fa20c559ee15d6ed3e42ce
|
|
BLAKE2b-256 checksum How to use checksums |
f0a212d97150f0a2a86548a747fd6c376b8b2460f5f5995b217b3f5d7638f4c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logSecurity for thinwrap-llm 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for thinwrap_llm-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.