KamoCRM

A model list anyone can read no longer passes a wrong key

FixAIService
Expediere
25 septembrie 2026 la 20:33 UTC
Autor
Kamo
Comite
b0d107a

The Hugging Face router and OpenRouter answer GET /v1/models with 200 for no key and for a wrong key, so Test connection read OK and sync reconciled 140 models for a provider whose every chat then failed with 401 (SP01 Task 38 Step 4). AZURE_OPENAI, CUSTOM, HUGGINGFACE) now prove the key when they send one: the same listing is asked for without it, and a 401/403 there means the answer already proved the key. Otherwise the key goes to /v1/chat/completions with an empty body, which the server authenticates before reading: 401/403 fails the check as auth_failed, while anything else (400 for a good key, measured on both vendors) leaves the listing's verdict. No inference runs, so sweeps cost nothing.

Toate modificările

Ca ceea ce vezi de transport maritim?

Toate acestea ajung în spațiul de lucru pe cont propriu. Începeți cu planul gratuit și citiți această pagină din nou într-o lună.

Pornește gratuit pentru totdeaunaVezi prețurile