Skip to main content

Anthropic SDK

Use the official Anthropic SDK when you need native Anthropic request and response shapes rather than the OpenAI-compatible abstraction layer.

Use authToken, not apiKey, for client authentication to Sentinel:

import Anthropic from "@anthropic-ai/sdk";

const client = new Anthropic({
  authToken: process.env.SP_API_KEY!,
  baseURL: `${process.env.SENTINEL_BASE_URL!}/v1/anthropic`,
});

Why authToken matters​

Anthropic’s direct API auth model and Sentinel’s client auth model are not the same.

Clients authenticate to Sentinel. Sentinel then injects the upstream Anthropic credential itself. This keeps provider credentials out of the client while preserving the native Anthropic SDK surface.

Broadly documented surfaces​

Supported with caveats

Anthropic native support is strongest on the core messages path, but batch and file workflows should still be validated in the exact environment you plan to run.

Broadly documented surfaces include:

  • messages
  • streaming messages
  • models
  • message batches
  • files

Caveats​

  • validate batch and file workflows in the exact environment you plan to deploy
  • provider version requirements still apply operationally, especially for admin sync and provider configuration flows

A native Anthropic route can exist while still depending on provider-specific version metadata or workflow behavior.

Not broadly verified yet​

The following should not be treated as broadly verified by default:

  • treating every Anthropic SDK beta surface as production-ready
  • assuming admin sync or file behavior will work without checking provider version metadata