SDKs

SDKs

Official Python and TypeScript clients, generated one-to-one from the same contract this site renders.

Drazill publishes two official SDKs — Python (drazill) and TypeScript (drazill) — generated directly from the OpenAPI contract, so every resource and method maps to an API operation and cannot drift from it. They add the ergonomics you’d otherwise hand-roll: typed models, retries, idempotency options, cursor iteration, a WebSocket client, and webhook signature verification.

Generated surface

Both SDKs mirror the entire public contract. These counts are read directly from the SDK generators’ stamped README blocks (never retyped) and asserted equal across the two:

SDKGenerated surface
Python (drazill on PyPI)65 resource groups · 464 operations · 868 types
TypeScript (drazill on npm)65 resource groups · 464 operations · 868 types

Install

Both SDKs are published at 0.2.0 and carry the same package name on each registry — unscoped on npm, so drazill means the same thing in both ecosystems.

$pip install drazill      # PyPI
$npm install drazill      # npm

These are alpha packages, and an unconfigured client talks to staging (https://staging.drazill.com/api/v1) — never production. That is deliberate: production is not yet a separate live environment, and a published package cannot be recalled. Pass base_url= / baseUrl (or set DRAZILL_BASE_URL) to target another environment.

There are no Go or Rust SDKs. Only Python and TypeScript exist; if you need another language, generate a client from the pinned OpenAPI spec (GET /api/v1/openapi/v1.json).

Pick a language

Python

drazill — sync and async clients, install from source, tested quickstarts.

TypeScript

drazill — native fetch, typed models, WebSocket client.

Versioning

SDK releases track the API versioning policy (docs/api/VERSIONING.md): minor releases are additive (new resources/methods, backward-compatible), major releases carry breaking changes and are pre-announced through the Changelog. Pin the SDK version — and, if you generate your own client, pin the contract via GET /api/v1/openapi/v1.json (ETag-cached).

Docs MCP & AI agents

These docs expose a documentation MCP server at https://drazill.docs.buildwithfern.com/_mcp/server, plus per-page Markdown and llms.txt, for AI agents. That server searches and answers questions about the documentation — it is not a hosted API MCP that calls Drazill endpoints or holds keys, and none is offered today. Agents integrate the normal way: over HTTP with an X-API-Key header, or through these SDKs. See AI & agents for the full machine-readable surface and the safety rules an agent should carry into any integration.