Supported providers & frameworks

This is the single support surface. If your provider is in the first table you are done after Get started — install the SDK, call tp.init(), and your calls are metered. Frameworks sometimes need one extra step, listed in the second table.

For which library versions are supported, see Supported versions. This page is about what is covered, not which release of it.

Providers

Every provider below is metered on the base install — pip install token-police / npm i token-police — with the two exceptions marked in the table. In Node, install the provider package you already use (they are optional peer dependencies) and TokenPolice taps it.

Streaming is metered everywhere in this table. Usage is recorded when the stream finishes, so a streamed call shows up with the same token counts and cost as a non-streamed one.

import OpenAI from "openai";
tp.init({ /* … */ instrumentModules: { openAI: OpenAI } });

Beyond chat

Non-chat calls are metered too and land in the dashboard tagged with their own operation, so a rule can target them separately from chat:

A rule on operation is embedding is handy for RAG: it stops a runaway re-embed loop without touching your chat traffic.

Known gaps. Rerank endpoints (Cohere, Voyage), moderation endpoints, and OpenAI images.edit / images.createVariation are not metered. Cover them with protect() and a provider= hint if you need them counted.

Frameworks

Tool spans say whether the tool calls inside an agent run appear as their own steps in the dashboard. Where the column says manual — as it does for hand-rolled tool loops and MCP tools in any framework — the model calls are still metered and still enforced; the tool steps simply don't get their own entry in the trace.

Python extras

pip install "token-police[langchain]"    # or llamaindex, pydantic-ai, openai-agents, agno, xai, voyageai
pip install "token-police[crewai]"       # CrewAI has its own extra and is not part of [all]
pip install "token-police[all]"          # every framework extra except crewai

[all] deliberately leaves CrewAI out: CrewAI supports Python 3.10–3.13 but not 3.14 yet, so keeping it separate is what lets [all] install everywhere. If you use CrewAI, install token-police[crewai] (on its own, or alongside [all]).

Pins & conflicts to know about

These are environment caveats, not things TokenPolice enforces — but they trip people up at install time:

• Mistral (Python): mistralai 1.x and 2.x are both supported — no pin needed. On 2.x the client import moved: from mistralai.client import Mistral (on 1.x it stays from mistralai import Mistral). On mistralai 2.0–2.9.1, pip may install an older OpenTelemetry train to satisfy that release's own cap; it still works, and mistralai>=2.9.2 drops the cap.
• CrewAI (Python): installs may print a benign resolver warning — safe to ignore. Strict resolvers (uv, Poetry, pip-tools) sometimes need a two-step install: CrewAI first, then token-police[crewai]. Set CREWAI_DISABLE_TELEMETRY=true to quiet CrewAI's own tracing noise.
• Don't downgrade TokenPolice's own dependencies. Older versions of them undercount Bedrock Converse usage; the pins that ship with the SDK are the tested ones.
• Never set OTEL_SDK_DISABLED=true. It turns off tracing globally — including TokenPolice's own instrumentation, so nothing gets metered.

Next