usage (prompt_tokens_details.cached_tokens). Caching is automatic and best-effort: a
prefix stays cached only while there is room for it.
Your cache is your own
Every account has its own cache. A prefix one account sent is never reused for another account’s request, and no other account can observe what yours has cached. All of your API keys share your account’s cache, including keys you create after rotating an old one.Splitting your cache further: cache_salt
If you serve several end customers through one account, you can keep their prefixes apart too.
Send a cache_salt string with the request: requests reuse each other’s prefixes only when
they carry the same cache_salt. A salt is always scoped to your account, so two accounts
that pick the same value still never share a cache.
- Any non-empty string; an empty string or no
cache_saltmeans your account’s default cache. - Use a stable value per partition, such as your own customer id. Changing it starts that partition from an empty cache.
- Supported on
/v1/chat/completions,/v1/completions,/v1/responsesand/v1/messages.
cache_salt that is not a string is rejected with a 400.