Earlier commit added a bare `inference_geo_us` key set to the full input
total, which overlaps with cache_read / cache_creation / priority — the
keys in input_token_details were no longer mutually exclusive, which the
langchainplus cost engine depends on (it sums detail values and treats
the remainder as the implicit non-cache base).
Restructure so inference_geo and service_tier compose into a single key
prefix. Every cache bucket gets the combined prefix, and the non-cache
base input lives under the bare prefix as its own bucket. Buckets sum to
input_tokens / output_tokens regardless of which dimensions are active:
service_tier=priority, inference_geo=us:
inference_geo_us_priority_cache_read
inference_geo_us_priority_cache_creation
inference_geo_us_priority (= non-cache input)
service_tier=standard, inference_geo=us:
inference_geo_us_cache_read
inference_geo_us_cache_creation
inference_geo_us (= non-cache input)
service_tier=priority, inference_geo=global:
priority_cache_read
priority_cache_creation
priority (= non-cache input)
Default service_tier=standard + inference_geo=global emits the original
bare `cache_read` / `cache_creation` keys with no non-cache bucket
(matches legacy behavior; non-cache base stays implicit).
Tests now assert sum(details.values()) == input_tokens for every
non-default combination.
LangChain Monorepo
Important
Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.
Important
This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:
core/ # Core primitives and abstractions for langchain
langchain/ # langchain-classic
langchain_v1/ # langchain
partners/ # Certain third-party providers integrations (see below)
standard-tests/ # Standardized tests for integrations
text-splitters/ # Text splitter utilities
(Each package contains its own README.md file with specific details about that package.)
Integrations (partners/)
The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:
Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.
For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.