SDKs Overview
Three ways to call the Ablatic API and when to use each
There are three ways to call the Ablatic API. Pick the one that fits your stack.
The three options
Official openai SDK, pointed at our base URL
Our /v1/chat/completions surface is OpenAI-compatible. Set base_url to https://api.ablatic.ai/v1, your key to sk-ablatic-..., and model to talos. Everything else stays the same. This is the fastest path if you already use the OpenAI SDK.
from openai import OpenAI
client = OpenAI(
base_url="https://api.ablatic.ai/v1",
api_key="sk-ablatic-...",
)Official anthropic SDK, pointed at our base URL
Our /v1/messages surface is a drop-in for the Anthropic Messages API. Set base_url to https://api.ablatic.ai, send your key as x-api-key, and call /v1/messages. This is the path for code already built on the Anthropic SDK, including Claude Code.
from anthropic import Anthropic
client = Anthropic(
base_url="https://api.ablatic.ai",
api_key="sk-ablatic-...",
)Native ablatic SDK
Our own SDK speaks the Ablatic API directly and exposes native extras that the compatibility surfaces do not, such as Glassbox confidence, refusal modes, and audit record access. Use it when you want those features without hand-rolling raw HTTP.
pip install ablaticnpm install ablaticWhen to use each
- Already on the OpenAI SDK: keep it, change three lines. See OpenAI compatibility.
- Already on the Anthropic SDK or Claude Code: keep it, change the base URL and key. See Anthropic compatibility.
- Want Glassbox confidence, refusal modes, or audit access in one client: use the native SDK.
All three send the same key format and hit the same backend. The native SDK is the only one that surfaces the Ablatic-specific fields directly.