Dobby SDKs

Dobby ships two SDK families. Most teams want the Collector — it streams your agent's activity to Dobby for governance + compliance. The Client SDK is an advanced tool for calling Dobby's APIs from your own code. Pick by job:

Collector SDK — Native Agent Telemetry

The Collector SDKs instrument YOUR agent code (LangChain / CrewAI / Gemini / Mastra / Vercel AI SDK / custom OpenAI scripts) and stream runs / tool calls / LLM calls to Dobby for governance + compliance scans. This is the path most customers start with.

Client SDK — Build on the Dobby APIAdvanced

The Client SDK is for building ON the platform — calling Dobby's APIs (LLM gateway, tasks, approvals, agent fleet, key management) from your own code, CI/CD, or another agent. Most customers don't need this; use the Collector above to get governance on your agents.

Don't confuse them — the Collector streams agent telemetry TO Dobby; the Client SDK calls Dobby's APIs. Different packages, different problems.

Quick Start

from dobby_sdk import DobbyClient

client = DobbyClient(api_key="gk_user_...")

# Make an LLM call through Dobby Gateway
response = client.chat.completions.create(
    model="claude-sonnet-4-6",
    messages=[{"role": "user", "content": "Hello from Dobby!"}],
)
print(response.choices[0].message.content)

# Create a task
task = client.tasks.create(title="Review PR #42", priority="high")

# Check costs
costs = client.costs.summary(period="30d")

Client SDK Capabilities

Authentication

All Client SDK calls are authenticated with a Dobby Gateway API key. You can pass it directly or set the DOBBY_API_KEY environment variable.