[Feature]: custom documentation in case of custom authentication header name

[mohittalele]

The Feature

Litellm allows for custom authentication header using litellm_key_header_name.

with this setup the the virtual key goes into this header. However, litellm UI API reference tab is not customized as per authentication header.

API reference should also include the custom header specific documentation for specific sdks.

Motivation, pitch

With custom header the use different sdk is not straightforward for people who are just getting started. The correct API reference would speed up onboarding of users on litellm.

Are you a ML Ops Team?

Yes

Twitter / LinkedIn details

No response

[CLAassistant]

All committers have signed the CLA.

[sivaramaaa]

NOTE:

There is still one more hardcoded check in : if tool_calling_method is auto : https://github.com/browser-use/browser-use/blob/577e15c963f7e3c499aac312ecb8da6e1f4733fe/browser_use/agent/service.py#L296

Also i am not sure if we require a new param non_function_calling_models or if we can simply re-use the existing tool_calling_method param and add checks based on that (Any help from maintainer here could help me optimize this code better)

This PR fixes : https://github.com/browser-use/browser-use/issues/1020 A slightly better fix compared to : https://github.com/browser-use/browser-use/pull/1048

[pirate]

Thanks for your work on this so far.

We have changed this area of the codebase recently to improve this, the model names are now all at the top of the file, but it still needs some work.

I have created a new issue to track this the next steps here: https://github.com/browser-use/browser-use/issues/1808