thinchat
English | 한국어
One interface for four LLM providers — claude, openai, gemini, ollama — that treats not leaking your API key as part of the job.
Name a provider, then call it: completion (whole, streamed, or JSON-structured) and, where the provider has one, embeddings — each with an async twin, over the openai and anthropic SDKs. No gateway, no router, no cost tracking — just the calls, plus the parts you'd otherwise hand-roll:
- Leak-safe keys. Your key is a credbox
Secret(masked in logs and tracebacks), revealed only at the SDK call. On a failure, thinchat severs the SDK error's chain and scrubs the message so the key never rides out on a traceback — and it pins each provider's official endpoint, so an environment variable can't redirect a resolved key to another host. - One shared credential store.
thinchat set claudesaves a key once to a 0600 store that every session — and every sibling tool — resolves from; or just use<PROVIDER>_API_KEYfrom the environment (the library core reads no file unless you ask). - The fiddly bits, handled. Structured output parses tolerant JSON into a dict; embeddings
return one alignment-checked vector per input;
RateLimitErrorcarriesretry_after;supports()reports a provider's capabilities before you call.
1. Install
pip install thinchat
Requires Python 3.11+. Both provider SDKs (openai and anthropic) come with it, so every provider works out of the box; each is imported lazily the first time you construct its client.
2. Use
from thinchat import make_client
llm = make_client("claude") # key from CLAUDE_API_KEY (see §3)
print(llm.complete("Say hi in one word."))
print(llm.complete("Name a color.", system="Answer in one word.")) # system= steers the generation verbs
# Structured output: you invent the schema; the model fills a JSON object into that shape.
# It steers generation but is not validated locally, so check the returned fields yourself.
review = llm.parse(
"Analyze the sentiment: 'Fast shipping and great quality.'",
schema={"type": "object",
"properties": {"sentiment": {"type": "string"}, "score": {"type": "number"}},
"required": ["sentiment"]},
)
print(review["sentiment"])
# Streaming.
for chunk in make_client("claude").stream("Count to five."):
print(chunk, end="")
# Embeddings (openai / gemini / ollama supported; not claude).
vectors = make_client("openai").embed(["hello", "world"])
complete returns a Completion — a str you can use directly as text that also carries the
reply's metadata, so you can tell a finished reply from one cut off at the token cap:
reply = make_client("claude", max_tokens=50).complete("Write a long essay on rivers.")
print(reply) # a str: prints, slices, compares like any string
if reply.truncated: # True when the reply hit the token cap
print(f"cut off (finish_reason={reply.finish_reason})") # .usage / .model also available
Every verb has an async twin — acomplete, astream, aparse, aembed:
import asyncio
async def main():
llm = make_client("claude")
text = await llm.acomplete("Summarize in one line: ...")
asyncio.run(main())
3. API keys
thinchat resolves a provider's key three ways, listed most-recommended first. (When more than one
is set, precedence runs the other way: api_key= > environment > stored file.)
1. Save it to the store — the thinchat command writes a 0600 store
(~/.config/thinchat/credentials.json) that persists across sessions, so you set a key once
and every session finds it — no re-export, no key sitting in a shell profile; this shared store is
what the tool adds. The full value is never printed (set reads it without echo; get shows it
masked, edges only):
thinchat set claude # prompt for the key (no echo), store it
thinchat list # which providers have a stored key
thinchat get claude # show the resolved key, masked
thinchat unset claude # remove it
2. An environment variable <PROVIDER>_API_KEY — the standard for a container, CI, or a
one-off shell session:
export CLAUDE_API_KEY="sk-ant-..." # or OPENAI_API_KEY / GEMINI_API_KEY; ollama needs none
3. Pass it directly — when your app manages its own secrets; no file is ever read:
llm = make_client("claude", api_key="sk-ant-...")
An environment variable always wins over the stored file, so a container or CI overrides the
store by setting <PROVIDER>_API_KEY — no file needed. The same operations are available in
Python, so a parent application can populate or read the store for its user:
from thinchat import set_api_key, get_api_key, stored_providers, unset_api_key
set_api_key("claude", value="sk-ant-...")
key = get_api_key("claude") # a credbox Secret | None (masked in repr/str/logs; .reveal() for plaintext)
stored_providers() # ["claude", ...] — which providers are in the store
unset_api_key("claude")
Claude uses
CLAUDE_API_KEY, not the anthropic SDK's ownANTHROPIC_API_KEY. thinchat always passes the resolved key to the SDK explicitly, so a strayANTHROPIC_API_KEYin the environment is never picked up.
4. Providers
| provider | key env | embeddings |
|---|---|---|
claude |
CLAUDE_API_KEY |
no |
openai |
OPENAI_API_KEY |
yes |
gemini |
GEMINI_API_KEY |
yes |
ollama |
none (local) | yes |
openai, gemini, and ollama speak the same OpenAI-compatible API, so one SDK serves all three;
only the base URL, key, and default models differ. Ollama runs locally (OLLAMA_HOST, default
http://localhost:11434) and needs no key.
Each provider takes the settings it exposes under the same name, sent only when you set them:
max_tokens (reply length), temperature / top_p (sampling), and timeout in seconds /
max_retries (the HTTP client) — e.g. make_client("claude", temperature=0.2, timeout=30). An
unset value leaves the provider's own default in place, except max_tokens, which Anthropic
requires and so defaults to 4096 for claude (the OpenAI-compatible providers omit it, letting the
model decide). Any verb also takes a per-call model= and an extra={...} passthrough (§9).
To reach a gateway, proxy, or Azure-style endpoint, pass base_url= to make_client
(make_client("openai", base_url="https://gateway.internal/v1")). When you do not, thinchat pins
each provider's official endpoint rather than leaving it unset — so the vendor SDK never reads its
own OPENAI_BASE_URL / ANTHROPIC_BASE_URL variable, closing a path where anything able to write
the environment (but not read the 0600 store) could redirect a resolved key to another host.
Ollama still resolves its local endpoint from OLLAMA_HOST.
5. Capabilities
A client whose provider lacks a capability raises UnsupportedError. The capabilities are
completion, streaming, structured_output, and embeddings; check first with supports:
make_client("claude").supports("embeddings") # False
6. Errors
Everything thinchat raises on purpose derives from ThinchatError, so one except handles
the package's failures:
UnknownProviderError— the name isn't one of the four providers.ProviderUnavailableError— the provider's SDK isn't installed, or no API key is set.UnsupportedError— the operation isn't available for the provider: a missing capability (e.g. embeddings on Claude), or storing a key for keyless ollama.BlankKeyError—set_api_key(orthinchat set) was given an empty or whitespace key. It is also aValueError, soexcept ValueErrorcatches it too.CredentialStoreError— the stored-key file (~/.config/thinchat/credentials.json) is present but unreadable or malformed, or could not be written.LLMError— the API call failed, or the reply was empty or malformed. Itsstatus_codeis the HTTP status when one was available (branch on it to tell a transient 5xx worth retrying from a permanent 4xx); the API key is redacted from the message and its cause chain.AuthError— the credentials were rejected (HTTP 401/403): a missing, invalid, or revoked key, or one without access. A subclass ofLLMError, soexcept LLMErrorstill catches it.RateLimitError— a 429 rate limit after the SDK's own retries. It is a subclass ofLLMError, so existing handlers still catch it, and itsretry_afteris how many seconds to wait before trying again (from the server's Retry-After), orNonewhen the server did not give one.
The vendor SDK performs the actual backoff through max_retries, honoring Retry-After;
thinchat adds no retry loop.
from thinchat import make_client, RateLimitError
with make_client("gemini") as llm:
try:
print(llm.complete("Say hi."))
except RateLimitError as e:
print(f"rate limited; wait {e.retry_after} seconds")
7. Lifecycle
A client holds an HTTP connection pool. For a one-off script you can ignore it; for a
server that builds a client per request, close it so connections do not leak — use it as a
context manager, or call close() / aclose():
with make_client("claude") as llm:
llm.complete("...") # sync: closes the pool on exit
async with make_client("claude") as llm:
await llm.acomplete("...") # async: closes the async pool too
close() frees the sync pool; if you drove async verbs, release with aclose() or
async with so the async pool is closed as well.
If you stop consuming an async stream early — a break out of async for, or a client
disconnect — close it promptly so its connection returns to the pool instead of waiting for the
event loop to finalize the generator: async with aclosing(llm.astream(...)) as s: (from
contextlib), or await s.aclose(). A sync stream releases on break by itself; only the
async stream needs this.
8. How it works
%%{init: {'theme':'base','themeVariables':{'fontSize':'18px','fontFamily':'ui-sans-serif, system-ui, sans-serif','lineColor':'#94a3b8'}}}%%
flowchart LR
M(["<b>make_client</b><br/>(provider)"]):::entry
C["<b>Client</b><br/>openai-compatible<br/>or claude"]:::client
V["<b>complete · stream</b><br/><b>parse · embed</b><br/>+ async twins"]:::verb
S("<b>vendor<br/>SDK</b>"):::sdk
O(["<b>Completion(str)</b><br/>dict · list[float]<br/>stream"]):::ok
E(["<b>LLMError</b><br/>AuthError<br/>RateLimitError (429)"]):::err
M --> C --> V --> S
S -->|ok| O
S -->|"SDK / transport error"| E
classDef entry fill:#6366f1,color:#ffffff,stroke:#4338ca,stroke-width:1px;
classDef client fill:#eef2ff,color:#1e293b,stroke:#6366f1,stroke-width:1px;
classDef verb fill:#ecfeff,color:#0f172a,stroke:#06b6d4,stroke-width:1px;
classDef sdk fill:#fef9c3,color:#0f172a,stroke:#eab308,stroke-width:1px;
classDef ok fill:#dcfce7,color:#14532d,stroke:#22c55e,stroke-width:1px;
classDef err fill:#fee2e2,color:#7f1d1d,stroke:#ef4444,stroke-width:1px;
make_client looks the provider up in one factory map: openai/gemini/ollama share a single
class over the openai SDK (they differ only in data); claude has its own over anthropic.
A call builds the request, hits the SDK, and either extracts the reply or maps the failure
to an LLMError (AuthError for 401/403, RateLimitError for a 429 after the SDK's retries).
9. Scope & stability
thinchat is intentionally a single-turn completion client: each call takes one prompt plus
an optional system and returns the reply as text (a Completion, a str that also carries
.finish_reason / .truncated / .usage / .model) — or a JSON object / vectors. It does
not cover multi-turn conversation history, tool/function calling, token/usage & cost
reporting, or vision / other multimodal input — for those, use the provider SDK directly.
parse() steers the reply toward your schema but does not enforce it (§2), and embed() raises
TypeError (not a ThinchatError) if handed a single string instead of a list.
Every verb takes an optional per-call model= (overriding the client's default for that call)
and extra={...}, a dict merged into the provider request for one-off provider-specific fields
(OpenAI seed, Anthropic thinking, ...) — such fields are provider-specific and are not
translated across providers, and they only reach the request, not the response (the reply is
still text). The default model and max_tokens per provider track current provider defaults
and are not pinned — pass model= / max_tokens= for reproducibility. Secret is re-exported
from credbox, which governs its masking and .reveal().
Pre-1.0 (0.x): the provider roster and its order, the error hierarchy, the make_client and
key-management signatures, and the Secret return type are stable (pinned by tests); the default
models and the message text of a bare LLMError may change between releases.
10. Development
Clone, install the dev extras, and run what CI runs:
uv venv && uv pip install -e ".[dev]"
make check # test + lint + types (or: pytest -q && ruff check src tests && mypy)
CI additionally builds the package and asserts that a base install imports no provider SDK
eagerly and ships py.typed.
11. License
Metadata
Release files for thinchat 0.3.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 | |
|---|---|---|---|
| thinchat-0.3.0.tar.gz | 70.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| thinchat-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 111.1 kB
Release files / thinchat-0.3.0.tar.gz
| Download URL | thinchat-0.3.0.tar.gz |
|---|---|
| Size | 70.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2856464ebf80a3b447c1e6269cefa43bd044e182cff48dff010db74443317a88
|
|
BLAKE2b-256 checksum How to use checksums |
ff503a5095f2f19560129a2fe633ba00ba59a78886e7514c5d91387034bee82b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Sep 12, 2026.
Transparency logRelease files / thinchat-0.3.0-py3-none-any.whl
| Download URL | thinchat-0.3.0-py3-none-any.whl |
|---|---|
| Size | 40.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a4a2badc5ce0cef9a00fcad05b064d7ff2dd8725d8b5553fbb3b2a44f4b95ce
|
|
BLAKE2b-256 checksum How to use checksums |
709a945bbdd491fd17ac33018ada1ef0d5dfda3516fd61fa12b6c2111f8ce16d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Sep 12, 2026.
Transparency log