Migrating to the Agent SDK

Not yet available. The Agent SDK is tracked to be built — today, use the Client SDKs against the live chat completions API. The docs below describe the intended migration path.

The Agent SDK wraps the raw API with an agent loop: it manages state, runs tools, and applies stop conditions so you don't hand-roll the turn loop.

From chat completions#

Replace your manual messages loop with a single callModel:

TypeScript

// Before — manual loop over /v1/chat/completions
// After — the Agent SDK owns the loop, tools, and state
import { OpenDunes } from "@opendunes/agent-sdk";

const client = new OpenDunes({ apiKey: process.env.OPENDUNES_API_KEY });

const result = await client.callModel({
  model: "anthropic/claude-sonnet-5",
  messages: [{ role: "user", content: "Summarize the latest deploy." }],
  tools: [/* your tools */],
});

What changes#

Concern	Chat completions	Agent SDK
Turn loop	You write it	Managed
Tool calls	You dispatch + re-send	Dispatched for you
State	You track `messages`	Kept across turns
Billing	Per request, in DA	Per request, in DA (unchanged)

Next steps#

Call Model — the full API.
Client SDKs — if you want thinner, unopinionated clients instead.