Check LLM Tokenizer Availability
GET/api/v1/llm/tokenizer-availability
Report whether the agent could load tokenizer from the hub. Advice only, stored nowhere — the operator decides. Probed server-side because the badge must reflect what the AGENT pod can reach: the hub is HF_ENDPOINT, the cluster's keeper mirror the browser cannot see. The agent's own load failure is permanent for the pod's lifetime, so catching a typo, a gated repo, or a not-yet-seeded keeper here — while the form is still open — is the whole value. The id is format-checked with the LLMModel.tokenizer field rules before anything goes on the wire (every path segment starts alphanumeric, so no traversal), and the probed host comes from settings, never from the caller.
요청
응답
- 200
- 400
- 401
- 403
- 404
- 405
- 409
- 410
- 413
- 415
- 422
- 429
- 500
- 502
- 503
- 504
Successful Response
Bad Request
Unauthorized
Forbidden
Not Found
Method Not Allowed
Conflict
Gone
Request Entity Too Large
Unsupported Media Type
Unprocessable Entity
Too Many Requests
Internal Server Error
Bad Gateway
Service Unavailable
Gateway Timeout