Adding pricing for new or unreleased LLMs in LangSmith cost tracking

Last updated: November 11, 2026

Overview

LangSmith tracks cost using a built-in model price map, which is updated separately from model release dates. On SaaS, a daily job pulls current prices from model.dev. On self-hosted, built-in prices only update through a database migration bundled into a LangSmith image or Helm chart upgrade, since self-hosted installs don't pull live from an external registry. This means a newly released model's price often isn't in the built-in map yet, on either deployment type, and self-hosted installs can lag further behind until they upgrade.

If you want cost tracking or evals to work for a model before built-in pricing ships, add a price entry yourself.

Adding a custom price entry

Via the UI, go to workspace Settings > Model pricing and add an entry matching the exact provider and model identifier used in your traces.

Via the REST API, call POST /api/v1/model-price-map with fields including:

  • name: a label for the entry

  • match_pattern: a regex matched against the model name as it appears in your traces

  • prompt_cost and completion_cost: per-token costs

  • prompt_cost_details (optional): additional cost fields, e.g. cache-read cost

Price-map entries only apply prospectively. They don't recalculate cost for traces already logged before the entry was added.

Org-level vs. workspace-level pricing

You can set a price once at the organization level, and every workspace uses it automatically, including workspaces created afterward. A workspace can still set its own override, which takes precedence over the org-level entry for that workspace. Configure this via the UI or the REST API at /api/v1/orgs/current/model-price-map.

Org-level pricing is available on LangSmith SaaS and on self-hosted from Helm chart langsmith-0.18.0-rc.63 onward (0.18 release line). On earlier self-hosted versions, price-map entries are workspace-scoped only: an entry added in one workspace doesn't apply to others, and new workspaces inherit only the built-in prices, not any custom entry you've added elsewhere. In that case you need to add the entry to each workspace individually, for example by looping over workspace IDs with the REST API.

Model configuration vs. pricing

Model configuration (registering a custom provider/model for use in Playground, evaluators, insights, and fleet) is a separate setting from the price map. Enterprise orgs can create an organization-scoped model configuration, but each workspace must still enable it individually under Feature Access > Evaluators. Setting up a model configuration doesn't by itself create an org-scoped price entry; pricing is configured separately as described above.

References