Chat API routes to v1 endpoint despite v2 client availability

[JayMehta21]

Observation

While using the TypeScript SDK, I noticed that chat() and chatStream() methods are still routing requests to /v1/chat.

However, the SDK exposes a v2 client:
get v2() { ... }

Impact

• Responses may not leverage latest API improvements
• Leads to suboptimal LLM performance
• Confusing for developers expecting v2 behavior

Suggestion

• Either route default chat methods to /v2/chat
• Or clearly document v1 vs v2 usage
• Or expose client.v2.chat() more prominently

Additional Context

Happy to contribute a fix if guidance is provided, especially if changes are required in the Fern API definition.

[daniel-cohere]

Hi Jay - thanks for raising your concern.

The intention behind leaving chat() and chatStream() routing to /v1/chat was so that we didn't break existing usage of our SDK when we released V2. Unfortunately, I don't think we can change this at the moment.

We have tried our best to document usage clearly. For example in our API reference you'll see the client instantiated via const cohere = new CohereClientV2({});. This also appears in our Working with Cohere's API and SDK page and in the SDK Readme. Is there anywhere in particular you think we could improve the documentation?