LiteLLM Proxy

Set up

LiteLLM Proxy can be self-hosted or cloud-hosted by LiteLLM. Either way, each proxy has its own address, so the SDK cannot recognize it automatically. Pass the LiteLLM recipe with your proxy’s base URL:

import OpenAI from 'openai';
import { litellmRecipe } from '@stigg/agent-sdk-js';

const litellm = stigg.wrap(
  new OpenAI({ baseURL: 'https://litellm.example.com', apiKey: process.env.LITELLM_KEY }),
  { recipe: litellmRecipe({ baseUrl: 'https://litellm.example.com' }) },
);

await litellm.chat.completions.create({
  model: 'gpt-5',   // a model group from your proxy's config
  messages,
  stiggContext: { customerId: 'customer-acme', entitlement: { currencyId: 'credits' } },
});

To change how cost is counted, set unitsPerDollar on the recipe. See Gateways for the options.

What is reported

LiteLLM Proxy is a gateway, self-hosted or cloud-hosted: one API in OpenAI’s format in front of many model providers. Every response includes a usage object in OpenAI’s format with the token counts. LiteLLM also prices each call itself and returns that price in the x-litellm-response-cost response header. The wrapper reads both and reports them to Stigg as the metrics below. For details, see LiteLLM’s cost tracking and response headers docs.

Method	Event name
`chat.completions.create`	`litellm.chat.completions.create`
`responses.create`	`litellm.responses.create`

Chat Completions

Metric	What it counts
`prompt_tokens`	Input tokens, including cached tokens
`completion_tokens`	Output tokens
`cached_tokens`	Input tokens served from the cache
`total_tokens`	All input and output tokens, as reported by the vendor
`cost`	The price LiteLLM computed for the call, read from the `x-litellm-response-cost` header, in micro-dollars by default. Non-streaming calls only.

Responses

Metric	What it counts
`input_tokens`	Input tokens, including cached tokens
`output_tokens`	Output tokens
`cached_tokens`	Input tokens served from the cache
`total_tokens`	All input and output tokens, as reported by the vendor
`cost`	The price LiteLLM computed for the call, read from the `x-litellm-response-cost` header, in micro-dollars by default. Non-streaming calls only.

Cached tokens are counted inside prompt_tokens and input_tokens. If you price both the input metric and cached_tokens, cached tokens are billed twice. total_tokens includes all the token counts above, so price the total or the parts, never both. Each event also carries:

Reported	What it is
`model` dimension	The deployment that served the call.

Response headers are sent before the model generates anything, so a streamed LiteLLM call cannot carry a cost. Streamed calls report tokens only. If you bill on cost, use non-streaming calls or also price the token metrics.

Every usage field the vendor returns is also included, with a raw. prefix. See How usage is reported.

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