[FEATURE_REQUEST] Description for OR's "Enable web search" option should mention it's not free

[cloak1505]

Have you searched for similar requests?

Yes

Is your feature request related to a problem? If so, please describe.

Too many users end up having web search on and wondering why free models report insufficient credits.

Doc: https://openrouter.ai/docs/features/web-search#pricing

The web plugin uses your OpenRouter credits and charges $4 per 1000 results. By default, max_results set to 5, this comes out to a maximum of $0.02 per request, in addition to the LLM usage for the search result prompt tokens.

Describe the solution you'd like

Original description: Use search capabilities provided by the backend.

Suggestion (OR only): Use search capabilities provided by the backend. NOT free - may cost up to $0.02 per request, including for free models.

More OR-specific suggestion: Use the web search plugin powered by Exa. NOT free - may cost up to $0.02 per request, including for free models.

Describe alternatives you've considered

No response

Additional context

No response

Priority

Low (Nice-to-have)

Are you willing to test this on staging/unstable branch if this is implemented?

Yes

[Cohee1207]

Instead of that, maybe add a fee to the cost estimator?

[cloak1505]

Instead of that, maybe add a fee to the cost estimator?

I'm guessing you want to avoid per-endpoint descriptions. Well, makes to add to cost estimator either way.

Max prompt cost: $0.000 → Max prompt cost: $0.020 (web search enabled) could do, otherwise users might wonder where the $0.02 is coming from.

[cloak1505]

Actually, → Max prompt cost: $0.000 + $0.02 (web search enabled) so the + part simply shows up when true. Less ambiguous when a paid model is used.