SDKs overview
Official Breeth client libraries for Node.js and Python — thin wrappers around the REST API.
Breeth ships official SDKs in two languages. Both are thin wrappers around the REST API — same endpoints, same auth, idiomatic types.
Node.js
@breeth/sdk · ESM + CJS · zero runtime deps · TypeScript types built in.
Python
breeth · sync + async clients · Pydantic types · httpx under the hood.
When to use an SDK vs raw REST
| Use an SDK if | Use raw REST if |
|---|---|
| You're building in Node or Python | You're in another language (Go, Rust, Ruby…) |
| You want typed responses | You want zero dependencies |
| You'd rather not write your own retry/error class | You have your own HTTP layer |
The SDKs cover every public endpoint. If you want a feature the SDK doesn't expose, open an issue and we'll add it — the API surface is small and we keep parity.
Versioning
Both SDKs follow SemVer. Major version bumps are reserved for breaking changes; minor for additive endpoints; patch for fixes. The 0.x line is pre-1.0 — small breaking changes are still possible if we find them quickly.
Authentication
Both SDKs accept the same ck_live_… API keys you mint at thebreeth.com/app/api-keys. They can also read the key from an environment variable, so you don't have to hand-pass it.
// Node
const client = new BreethClient({ apiKey: process.env.BREETH_API_KEY! });# Python — env-var auto-read
client = BreethClient()Source code
Both SDKs are MIT-licensed. Source: