DeepSeek

DeepSeek serves its own DeepSeek models. Its API follows OpenAI’s format, so you wrap it with the OpenAI client and the SDK meters it with the OpenAI recipe.

Set up

Point the OpenAI client’s baseURL at DeepSeek and wrap it:

import OpenAI from 'openai';

const deepseek = stigg.wrap(
  new OpenAI({ baseURL: 'https://api.deepseek.com', apiKey: process.env.DEEPSEEK_API_KEY }),
);

const response = await deepseek.chat.completions.create({
  model,
  messages,
  stiggContext: { customerId: 'customer-acme', entitlement: { currencyId: 'credits' } },
});

What is reported

DeepSeek returns a usage object in OpenAI’s format with the number of tokens each call consumed. Calls are reported under the openai.chat.completions.create event name, with the same metrics as OpenAI. DeepSeek reports its cache usage in its own fields, prompt_cache_hit_tokens and prompt_cache_miss_tokens, rather than OpenAI’s cached_tokens. If the cached_tokens metric stays at zero for your DeepSeek traffic, build a meter on raw.prompt_cache_hit_tokens to meter cache hits. Every usage field the provider returns is also included, with a raw. prefix. See How usage is reported. For details on DeepSeek’s API, see DeepSeek’s API docs and context caching guide.

Getting started

Developer tools

Governance (Beta)

AI agents and LLMs (Beta)

Modeling your pricing in Stigg

Entitlements

Managing customers, subscriptions and contracts

Getting usage data into Stigg

Snap-in widgets

Importing and exporting data

Going live

Workflow automation

Rolling out pricing changes with confidence

Price localization

Managing your account

High-availability and scale

Security & compliance

Set up

What is reported

​Set up

​What is reported

Set up

What is reported